Website review, no card needed
evergreeneye.com website review
Visit site (opens in a new tab)Reviewed 23 October 202631 issues · 87 checks
This review found 31 issues worth fixing on evergreeneye.com, 7 of them high impact, across 87 checks. The most urgent: fails Core Web Vitals for real visitors. 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
81BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 2.0 s |
| May 9, 2026 | 2.0 s |
| May 16, 2026 | 2.1 s |
| May 23, 2026 | 2.3 s |
| May 30, 2026 | 2.4 s |
| Jun 6, 2026 | 2.4 s |
| Jun 13, 2026 | 2.2 s |
| Jun 20, 2026 | 2.0 s |
| Jun 27, 2026 | 2.0 s |
| Jul 4, 2026 | 2.1 s |
| Jul 11, 2026 | 2.1 s |
| Jul 18, 2026 | 2.3 s |
| Jul 25, 2026 | 2.2 s |
| Aug 1, 2026 | 2.2 s |
| Aug 8, 2026 | 2.2 s |
| Aug 15, 2026 | 2.2 s |
| Aug 22, 2026 | 2.3 s |
| Aug 29, 2026 | 2.4 s |
| Sep 5, 2026 | 2.4 s |
| Sep 12, 2026 | 2.3 s |
| Sep 19, 2026 | 2.4 s |
| Sep 26, 2026 | 2.3 s |
| Oct 3, 2026 | 2.5 s |
| Oct 10, 2026 | 2.4 s |
| Oct 17, 2026 | 2.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 85 ms |
| May 9, 2026 | 86 ms |
| May 16, 2026 | 86 ms |
| May 23, 2026 | 86 ms |
| May 30, 2026 | 86 ms |
| Jun 6, 2026 | 83 ms |
| Jun 13, 2026 | 85 ms |
| Jun 20, 2026 | 95 ms |
| Jun 27, 2026 | 94 ms |
| Jul 4, 2026 | 95 ms |
| Jul 11, 2026 | 94 ms |
| Jul 18, 2026 | 87 ms |
| Jul 25, 2026 | 85 ms |
| Aug 1, 2026 | 81 ms |
| Aug 8, 2026 | 81 ms |
| Aug 15, 2026 | 83 ms |
| Aug 22, 2026 | 86 ms |
| Aug 29, 2026 | 87 ms |
| Sep 5, 2026 | 86 ms |
| Sep 12, 2026 | 86 ms |
| Sep 19, 2026 | 81 ms |
| Sep 26, 2026 | 81 ms |
| Oct 3, 2026 | 85 ms |
| Oct 10, 2026 | 87 ms |
| Oct 17, 2026 | 88 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.0 s
2.0 s
3.0 s
4.0 s
5.0 s
5.9 s
6.9 s
7.9 s
Speed
8 third-party services on the page
8 third-party services load with your homepage (Key CDN, Google Tag Manager and Wistia and others), adding 1.4 MB and 985 ms of main-thread time.
Mobile performance score: 64
64/100Your mobile performance score is 64 (desktop: 85). Pages that score under 90 lose visitors before the first paint.
Use efficient cache lifetimes
750 ms · 196 KiB18 files are served with short cache lifetimes, so returning visitors download them again (196 KiB).
Reduce unused JavaScript
450 ms · 488 KiBAbout 488 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.
Render-blocking requests
450 ms3 files block the first paint until they finish downloading. Deferring or inlining them could save about 450 ms.
Google Tag Manager adds 285 ms
285 msGoogle Tag Manager costs a phone 285 ms of main-thread work and 531 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.
Key CDN adds 304 ms
304 msKey CDN costs a phone 304 ms of main-thread work and 84 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.
Main-thread work: 2.2 s
A phone's processor spends 2.2 s on main-thread work while loading, 1.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Wistia adds 145 ms
145 msWistia costs a phone 145 ms of main-thread work and 349 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.
Improve image delivery
150 ms · 240 KiB4 images could be 240 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.
Reduce unused CSS
150 ms · 19 KiBAbout 19 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
Legacy JavaScript
150 ms · 12 KiBPolyfills for old browsers add 12 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
6 long tasks on the main thread
6 long tasks block the main thread while loading, the longest for 117 ms. During a long task the page ignores taps.
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
3 KiB3 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 2 ms
2 msYour server sent the HTML in 2 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.
Speed Index: 11.5 s
11.5 sVisually, the page fills in at 11.5 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 14.4 s
14.4 sThe page becomes fully interactive after 14.4 s. Good is under 3.8 s.
Largest Contentful Paint: 5.4 s
5.4 sYour largest element takes 5.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Ever Green Eye Doctor Group Picture”. Most of its time is resource load delay (5.7 s).
Real-user LCP: 3.4 s
3.4 sReal visitors wait 3.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user TTFB: 1.2 s
1.2 sReal visitors wait 1.2 s for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 3.0 s
3.0 sThe first text or image appears after 3.0 s on a phone. Good is under 1.8 s.
6 images without width and height
6 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+2%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 85 ms to 88 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 13% slower for real visitors
+13%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 2.0 s to 2.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user INP: 75 ms
75 msReal visitors wait 75 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.6 s
1.6 sReal visitors see the first content after 1.6 s (75th percentile). Good is under 1.8 s.
Total Blocking Time: 130 ms
130 msScripts block the page for only 130 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0.065
0.065The layout barely moves while loading (CLS 0.065, good is under 0.1).
Images and page weight
5 images in older formats
5 images (340 KiB) 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.
1 image below the first screen load straight away
1 image further down the page (174 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 0.5 g of CO₂ per visit
0.55 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.55 g of CO₂e: 65.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Page weight: 1.9 MB in 128 requests
1.9 MBYour homepage downloads 1.9 MB in 128 requests on a phone: scripts 1.4 MB (33), images 410 KiB (31) and other files 51 KiB (57). That is a lean page.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
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.
ARIA roles used must conform to valid values (1 element)
ARIA roles used must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.
10 text elements with low contrast
10 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 (30 elements)
All page content should be contained by landmarks: 30 elements on the page fail this check, rated moderate by axe-core.
2 links without text
2 visible links have no text or label, so screen readers cannot say where they go.
2 checks passed
Every image has alt text
All 15 images in the HTML carry an alt attribute.
38 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 43 WCAG 2.2 A/AA and best-practice rules on the phone render: 38 passed and 5 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Structured data has 1 problem
Structured data found (BreadcrumbList, Organization, WebPage and WebSite) but with 1 problem, for example “ld+json block 1 is not valid JSON (Unexpected non-whitespace character after JSON at position 1)”.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
6 links crawlers can't follow
6 links have no real href, so search engines can't follow them.
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.
176 internal links, 6 external
The homepage links to 176 pages on evergreeneye.com and 6 external pages.
6 checks passed
Meta description: 151 characters
Your meta description is 151 characters: “The eye doctors and ophthalmologists at Evergreen provide expert LASIK, cataracts, and eye care services to patients in…”.
One H1 headline
Your main headline reads: “Welcome to Evergreen Eye Center”.
Title: 49 characters
Your title is a healthy 49 characters: “LASIK Seattle | Eye Doctor Tacoma | Evergreen Eye”.
Canonical URL set
The canonical URL is https://www.evergreeneye.com/.
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.evergreeneye.com/sitemap_index.xml.
AI search readiness
No llms.txt
There is no https://www.evergreeneye.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,251 words), so crawlers that don't run JavaScript still read it.
Other pages
4 linked pages hidden from search
https://www.evergreeneye.com/about, https://www.evergreeneye.com/about/why-evergreen, https://www.evergreeneye.com/about/innovation-technology and https://www.evergreeneye.com/about/patient-testimonials are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.
11 pages slow to respond
https://www.evergreeneye.com/about/blog, https://www.evergreeneye.com/about/review-us, https://www.evergreeneye.com/about/patient-testimonials, https://www.evergreeneye.com/eye-doctor-seattle, https://www.evergreeneye.com/eye-doctor-seattle/robert-a-tester-md and https://www.evergreeneye.com/eye-doctor-seattle/gary-w-chung-md 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 68 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.
Every page has a meta description
All 15 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.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.
3 low-resolution images
3 images are served at too low a resolution for sharp phone screens.
2 checks passed
Tap targets are thumb-sized
18 of 18 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
Thin social proof
Social proof on the homepage: 2 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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 801 words of copy
The homepage carries about 801 words of visible text.
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “SCHEDULE ONLINE”.
20 calls to action
The homepage has 20 calls to action, for example “Request Appointment”, “book online” and “Schedule An Appointment”.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics and Meta Pixel.
Direct contact links
Visitors can reach you directly: 6 phone links and 0 email links.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and The Trade Desk (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.
12 cookies set on arrival
12Opening the homepage sets 12 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.
25 other companies contacted
Loading the homepage contacts 25 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 evergreeneye.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
- Framework
- jQuery
- Analytics
- Google 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 31 issues on evergreeneye.com, including 17 speed issues, 4 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.