Website review, no card needed

lodenvision.com logo

lodenvision.com website review

Visit site (opens in a new tab)Reviewed 23 October 202629 issues · 83 checks

This review found 29 issues worth fixing on lodenvision.com, 14 of them high impact, across 83 checks. The most urgent: reduce unused JavaScript. 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.8 sMay 2Oct 171.9 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20262.0 s
May 9, 20262.1 s
May 16, 20262.1 s
May 23, 20262.1 s
May 30, 20262.1 s
Jun 6, 20262.1 s
Jun 13, 20262.1 s
Jun 20, 20262.2 s
Jun 27, 20262.2 s
Jul 4, 20262.2 s
Jul 11, 20262.1 s
Jul 18, 20262.0 s
Jul 25, 20261.9 s
Aug 1, 20261.8 s
Aug 8, 20261.8 s
Aug 15, 20261.9 s
Aug 22, 20262.0 s
Aug 29, 20262.0 s
Sep 5, 20262.1 s
Sep 12, 20261.9 s
Sep 19, 20261.9 s
Sep 26, 20261.9 s
Oct 3, 20261.9 s
Oct 10, 20261.9 s
Oct 17, 20261.9 s
Real-visitor tap response (INP)75th percentile, phones
145 ms74 msMay 2Oct 1784 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 202684 ms
May 9, 202686 ms
May 16, 202686 ms
May 23, 202683 ms
May 30, 202682 ms
Jun 6, 202688 ms
Jun 13, 202698 ms
Jun 20, 202699 ms
Jun 27, 202699 ms
Jul 4, 2026103 ms
Jul 11, 2026105 ms
Jul 18, 2026113 ms
Jul 25, 2026122 ms
Aug 1, 2026127 ms
Aug 8, 2026127 ms
Aug 15, 2026136 ms
Aug 22, 2026137 ms
Aug 29, 2026136 ms
Sep 5, 2026137 ms
Sep 12, 2026117 ms
Sep 19, 2026114 ms
Sep 26, 2026104 ms
Oct 3, 202696 ms
Oct 10, 202692 ms
Oct 17, 202684 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 lodenvision.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. lodenvision.com at 0.5 s0.5 s
  2. lodenvision.com at 1.1 s1.1 s
  3. lodenvision.com at 1.6 s1.6 s
  4. lodenvision.com at 2.1 s2.1 s
  5. lodenvision.com at 2.6 s2.6 s
  6. lodenvision.com at 3.2 s3.2 s
  7. lodenvision.com at 3.7 s3.7 s
  8. lodenvision.com at 4.2 s4.2 s

Speed

8 to fix36
  • Reduce unused JavaScript

    2.5 s · 593 KiB

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

  • Mobile performance score: 36

    36/100

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

  • Main-thread work: 4.6 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Wistia and Facebook and others), adding 3.0 MB and 1.8 s of main-thread time.

  • Google Tag Manager adds 772 ms

    772 ms

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

  • Wistia adds 577 ms

    577 ms

    Wistia costs a phone 577 ms of main-thread work and 2.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.

  • Use efficient cache lifetimes

    300 ms · 383 KiB

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

  • Improve image delivery

    300 ms · 152 KiB

    6 images could be 152 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.

  • 19 long tasks on the main thread

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

  • Render-blocking requests

    150 ms

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

  • Font display

    50 ms

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

  • Reduce unused CSS

    33 KiB

    About 33 KiB of CSS is downloaded but never applied on this page.

  • Legacy JavaScript

    20 KiB

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

  • Phones get a much slower page than desktops

    Desktop scores 86 but mobile only 36. A gap that wide usually means heavy scripts and images that hit phones hardest.

  • 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: 12 ms

    12 ms

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

Core Web Vitals

8 to fix100
  • 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.

  • Largest Contentful Paint: 21.3 s

    21.3 s

    Your largest element takes 21.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “NASHVILLE’S EXPERTS IN VISION CORRECTION & CATARACT SURGERY”.

  • Time to Interactive: 21.5 s

    21.5 s

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

  • First Contentful Paint: 5.0 s

    5.0 s

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

  • Speed Index: 9.3 s

    9.3 s

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

  • Total Blocking Time: 975 ms

    975 ms

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

  • Real-user TTFB: 946 ms

    946 ms

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

  • 19 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +4%

    Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 84 ms to 84 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-17, real Chrome visitors' largest content (lcp) went from 2.0 s to 1.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

5 checks passed
  • Real-user LCP: 1.9 s

    1.9 s

    Real visitors wait 1.9 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.00

    0.00

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

  • Real-user FCP: 1.4 s

    1.4 s

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

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

2 to fix50
  • Page weight: 4.4 MB in 149 requests

    4.4 MB

    Your homepage downloads 4.4 MB in 149 requests on a phone: images 2.6 MB (33), scripts 1.6 MB (41) and fonts 129 KiB (8). Under 2 MB keeps phones on slow connections fast.

  • 3 images far larger than shown

    522 KiB

    3 images are downloaded at several times the size a phone draws them, for example self-test-icon.svg at 150 px wide, shown at 30 px. Resized copies would save about 522 KiB.

  • 1 image in older formats

    1 image (40 KiB) is 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.

  • About 1.3 g of CO₂ per visit

    1.25 g

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

1 checks passed
  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

Accessibility

3 to fixGoogle 9395
  • 16 text elements with low contrast

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

  • 2 images without alt text

    2 images have no alt text, which hurts accessibility and image search.

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

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

1 checks passed
  • 48 automated accessibility rules passed

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

SEO

1 to fixGoogle 8598
  • 5 links with vague text

    5 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 98 internal links, 11 external

    The homepage links to 98 pages on lodenvision.com and 11 external pages.

8 checks passed
  • Meta description: 142 characters

    Your meta description is 142 characters: “Loden Vision Centers offers the most advanced LASIK eye surgery, laser cataract surgery, and high-quality vision care i…”.

  • One H1 headline

    Your main headline reads: “Nashville’s Experts In Vision Correction & Cataract Surgery”.

  • Title: 42 characters

    Your title is a healthy 42 characters: “LASIK Eye Surgery Nashville | Loden Vision”.

  • Canonical URL set

    The canonical URL is https://www.lodenvision.com/.

  • Structured data in place

    Structured data found: BreadcrumbList, MedicalOrganization, MedicalWebPage, Organization and WebPage.

  • 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.lodenvision.com/sitemap_index.xml.

AI search readiness

100
  • No llms.txt

    There is no https://www.lodenvision.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: 5 of 6 facts

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

  • Text is in the HTML

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

Other pages

3 to fix83
  • 4 linked pages hidden from search

    https://www.lodenvision.com/loden-ivision-centers/our-staff, https://www.lodenvision.com/loden-ivision-centers/our-facilities, https://www.lodenvision.com/loden-ivision-centers/careers and https://www.lodenvision.com/loden-ivision-centers/read-our-reviews are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 1 link to non-canonical URLs

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

  • 2 pages without an H1

    https://www.lodenvision.com/patients/schedule-an-appointment and https://www.lodenvision.com/cataracts-nashville have 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 45 found) and read each the way a search engine does.

4 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 a title

    All 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9678
  • 1 broken image

    1 image failed to load on a phone, for example https://jelly.mdhv.io/v1/star.gif?pid=e7HcBq3X2aRx1puYgWkBU50Z1kX8&src=mh&evt=hi.

  • 4 JavaScript errors while loading

    4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 400 ()”.

2 checks passed
  • Tap targets are thumb-sized

    24 of 27 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix94
  • 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 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 1,169 words of copy

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

7 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Click to call” and “SCHEDULE AN APPOINTMENT”.

  • 11 calls to action

    The homepage has 11 calls to action, for example “Book Vision Evaluation”, “Schedule an Appointment” and “Contact”.

  • Social proof on the page

    Social proof on the homepage: 13 testimonial or review blocks and 3 trust badges.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

    Visitors can reach you directly: 9 phone links and 0 email links.

  • Opening hours shown

    Your opening hours are on the homepage.

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

  • 1 cookie set on arrival

    1

    Opening the homepage sets 1 cookie (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.

  • 32 other companies contacted

    Loading the homepage contacts 32 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 lodenvision.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 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 lodenvision.com, including 16 speed issues, 1 SEO issue 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