Website review, no card needed

wilmingtoneye.com logo

wilmingtoneye.com website review

Visit site (opens in a new tab)Reviewed 19 October 202629 issues · 84 checks

This review found 29 issues worth fixing on wilmingtoneye.com, 14 of them high impact, across 84 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
2.3 s1.6 sApr 25Oct 101.9 s
Show as table
DateReal-visitor load time (LCP)
Apr 25, 20262.1 s
May 2, 20262.1 s
May 9, 20262.1 s
May 16, 20262.1 s
May 23, 20262.1 s
May 30, 20262.2 s
Jun 6, 20262.1 s
Jun 13, 20262.1 s
Jun 20, 20262.1 s
Jun 27, 20262.2 s
Jul 4, 20262.2 s
Jul 11, 20262.2 s
Jul 18, 20262.1 s
Jul 25, 20262.0 s
Aug 1, 20261.9 s
Aug 8, 20261.8 s
Aug 15, 20261.8 s
Aug 22, 20261.7 s
Aug 29, 20261.7 s
Sep 5, 20261.8 s
Sep 12, 20261.8 s
Sep 19, 20262.0 s
Sep 26, 20262.0 s
Oct 3, 20261.9 s
Oct 10, 20261.9 s
Real-visitor tap response (INP)75th percentile, phones
84 ms77 msApr 25Oct 1082 ms
Show as table
DateReal-visitor tap response (INP)
Apr 25, 202681 ms
May 2, 202679 ms
May 9, 202679 ms
May 16, 202682 ms
May 23, 202681 ms
May 30, 202680 ms
Jun 6, 202680 ms
Jun 13, 202679 ms
Jun 20, 202680 ms
Jun 27, 202683 ms
Jul 4, 202680 ms
Jul 11, 202680 ms
Jul 18, 202680 ms
Jul 25, 202679 ms
Aug 1, 202679 ms
Aug 8, 202679 ms
Aug 15, 202679 ms
Aug 22, 202679 ms
Aug 29, 202678 ms
Sep 5, 202679 ms
Sep 12, 202681 ms
Sep 19, 202682 ms
Sep 26, 202683 ms
Oct 3, 202683 ms
Oct 10, 202682 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 wilmingtoneye.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. wilmingtoneye.com at 0.6 s0.6 s
  2. wilmingtoneye.com at 1.2 s1.2 s
  3. wilmingtoneye.com at 1.8 s1.8 s
  4. wilmingtoneye.com at 2.4 s2.4 s
  5. wilmingtoneye.com at 3.0 s3.0 s
  6. wilmingtoneye.com at 3.6 s3.6 s
  7. wilmingtoneye.com at 4.2 s4.2 s
  8. wilmingtoneye.com at 4.7 s4.7 s

Speed

9 to fix36
  • Improve image delivery

    19.7 s · 3.6 MB

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

  • Reduce unused JavaScript

    6.2 s · 869 KiB

    About 869 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 6.2 s faster on a phone.

  • Render-blocking requests

    3.3 s

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

  • Use efficient cache lifetimes

    1.1 s · 180 KiB

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

  • Mobile performance score: 36

    36/100

    Your mobile performance score is 36 (desktop: 39). 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 Tag Manager, Google CDN and Facebook and others), adding 1.9 MB and 1.5 s of main-thread time.

  • Google Tag Manager adds 635 ms

    635 ms

    Google Tag Manager costs a phone 635 ms of main-thread work and 897 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 CDN adds 459 ms

    459 ms

    Google CDN costs a phone 459 ms of main-thread work and 733 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: 3.6 s

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

  • Reduce unused CSS

    170 ms · 86 KiB

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

  • 17 long tasks on the main thread

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

  • Legacy JavaScript

    200 ms · 12 KiB

    Polyfills for old browsers add 12 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 200 ms faster on a phone.

  • Font display

    50 ms

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

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

  • Minify JavaScript

    2 KiB

    2 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 10 ms

    10 ms

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

Core Web Vitals

6 to fix100
  • First Contentful Paint: 10.6 s

    10.6 s

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

  • Largest Contentful Paint: 40.2 s

    40.2 s

    Your largest element takes 40.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

  • Speed Index: 17.3 s

    17.3 s

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

  • Time to Interactive: 40.2 s

    40.2 s

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

  • Total Blocking Time: 766 ms

    766 ms

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

  • 3 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +3%

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

  • Largest content (LCP) held steady for real visitors

    -8%

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

7 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: 2.0 s

    2.0 s

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

  • Real-user INP: 79 ms

    79 ms

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

  • Real-user CLS: 0.01

    0.01

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

  • Real-user FCP: 1.3 s

    1.3 s

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

  • Real-user TTFB: 539 ms

    539 ms

    Real visitors wait 539 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).

Images and page weight

5 to fix18
  • Page weight: 11.8 MB in 92 requests

    11.8 MB

    Your homepage downloads 11.8 MB in 92 requests on a phone: media 4.8 MB (2), images 4.3 MB (12) and scripts 1.9 MB (35). Under 2 MB keeps phones on slow connections fast.

  • 3 images over 500 KB

    3 images weigh 4.1 MB together. On a phone connection a single image that size takes seconds.

  • 3 images far larger than shown

    2.0 MB

    3 images are downloaded at several times the size a phone draws them, for example surfer.png at 1,182 px wide, shown at 208 px. Resized copies would save about 2.0 MB.

  • 4 images in older formats

    4 images (4.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.

  • 3 images below the first screen load straight away

    3 images further down the page (3.7 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.34 g

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

Accessibility

3 to fixGoogle 9796
  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

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

  • 3 form fields without a label

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

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (1 element).

2 checks passed
  • Every image has alt text

    All 5 images in the HTML carry an alt attribute.

  • 48 automated accessibility rules passed

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

SEO

Google 100100
  • 113 internal links, 14 external

    The homepage links to 113 pages on wilmingtoneye.com and 14 external pages.

8 checks passed
  • Meta description: 147 characters

    Your meta description is 147 characters: “Our team of board-certified ophthalmologists focus on every patient, working ogether to provide the highest standard of…”.

  • One H1 headline

    Your main headline reads: “Wilmington Eye, your area's most comprehensive eye care”.

  • Title: 47 characters

    Your title is a healthy 47 characters: “Ophthalmologist Wilmington, NC | Wilmington Eye”.

  • Canonical URL set

    The canonical URL is https://wilmingtoneye.com/.

  • Structured data in place

    Structured data found: BreadcrumbList, MedicalOrganization, 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://wilmingtoneye.com/sitemap.xml.

AI search readiness

100
4 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: 6 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.

  • Text is in the HTML

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

  • llms.txt published

    The site publishes https://wilmingtoneye.com/llms.txt (195 KiB, 513 links, though it should open with a “# Title” line), a plain-text guide to the site for AI tools.

Other pages

1 to fix95
  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://wilmingtoneye.com/appointment, whose canonical is https://wilmingtoneye.com/make-an-appointment. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 40 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.

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

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9687
  • 4 small tap targets

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

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix88
  • 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: 38 testimonial or review blocks. 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 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 1,479 words of copy

    The homepage carries about 1,479 words of visible text.

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

6 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Click Here to Learn More”.

  • 6 calls to action

    The homepage has 6 calls to action, for example “Optical Shop”, “Contact” and “Subscribe”.

  • 1 short form

    A short form (2 fields at most) is right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

  • Direct contact links

    Visitors can reach you directly: 2 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

1 to fix
  • 5 trackers load before any consent

    5

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Clarity (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.

  • 10 cookies set on arrival

    10

    Opening the homepage sets 10 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.

  • 20 other companies contacted

    Loading the homepage contacts 20 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 wilmingtoneye.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 29 issues on wilmingtoneye.com, including 15 speed 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

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