Website review, no card needed

keelerusa.com logo

keelerusa.com website review

Visit site (opens in a new tab)Reviewed 3 November 202655 issues · 90 checks

This review found 55 issues worth fixing on keelerusa.com, 21 of them high impact, across 90 checks. The most urgent: improve image delivery. 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
4.3 s3.3 sMay 16Oct 314.1 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20263.5 s
May 23, 20263.5 s
May 30, 20263.8 s
Jun 6, 20263.6 s
Jun 13, 20263.7 s
Jun 20, 20263.7 s
Jun 27, 20263.7 s
Jul 4, 20263.9 s
Jul 11, 20263.8 s
Jul 18, 20263.7 s
Jul 25, 20263.9 s
Aug 1, 20263.9 s
Aug 8, 20263.9 s
Aug 15, 20263.9 s
Aug 22, 20263.6 s
Aug 29, 20263.7 s
Sep 5, 20264.0 s
Sep 12, 20264.0 s
Sep 19, 20264.0 s
Sep 26, 20263.9 s
Oct 3, 20264.0 s
Oct 10, 20264.2 s
Oct 17, 20264.2 s
Oct 24, 20264.2 s
Oct 31, 20264.1 s
Real-visitor tap response (INP)75th percentile, phones
128 ms79 msMay 16Oct 31118 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 202696 ms
May 23, 202696 ms
May 30, 202694 ms
Jun 6, 202685 ms
Jun 13, 202687 ms
Jun 20, 202687 ms
Jun 27, 202693 ms
Jul 4, 2026100 ms
Jul 11, 2026100 ms
Jul 18, 2026104 ms
Jul 25, 2026103 ms
Aug 1, 2026100 ms
Aug 8, 202694 ms
Aug 15, 202693 ms
Aug 22, 202693 ms
Aug 29, 202691 ms
Sep 5, 2026100 ms
Sep 12, 202697 ms
Sep 19, 202696 ms
Sep 26, 2026102 ms
Oct 3, 2026106 ms
Oct 10, 2026117 ms
Oct 17, 2026122 ms
Oct 24, 2026118 ms
Oct 31, 2026118 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 keelerusa.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. keelerusa.com at 1.1 s1.1 s
  2. keelerusa.com at 2.3 s2.3 s
  3. keelerusa.com at 3.4 s3.4 s
  4. keelerusa.com at 4.5 s4.5 s
  5. keelerusa.com at 5.7 s5.7 s
  6. keelerusa.com at 6.8 s6.8 s
  7. keelerusa.com at 8.0 s8.0 s
  8. keelerusa.com at 9.1 s9.1 s

Speed

14 to fix41
  • Improve image delivery

    1.2 s · 6.2 MB

    26 images could be 6.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.2 s faster on a phone.

  • Use efficient cache lifetimes

    2.3 s · 3.4 MB

    271 files are served with short cache lifetimes, so returning visitors download them again (3.4 MB).

  • Render-blocking requests

    1.4 s

    4 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.4 s.

  • Mobile performance score: 41

    41/100

    Your mobile performance score is 41. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Main-thread work: 4.7 s

    A phone's processor spends 4.7 s on main-thread work while loading, 2.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • Reduce unused JavaScript

    890 ms · 1.4 MB

    About 1.4 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 890 ms faster on a phone.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google CDN, YouTube and Google Tag Manager and others), adding 3.1 MB and 1.2 s of main-thread time.

  • Reduce unused CSS

    890 ms · 264 KiB

    About 264 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 890 ms faster on a phone.

  • Font display

    500 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 500 ms).

  • Google CDN adds 364 ms

    364 ms

    Google CDN costs a phone 364 ms of main-thread work and 1.1 MB 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.

  • YouTube adds 328 ms

    328 ms

    YouTube costs a phone 328 ms of main-thread work and 989 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.

  • Google Tag Manager adds 235 ms

    235 ms

    Google Tag Manager costs a phone 235 ms of main-thread work and 343 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.

  • 1,814 HTML elements

    The page has 1,814 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • LiveChat adds 46 ms

    46 ms

    LiveChat costs a phone 46 ms of main-thread work and 440 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.

  • 17 long tasks on the main thread

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

  • Legacy JavaScript

    13 KiB

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

  • Chained critical requests

    Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

  • Minify JavaScript

    2 KiB

    2 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 11 ms

    11 ms

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

Core Web Vitals

12 to fix67
  • Fails Core Web Vitals for real visitors

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

  • Real-user LCP: 4.1 s

    4.1 s

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

  • Real-user FCP: 3.3 s

    3.3 s

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

  • Real-user TTFB: 1.8 s

    1.8 s

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

  • Largest Contentful Paint: 11.6 s

    11.6 s

    Your largest element takes 11.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Partner Portal”. Most of its time is resource load delay (7.5 s).

  • Speed Index: 16.9 s

    16.9 s

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

  • Time to Interactive: 46.6 s

    46.6 s

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

  • Tap response (INP) got 23% slower for real visitors

    +23%

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

  • Cumulative Layout Shift: 0.244

    0.244

    The layout shifts by 0.244 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Total Blocking Time: 383 ms

    383 ms

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

  • First Contentful Paint: 2.3 s

    2.3 s

    The first text or image appears after 2.3 s on a phone. Good is under 1.8 s.

  • 19 images without width and height

    19 images have no width and height attributes, so the layout jumps as each one loads.

  • Largest content (LCP) got 18% slower for real visitors

    +18%

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

2 checks passed
  • Real-user INP: 118 ms

    118 ms

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

  • Real-user CLS: 0.02

    0.02

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

Images and page weight

5 to fix18
  • Page weight: 11.5 MB in 346 requests

    11.5 MB

    Your homepage downloads 11.5 MB in 346 requests on a phone: images 7.2 MB (40), scripts 3.4 MB (255) and other files 392 KiB (29). Under 2 MB keeps phones on slow connections fast.

  • 5 images over 500 KB

    5 images weigh 5.0 MB together. On a phone connection a single image that size takes seconds.

  • 4 images far larger than shown

    2.1 MB

    4 images are downloaded at several times the size a phone draws them, for example 1st-8a.jpg at 2,362 px wide, shown at 360 px. Resized copies would save about 2.1 MB.

  • 19 images in older formats

    19 images (6.8 MB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

  • 5 images below the first screen load straight away

    5 images further down the page (4.2 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 3.3 g of CO₂ per visit

    3.27 g

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

Accessibility

7 to fixGoogle 7990
  • 18 buttons without a name

    18 buttons have no accessible name, so screen readers announce just “button”.

  • Certain ARIA roles must contain particular children (1 element)

    Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

  • Images must have alternative text (1 element)

    Images must have alternative text: 1 element on the page fails this check, rated critical by axe-core.

  • 14 text elements with low contrast

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

  • All page content should be contained by landmarks (3 elements)

    All page content should be contained by landmarks: 3 elements on the page fail this check, rated moderate by axe-core.

  • 17 links without text

    17 visible links have no text or label, so screen readers cannot say where they go.

  • 2 form fields without a label

    2 form fields have no label, so screen readers announce an empty box and autofill guesses.

1 checks passed
  • 47 automated accessibility rules passed

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

SEO

8 to fixGoogle 8362
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Title is short (29 characters)

    Your title is only 29 characters: “Keeler | Diagnostic equipment”. 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.

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • Meta description is long (260 characters)

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

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No XML sitemap

    No XML sitemap at https://www.keelerusa.com/sitemap.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.

  • No X (Twitter) card tag

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

  • 236 internal links, 121 external

    The homepage links to 236 pages on keelerusa.com and 121 external pages.

1 checks passed
  • robots.txt in place

    robots.txt is in place.

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.keelerusa.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 (1,309 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix95
  • 9 pages without a meta description

    https://www.keelerusa.com/catalogsearch/advanced, https://www.keelerusa.com/products/diagnostic.html, https://www.keelerusa.com/products/diagnostic/binocular-indirect-ophthalmoscopes.html, https://www.keelerusa.com/products/diagnostic/binocular-indirect-ophthalmoscopes/all-pupil-ii.html, https://www.keelerusa.com/products/diagnostic/binocular-indirect-ophthalmoscopes/spectra-iris.html and https://www.keelerusa.com/products/diagnostic/binocular-indirect-ophthalmoscopes/vantage-plus.html and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 internal pages checked

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

6 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

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

  • 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 14 pages that loaded have a <title>.

Best practices

5 to fixGoogle 6969
  • 10 broken images

    10 images failed to load on a phone, for example https://www.keelerusa.com/.

  • 10 small tap targets

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

  • 5 third-party cookies

    5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “Connecting to 'https://ad.doubleclick.net/ccm/s/collect?auid=1493247116.1793744194&gtm=45He6b20v9127308993za200zd912730…”.

  • 3 distorted images

    3 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix90
  • Thin social proof

    Social proof on the homepage: 6 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

  • 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.

  • About 529 words of copy

    The homepage carries about 529 words of visible text.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Contact us”.

  • 13 calls to action

    The homepage has 13 calls to action, for example “Digital contact tonometers”, “Standard contact tonometers” and “Non contact tonometers”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager and Meta Pixel.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Meta Pixel (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

  • 25 cookies set on arrival

    25

    Opening the homepage sets 25 cookies, 4 of them by other companies (measured from a US location before any click).

  • 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.

  • 18 other companies contacted

    Loading the homepage contacts 18 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

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 keelerusa.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
WordPress
E-commerce
Magento
Analytics
Google Tag Manager

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 55 issues on keelerusa.com, including 26 speed issues, 8 SEO issues and 1 conversion gap. 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