Website review, no card needed
visionease.com website review
Visit site (opens in a new tab)Reviewed 1 November 202625 issues · 76 checks
This review found 25 issues worth fixing on visionease.com, 3 of them high impact, across 76 checks. The most urgent: 45 text elements with low contrast. 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
91AClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.0 s |
| May 23, 2026 | 1.9 s |
| May 30, 2026 | 1.7 s |
| Jun 6, 2026 | 1.6 s |
| Jun 27, 2026 | 1.8 s |
| Jul 4, 2026 | 2.0 s |
| Jul 11, 2026 | 2.1 s |
| Aug 1, 2026 | 2.1 s |
| Aug 29, 2026 | 2.0 s |
| Oct 10, 2026 | 2.2 s |
| Oct 17, 2026 | 2.6 s |
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
Speed
Mobile performance score: 85
85/100Your mobile performance score is 85. Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
450 ms · 136 KiBAbout 136 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.
Google Tag Manager adds 187 ms
187 msGoogle Tag Manager costs a phone 187 ms of main-thread work and 298 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.
4 third-party services on the page
4 third-party services load with your homepage (Google Tag Manager, Google Analytics and YouTube and others), adding 349 KiB and 223 ms of main-thread time.
Use efficient cache lifetimes
150 ms · 16 KiB1 file is served with short cache lifetimes, so returning visitors download them again (16 KiB).
Render-blocking requests
150 ms2 files block the first paint until they finish downloading. Deferring or inlining them could save about 150 ms.
2 long tasks on the main thread
2 long tasks block the main thread while loading, the longest for 107 ms. During a long task the page ignores taps.
Improve image delivery
50 KiB5 images could be 50 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Reduce unused CSS
36 KiBAbout 36 KiB of CSS is downloaded but never applied on this page.
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.
2 checks passed
Main-thread work: 0.4 s
A phone's processor spends 0.4 s on main-thread work while loading, 200 ms of it running JavaScript. That is comfortably low.
Server response: 2 ms
2 msYour server sent the HTML in 2 ms, well inside Google's 600 ms guideline.
Core Web Vitals
First Contentful Paint: 3.4 s
3.4 sThe first text or image appears after 3.4 s on a phone. Good is under 1.8 s.
Largest content (LCP) got 25% slower for real visitors
+25%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 2.0 s to 2.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest Contentful Paint: 3.4 s
3.4 sYour largest element takes 3.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “VISION EASE, a HOYA Vision Care-owned company, is a global …”. Most of its time is element render delay (1.4 s).
Time to Interactive: 5.4 s
5.4 sThe page becomes fully interactive after 5.4 s. Good is under 3.8 s.
Speed Index: 3.5 s
3.5 sVisually, the page fills in at 3.5 s (Speed Index). Good is under 3.4 s.
Not enough real-visitor data yet
Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.
2 checks passed
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 29 ms
29 msScripts block the page for only 29 ms while loading. Good is under 200 ms.
Images and page weight
4 images below the first screen load straight away
4 images further down the page (108 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 0.2 g of CO₂ per visit
0.21 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.21 g of CO₂e: 24.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Page weight: 743 KiB in 35 requests
743 KiBYour homepage downloads 743 KiB in 35 requests on a phone: scripts 348 KiB (7), images 249 KiB (17) and fonts 93 KiB (5). That is a lean page.
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
45 text elements with low contrast
45 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 (6 elements)
All page content should be contained by landmarks: 6 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.
3 links without text
3 visible links have no text or label, so screen readers cannot say where they go.
2 checks passed
Every image has alt text
All 13 images in the HTML carry an alt attribute.
31 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 36 WCAG 2.2 A/AA and best-practice rules on the phone render: 31 passed and 5 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
No favicon declared
No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.
4 links with vague text
4 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
54 internal links, 3 external
The homepage links to 54 pages on visionease.com and 3 external pages.
7 checks passed
Meta description: 153 characters
Your meta description is 153 characters: “We are more than a lens manufacturer. We are a partner you can count on to help your lens business grow. Learn more abo…”.
One H1 headline
Your main headline reads: “Crafted With Precision”.
Title: 51 characters
Your title is a healthy 51 characters: “VISION EASE | A Global Ophthalmic Lens Manufacturer”.
Canonical URL set
The canonical URL is https://visionease.com/.
Structured data in place
Structured data found: BreadcrumbList, WebPage and WebSite.
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://visionease.com/sitemap.xml.
AI search readiness
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://visionease.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 (582 words), so crawlers that don't run JavaScript still read it.
Other pages
1 linked page hidden from search
https://visionease.com/about-us/who-we-are is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
2 pages share a title
https://visionease.com/resources/how-to-order and https://visionease.com/resources/blogs all use the title “How to Order VISION EASE Lenses | Support | VISION EASE”. Search engines can't tell which page to show for a search, so each competes with the others.
6 pages without a meta description
https://visionease.com/optical-lenses-brands/sun-products, https://visionease.com/optical-lenses-brands/clear-products, https://visionease.com/partner, https://visionease.com/hoya-linc, https://visionease.com/resources/lens-availability and https://visionease.com/about-us/who-we-are have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages share a meta description
https://visionease.com/resources/how-to-order and https://visionease.com/resources/blogs use the same meta description. A description written for each page earns more clicks.
1 page without an H1
https://visionease.com/about-us/patents has no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 21 found) and read each the way a search engine does.
3 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.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
27 of 30 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
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 577 words of copy
The homepage carries about 577 words of visible text.
6 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “How to Order” and “Contact”.
11 calls to action
The homepage has 11 calls to action, for example “How to Order”, “Contact” and “Learn More”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 4 phone links and 1 email link.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
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.
6 cookies set on arrival
6Opening the homepage sets 6 cookies, 1 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.
4 other companies contacted
Loading the homepage contacts 4 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 visionease.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 © 2024.
Stack
- CMS
- WordPress
- Analytics
- Google Tag Manager
- Hosting
- Google Cloud
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 25 issues on visionease.com, including 8 speed issues, 3 SEO issues and 2 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.