Website review, no card needed

bestwordlist.com logo

bestwordlist.com website review

Visit site (opens in a new tab)Reviewed 11 October 202621 issues · 72 checks

This review found 21 issues worth fixing on bestwordlist.com, 4 of them high impact, across 72 checks. The most urgent: 4 text elements with low contrast. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
554 ms491 msApr 18Oct 3498 ms
Show as table
DateReal-visitor load time (LCP)
Apr 18, 2026514 ms
Apr 25, 2026514 ms
May 2, 2026517 ms
May 9, 2026523 ms
May 16, 2026528 ms
May 23, 2026532 ms
May 30, 2026540 ms
Jun 6, 2026541 ms
Jun 13, 2026542 ms
Jun 20, 2026545 ms
Jun 27, 2026547 ms
Jul 4, 2026547 ms
Jul 11, 2026543 ms
Jul 18, 2026535 ms
Jul 25, 2026528 ms
Aug 1, 2026526 ms
Aug 8, 2026527 ms
Aug 15, 2026533 ms
Aug 22, 2026536 ms
Aug 29, 2026541 ms
Sep 5, 2026536 ms
Sep 12, 2026529 ms
Sep 19, 2026516 ms
Sep 26, 2026505 ms
Oct 3, 2026498 ms
Real-visitor tap response (INP)75th percentile, phones
60 ms58 msApr 18Oct 359 ms
Show as table
DateReal-visitor tap response (INP)
Apr 18, 202660 ms
Apr 25, 202660 ms
May 2, 202660 ms
May 9, 202659 ms
May 16, 202659 ms
May 23, 202659 ms
May 30, 202659 ms
Jun 6, 202660 ms
Jun 13, 202660 ms
Jun 20, 202660 ms
Jun 27, 202660 ms
Jul 4, 202660 ms
Jul 11, 202660 ms
Jul 18, 202660 ms
Jul 25, 202659 ms
Aug 1, 202659 ms
Aug 8, 202659 ms
Aug 15, 202659 ms
Aug 22, 202658 ms
Aug 29, 202659 ms
Sep 5, 202659 ms
Sep 12, 202659 ms
Sep 19, 202659 ms
Sep 26, 202659 ms
Oct 3, 202659 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of bestwordlist.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. bestwordlist.com at 0.4 s0.4 s
  2. bestwordlist.com at 0.8 s0.8 s
  3. bestwordlist.com at 1.1 s1.1 s
  4. bestwordlist.com at 1.5 s1.5 s
  5. bestwordlist.com at 1.9 s1.9 s
  6. bestwordlist.com at 2.3 s2.3 s
  7. bestwordlist.com at 2.6 s2.6 s
  8. bestwordlist.com at 3.0 s3.0 s

Speed

2 to fix94
  • Reduce unused JavaScript

    291 KiB

    About 291 KiB of JavaScript is downloaded but never used on this page.

  • Google/Doubleclick Ads adds 137 ms

    137 ms

    Google/Doubleclick Ads costs a phone 137 ms of main-thread work and 307 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google/Doubleclick Ads, sportslocalmedia.com and Google Tag Manager and others), adding 836 KiB and 414 ms of main-thread time.

  • 6 long tasks on the main thread

    6 long tasks block the main thread while loading, the longest for 189 ms. During a long task the page ignores taps.

  • Use efficient cache lifetimes

    176 KiB

    8 files are served with short cache lifetimes, so returning visitors download them again (176 KiB).

  • Legacy JavaScript

    11 KiB

    Polyfills for old browsers add 11 KiB JavaScript that modern phones do not need.

3 checks passed
  • Mobile performance score: 94

    94/100

    Your mobile performance score is 94 (desktop: 86). That is in Google's “good” band (90 and up).

  • Main-thread work: 1.8 s

    A phone's processor spends 1.8 s on main-thread work while loading, 1.2 s of it running JavaScript. That is comfortably low.

  • Server response: 1 ms

    1 ms

    Your server sent the HTML in 1 ms, well inside Google's 600 ms guideline.

Core Web Vitals

3 to fix100
  • Time to Interactive: 10.0 s

    10.0 s

    The page becomes fully interactive after 10.0 s. Good is under 3.8 s.

  • Total Blocking Time: 241 ms

    241 ms

    Scripts block taps and scrolling for 241 ms in total while the page loads. Good is under 200 ms.

  • Speed Index: 3.5 s

    3.5 s

    Visually, the page fills in at 3.5 s (Speed Index). Good is under 3.4 s.

  • Tap response (INP) held steady for real visitors

    -2%

    Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' tap response (inp) went from 60 ms to 59 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Largest content (LCP) held steady for real visitors

    -2%

    Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' largest content (lcp) went from 0.5 s to 0.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

9 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 0.8 s

    0.8 s

    Real visitors wait 0.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 60 ms

    60 ms

    Real visitors wait 60 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Real-user FCP: 0.7 s

    0.7 s

    Real visitors see the first content after 0.7 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 373 ms

    373 ms

    Real visitors wait 373 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

  • First Contentful Paint: 0.8 s

    0.8 s

    The first text or image appears after 0.8 s, inside the 1.8 s “good” threshold.

  • Largest Contentful Paint: 0.8 s

    0.8 s

    Your largest element renders in 0.8 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Click to choose the size All alphabetical All by size 2 3 4…”.

Images and page weight

100
  • About 0.2 g of CO₂ per visit

    0.25 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.25 g of CO₂e: 29.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

4 checks passed
  • Page weight: 888 KiB in 100 requests

    888 KiB

    Your homepage downloads 888 KiB in 100 requests on a phone: scripts 719 KiB (11), other files 134 KiB (69) and images 19 KiB (15). That is a lean page.

  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

3 to fixGoogle 8893
  • 4 text elements with low contrast

    4 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • Headings skip levels

    Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 1 image in the HTML carry an alt attribute.

  • 23 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 27 WCAG 2.2 A/AA and best-practice rules on the phone render: 23 passed and 4 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

6 to fixGoogle 9273
  • Title is short (14 characters)

    Your title is only 14 characters: “Best Word List”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • 6 H1 headlines

    There are 6 <h1> headlines (“1. Lists of all words”, “2. Word lists beginning with …” and “3. Word lists ending with …”). One clear main headline is easier for people and search engines.

  • Meta description is long (163 characters)

    Your meta description is 163 characters; Google truncates after about 160, so the end of your pitch is cut.

  • No XML sitemap

    No XML sitemap at https://www.bestwordlist.com/sitemaplists.xml, so Google discovers your pages only by following links.

  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • Open Graph partly set

    Open Graph is missing og:title and og:description, so shared links fall back to guesses.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 154 internal links, 7 external

    The homepage links to 154 pages on bestwordlist.com and 7 external pages.

2 checks passed
  • Canonical URL set

    The canonical URL is https://www.bestwordlist.com/index.htm.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

AI search readiness

1 to fix88
  • No Organization structured data

    There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

  • No llms.txt

    There is no https://www.bestwordlist.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

2 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Text is in the HTML

    Your server sends the page's text in the HTML (163 words), so crawlers that don't run JavaScript still read it.

Other pages

100
  • 2 pages with very little text

    https://www.bestwordlist.com/indexwordswith.htm and https://www.bestwordlist.com/indexposition.htm have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 8 pages slow to respond

    https://www.bestwordlist.com/indexwordswith.htm, https://www.bestwordlist.com/indexposition.htm, https://www.bestwordlist.com/allwordssize.htm, https://www.bestwordlist.com/2letterwords.htm, https://www.bestwordlist.com/3letterwords.htm and https://www.bestwordlist.com/4letterwords.htm and 2 others took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 151 found) and read each the way a search engine does.

7 checks passed
  • Linked pages load

    11 pages of 15 loaded without an error (the rest turned automated requests away).

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 11 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 11 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 161 small tap targets

    161 of 161 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix42
  • No call to action on the first screen

    On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • No direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

  • Only about 163 words

    The homepage has only about 163 words of visible text; thin pages give Google and first-time buyers little to go on.

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

  • No risk reducer

    No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

1 checks passed
  • 1 call to action

    The homepage has 1 call to action, for example “learn more”.

Privacy and tracking

  • No consent tool detected

    No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at bestwordlist.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Go beyond the website

What your $25 Growth Playbook adds

This review found 21 issues on bestwordlist.com, including 5 speed issues, 6 SEO issues and 5 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25