Website review, no card needed
keelerglobal.com website review
Visit site (opens in a new tab)Reviewed 30 October 202651 issues · 93 checks
This review found 51 issues worth fixing on keelerglobal.com, 21 of them high impact, across 93 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
73C- #91,625 of 124,051 reviewed websitesbeats 23%
- #57,075 of 69,761 online storesbeats 15%
- #1,785 of 2,904 WooCommerce storesbeats 33%
Closest competitors among WooCommerce stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 3.7 s |
| May 16, 2026 | 3.7 s |
| May 23, 2026 | 3.8 s |
| May 30, 2026 | 3.9 s |
| Jun 6, 2026 | 4.0 s |
| Jun 13, 2026 | 4.0 s |
| Jun 20, 2026 | 4.0 s |
| Jun 27, 2026 | 4.0 s |
| Jul 4, 2026 | 4.0 s |
| Jul 11, 2026 | 4.1 s |
| Jul 18, 2026 | 4.2 s |
| Jul 25, 2026 | 4.3 s |
| Aug 1, 2026 | 4.6 s |
| Aug 8, 2026 | 4.7 s |
| Aug 15, 2026 | 4.8 s |
| Aug 22, 2026 | 4.8 s |
| Aug 29, 2026 | 4.7 s |
| Sep 5, 2026 | 4.8 s |
| Sep 12, 2026 | 5.0 s |
| Sep 19, 2026 | 5.1 s |
| Sep 26, 2026 | 5.8 s |
| Oct 3, 2026 | 5.9 s |
| Oct 10, 2026 | 6.3 s |
| Oct 17, 2026 | 6.5 s |
| Oct 24, 2026 | 6.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 141 ms |
| May 16, 2026 | 146 ms |
| May 23, 2026 | 145 ms |
| May 30, 2026 | 154 ms |
| Jun 6, 2026 | 154 ms |
| Jun 13, 2026 | 146 ms |
| Jun 20, 2026 | 146 ms |
| Jun 27, 2026 | 146 ms |
| Jul 4, 2026 | 167 ms |
| Jul 11, 2026 | 172 ms |
| Jul 18, 2026 | 174 ms |
| Jul 25, 2026 | 170 ms |
| Aug 1, 2026 | 145 ms |
| Aug 8, 2026 | 139 ms |
| Aug 15, 2026 | 142 ms |
| Aug 22, 2026 | 144 ms |
| Aug 29, 2026 | 146 ms |
| Sep 5, 2026 | 156 ms |
| Sep 12, 2026 | 151 ms |
| Sep 19, 2026 | 144 ms |
| Sep 26, 2026 | 148 ms |
| Oct 3, 2026 | 143 ms |
| Oct 10, 2026 | 143 ms |
| Oct 17, 2026 | 145 ms |
| Oct 24, 2026 | 140 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
How it loaded on a phone
1.4 s
2.8 s
4.2 s
5.6 s
7.0 s
8.4 s
9.8 s
11.1 s
Speed
Use efficient cache lifetimes
5.4 s · 2.6 MB123 files are served with short cache lifetimes, so returning visitors download them again (2.6 MB).
Improve image delivery
3.4 s · 1.4 MB10 images could be 1.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.4 s faster on a phone.
Render-blocking requests
3.1 s49 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.1 s.
Reduce unused JavaScript
1.4 s · 997 KiBAbout 997 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.4 s faster on a phone.
Mobile performance score: 47
47/100Your mobile performance score is 47. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
8 third-party services on the page
8 third-party services load with your homepage (Google CDN, Google Tag Manager and Amazon Web Services and others), adding 1.8 MB and 1.0 s of main-thread time.
Google CDN adds 546 ms
546 msGoogle CDN costs a phone 546 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.
Font display
400 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 400 ms).
Main-thread work: 3.9 s
A phone's processor spends 3.9 s on main-thread work while loading, 1.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Reduce unused CSS
300 ms · 89 KiBAbout 89 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.
Google Tag Manager adds 273 ms
273 msGoogle Tag Manager costs a phone 273 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.
2,053 HTML elements
The page has 2,053 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
11 long tasks on the main thread
11 long tasks block the main thread while loading, the longest for 205 ms. During a long task the page ignores taps.
Legacy JavaScript
150 ms · 18 KiBPolyfills for old browsers add 18 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
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.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
1 checks passed
Server response: 113 ms
113 msYour server sent the HTML in 113 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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: 6.5 s
6.5 sReal visitors wait 6.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 5.5 s
5.5 sReal visitors see the first content after 5.5 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 5.1 s
5.1 sReal visitors wait 5.1 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 26.2 s
26.2 sYour largest element takes 26.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Speed Index: 20.6 s
20.6 sVisually, the page fills in at 20.6 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 29.2 s
29.2 sThe page becomes fully interactive after 29.2 s. Good is under 3.8 s.
First Contentful Paint: 3.2 s
3.2 sThe first text or image appears after 3.2 s on a phone. Good is under 1.8 s.
Largest content (LCP) got 78% slower for real visitors
+78%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 3.7 s to 6.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 480 ms
480 msScripts block taps and scrolling for 480 ms in total while the page loads. Good is under 200 ms.
5 images without width and height
5 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
-1%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 141 ms to 140 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
2 checks passed
Real-user CLS: 0.01
0.01For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0.015
0.015The layout barely moves while loading (CLS 0.015, good is under 0.1).
Images and page weight
Page weight: 8.7 MB in 156 requests
8.7 MBYour homepage downloads 8.7 MB in 156 requests on a phone: images 5.8 MB (27), scripts 2.0 MB (62) and other files 357 KiB (6). Under 2 MB keeps phones on slow connections fast.
4 images over 500 KB
4 images weigh 4.3 MB together. On a phone connection a single image that size takes seconds.
2 images far larger than shown
2.2 MB2 images are downloaded at several times the size a phone draws them, for example 1st-8a.jpg at 2,362 px wide, shown at 320 px. Resized copies would save about 2.2 MB.
11 images in older formats
11 images (5.2 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.
An image on the first screen is lazy-loaded
MTMTE-aug25-mobile.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).
About 2.5 g of CO₂ per visit
2.46 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.46 g of CO₂e: 295.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Invalid ARIA attributes
1 element use ARIA attributes their role does not allow, which confuses screen readers.
39 text elements with low contrast
39 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
1 tap target too small
1 tap target is too small or too close together to hit reliably with a finger.
All page content should be contained by landmarks (36 elements)
All page content should be contained by landmarks: 36 elements on the page fail this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
31 links without text
31 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.
ARIA role should be appropriate for the element (2 elements)
ARIA role should be appropriate for the element: 2 elements on the page fail this check, rated minor by axe-core.
Headings should not be empty (1 element)
Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h2 → h4, h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 53 images in the HTML carry an alt attribute.
51 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 61 WCAG 2.2 A/AA and best-practice rules on the phone render: 51 passed and 10 failed. 6 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is short (13 characters)
Your title is only 13 characters: “Keeler - Home”. Between 30 and 65 characters leaves room to say what you do and for whom.
10 links with vague text
10 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
205 internal links, 51 external
The homepage links to 205 pages on keelerglobal.com and 51 external pages.
6 checks passed
Meta description: 132 characters
Your meta description is 132 characters: “Welcome to Keeler. Supporting eye care professionals with trusted products and free education resources to last their c…”.
Canonical URL set
The canonical URL is https://www.keelerglobal.com/.
Structured data in place
Structured data found: BreadcrumbList, ImageObject, Organization, WebPage and WebSite.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://www.keelerglobal.com/sitemap_index.xml.
AI search readiness
No llms.txt
There is no https://www.keelerglobal.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.
3 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.
Organization data: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (1,500 words), so crawlers that don't run JavaScript still read it.
Other pages
6 pages without a meta description
https://www.keelerglobal.com/it, https://www.keelerglobal.com/pt-br, https://www.keelerglobal.com/products, https://www.keelerglobal.com/product-category/binocular-indirect-ophthalmoscopes, https://www.keelerglobal.com/product-category/ophthalmic-cryo-surgical and https://www.keelerglobal.com/software-request have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages without an H1
https://www.keelerglobal.com/it and https://www.keelerglobal.com/pt-br have no <h1> headline, so visitors and search engines get no clear main topic.
11 pages slow to respond
https://www.keelerglobal.com/it, https://www.keelerglobal.com/pt-br, https://www.keelerglobal.com/distributors, https://www.keelerglobal.com/products, https://www.keelerglobal.com/product-category/binocular-indirect-ophthalmoscopes and https://www.keelerglobal.com/product-category/handhelds and 5 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 83 found) and read each the way a search engine does.
5 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.
Titles are unique
Every page we checked has its own title.
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
15 small tap targets
15 of 57 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
5 JavaScript errors while loading
5 errors were logged to the browser console while the page loaded, for example “Invalid or unexpected token”.
5 distorted images
5 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
Local business without LocalBusiness data
Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
A 8-field form
Your longest form asks for 8 fields (3 required). Every extra field lowers completion.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
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 984 words of copy
The homepage carries about 984 words of visible text.
4 checks passed
8 calls to action
The homepage has 8 calls to action, for example “Shop Keeler”, “Contact us” and “Start the returns process”.
Social proof on the page
Social proof on the homepage: 1 customer or partner logo and 2 trust badges.
Analytics in place
Analytics detected: Google Tag Manager and Google Analytics.
Phone number on the homepage
Your phone number is on the homepage.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (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.
2 cookies set on arrival
2Opening the homepage sets 2 cookies (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.
12 other companies contacted
Loading the homepage contacts 12 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 keelerglobal.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
- The footer still says © 2025.
Stack
- CMS
- WordPress
- Framework
- jQuery
- E-commerce
- WooCommerce
- Analytics
- Google Analytics | Google Tag Manager
- Hosting
- Sucuri
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 51 issues on keelerglobal.com, including 23 speed issues, 3 SEO issues and 3 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.