KWFinder for site speed? What to use instead
Short answer KWFinder can't speed up your site. It is a keyword research tool: it shows what people search, how often, and how hard a term is to rank for. To check speed, use Google's free tools: PageSpeed Insights for one page, Search Console's Core Web Vitals report for the whole site. The fixes happen in your images, scripts and hosting.
Want help applying this to your business? Talk it through on a free 30-minute call.
Book a callCan KWFinder improve site speed?
No. KWFinder is a keyword research tool from Mangools. Its own page lists what it does: search volumes, a keyword difficulty score, keyword ideas, the keywords a competitor ranks for, search trends, and local results in more than 65,000 locations (Mangools: KWFinder). Nothing on that page measures how fast your pages load, and nothing changes your website.
The rest of the Mangools suite doesn't fill the gap either. SiteProfiler, its website tool, shows authority, backlink and top-content data, with no load-time or Core Web Vitals check on its page. Its other tools (SERPChecker, SERPWatcher, LinkMiner) cover search results, rank tracking and backlinks (Mangools: SiteProfiler).
Speed is a different job with different tools:
| Job | Question it answers | Tool |
|---|---|---|
| Keyword research | What words do customers type, and can I rank for them? | KWFinder, Google Keyword Planner, Search Console |
| Speed testing | How long does my page take to show and respond on a phone? | PageSpeed Insights, Search Console, Lighthouse |
| Speed fixing | What makes it slow, and how do I remove it? | Your website platform, an image compressor, your host or developer |
A keyword tool can tell you a page should exist. It can't tell you that page's hero photo weighs 4 MB.
What tools actually check site speed?
Three free Google tools cover what a small business needs.
| Tool | What it shows | Best for |
|---|---|---|
| PageSpeed Insights | Real-visitor data for one page (or the whole site) plus a lab test with fix suggestions, mobile and desktop | Checking one page, before and after a fix |
| Search Console, Core Web Vitals report | Which groups of pages pass or fail, based on real visitors | Finding which pages to fix first |
| Lighthouse in Chrome | The same lab test, run from your own browser | Pages behind a login, or retesting while you work |
PageSpeed Insights gives two kinds of numbers. Google explains the difference:
"Lab data is useful for debugging issues, as it is collected in a controlled environment. However, it may not capture real-world bottlenecks. Field data is useful for capturing true, real-world user experience - but has a more limited set of metrics." (PageSpeed Insights: About)
The real-visitor ("field") numbers come from Chrome users over the last 28 days. A new or low-traffic page may not have enough of them; PageSpeed Insights then shows data for the whole site instead (PageSpeed Insights: About).
Lighthouse is the engine behind the lab test. Google describes it as "an open-source, automated tool to help you improve the quality of web pages" (Chrome for Developers: Lighthouse). You can run it from the Lighthouse panel in Chrome's developer tools, which also works on pages that need a login.
For a full walkthrough of each tool, see PageSpeed Insights: how to read it and Search Console site speed.
How to check your site speed in 10 minutes
- Open PageSpeed Insights, paste your home page address and run it. Read the mobile tab first; phones are usually the slower case.
- Look at the top section, the real-visitor data. If it says the page passes the Core Web Vitals assessment, speed is not your main problem.
- If it fails, note which metric is red: loading (LCP), response to taps (INP) or layout jumping (CLS).
- Scroll to the suggestions under the lab test. They name the heavy files, often an image or a third-party script.
- Repeat for your two or three most important service pages.
- If you have Search Console, open the Core Web Vitals report. It groups similar pages, so one fix to a shared template can clear many URLs at once.
What do the numbers mean?
Google's Core Web Vitals are three measures of real visitor experience. Google gives these targets:
| Metric | What it measures | Good | Poor |
|---|---|---|---|
| LCP (Largest Contentful Paint) | When the main image or text block appears | 2.5 seconds or less | Over 4 seconds |
| INP (Interaction to Next Paint) | How fast the page reacts to a tap or click | 200 milliseconds or less | Over 500 milliseconds |
| CLS (Cumulative Layout Shift) | How much the layout jumps while loading | 0.1 or less | Over 0.25 |
Source: PageSpeed Insights: About, and Google Search Central: Core Web Vitals. The real-visitor figure is the 75th percentile, chosen, Google says, "so that developers can understand the most frustrating user experiences on their site."
The 0 to 100 performance score is a lab grade: 90 or above is good, below 50 is poor (PageSpeed Insights: About). Don't chase 100. Google says:
"Core Web Vitals are used by our ranking systems." (Google Search Central: page experience)
and, on the same page, that "trying to get a perfect score just for SEO reasons may not be the best use of your time." Pass the three real-visitor metrics, then stop. More on reading each band: Core Web Vitals checklist.
What actually makes a slow page faster?
The fix depends on which metric fails. Google's web.dev team lists these as the most effective changes:
| Failing metric | Usual cause on a small business site | Fix |
|---|---|---|
| LCP (slow to load) | A huge hero photo or slider, slow hosting | Resize and compress the top image; make it load first; use a CDN (a network that serves files from servers near the visitor) |
| INP (slow to respond) | Chat widgets, pop-ups, tracking and booking scripts | Remove scripts you don't use; load the rest later |
| CLS (layout jumps) | Images, ads or banners with no reserved space | Set width and height on images and embeds |
Source: web.dev: The most effective ways to improve Core Web Vitals.
On Wix, Squarespace or Shopify, you control mainly images, apps and embeds; the platform runs the hosting. On WordPress, you also choose the host, theme and caching plugin. If the fix means editing code, that is a developer's job, not a keyword tool's.
Where KWFinder does help
KWFinder earns its place before a page is built: finding the words customers use, how often they search them, and which terms a small site can realistically win. Its free tier gives 5 lookups per 24 hours (Mangools: KWFinder). Google's free Keyword Planner and your own Search Console data do much of the same job: see keyword research for a local business.
Keywords and speed answer different questions. Google ranks the most relevant page first and uses page experience mostly when relevant pages are otherwise close; why that order matters: page speed vs relevance.
Example
Illustrative cases, not measured results.
A landscaper who bought a keyword tool to fix a slow site
His home page takes about 6 seconds to show its main photo on a phone. A keyword tool shows him 40 search terms, but the page is just as slow afterwards. PageSpeed Insights names the cause: a 5 MB slideshow at the top. Replacing it with one compressed photo brings the main image in well under 2.5 seconds.
A dental office with a good score and no calls
PageSpeed Insights shows 92 on mobile and real visitors pass. Speed is fine. Her problem is that no page mentions "emergency dentist" or her suburb. Here a keyword tool is the right purchase, or the free Keyword Planner.
FAQ
Does Mangools have a site speed tool?
Not on its own pages. KWFinder, SiteProfiler, SERPChecker, SERPWatcher and LinkMiner cover keywords, authority, rankings and backlinks, not load time.
Is PageSpeed Insights free?
Yes. You paste a page address and get the report. Search Console is also free, but you must first verify you own the site: Search Console setup.
Will better keywords make my site feel faster?
No. Words weigh almost nothing next to photos and scripts. Load time changes only when files get lighter or the server gets faster.
My score changes every time I test. Why?
The lab test is one simulated load, so it varies. The real-visitor data covers 28 days of actual visits; judge your site by that.
Different for you?
- New site with almost no visitors: real-visitor data may be missing; use the lab test and fix the biggest suggestions. See Search Console site speed.
- Pages are fast but nobody finds them: that is a keyword and content problem: keyword research for a local business, or the SEO agent.
- Slow site and you don't edit code: the fixes live in the website itself: Website agent.