Website review, no card needed

locateinlexington.com logo

locateinlexington.com website review

Visit site (opens in a new tab)Reviewed 6 November 202633 issues · 82 checks

This review found 33 issues worth fixing on locateinlexington.com, 12 of them high impact, across 82 checks. The most urgent: render-blocking requests. 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

Full-page screenshot of locateinlexington.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. locateinlexington.com at 0.9 s0.9 s
  2. locateinlexington.com at 1.8 s1.8 s
  3. locateinlexington.com at 2.7 s2.7 s
  4. locateinlexington.com at 3.6 s3.6 s
  5. locateinlexington.com at 4.5 s4.5 s
  6. locateinlexington.com at 5.5 s5.5 s
  7. locateinlexington.com at 6.4 s6.4 s
  8. locateinlexington.com at 7.3 s7.3 s

Speed

10 to fix37
  • Render-blocking requests

    2.8 s

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

  • Main-thread work: 10.7 s

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

  • Mobile performance score: 37

    37/100

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

  • 4,726 HTML elements

    The page has 4,726 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • 7 third-party services on the page

    7 third-party services load with your homepage (Google Tag Manager, Vimeo and Unpkg and others), adding 18.8 MB and 932 ms of main-thread time.

  • Vimeo adds 323 ms

    323 ms

    Vimeo costs a phone 323 ms of main-thread work and 18.2 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.

  • 20 long tasks on the main thread

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

  • Reduce unused JavaScript

    616 KiB

    About 616 KiB of JavaScript is downloaded but never used on this page.

  • Google Tag Manager adds 398 ms

    398 ms

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

  • Reduce unused CSS

    300 ms · 95 KiB

    About 95 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.

  • Improve image delivery

    154 KiB

    3 images could be 154 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Font display

    100 ms

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

  • Use efficient cache lifetimes

    67 KiB

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

  • Legacy JavaScript

    12 KiB

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

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

    40 ms

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

Core Web Vitals

6 to fix38
  • Speed Index: 15.4 s

    15.4 s

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

  • Time to Interactive: 34.8 s

    34.8 s

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

  • Cumulative Layout Shift: 0.847

    0.847

    The layout shifts by 0.847 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Total Blocking Time: 1.3 s

    1.3 s

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

  • First Contentful Paint: 2.3 s

    2.3 s

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

  • 9 images without width and height

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

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

1 checks passed
  • Largest Contentful Paint: 2.3 s

    2.3 s

    Your largest element renders in 2.3 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Unlock the potential of Greater Lexington”.

Images and page weight

1 to fix70
  • Page weight: 26.0 MB in 335 requests

    26.0 MB

    Your homepage downloads 26.0 MB in 335 requests on a phone: other files 17.7 MB (30), images 5.8 MB (159) and scripts 1.5 MB (67). Under 2 MB keeps phones on slow connections fast.

  • About 7.4 g of CO₂ per visit

    7.36 g

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

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

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

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

6 to fixGoogle 8893
  • Certain ARIA roles must contain particular children (3 elements)

    Certain ARIA roles must contain particular children: 3 elements on the page fail this check, rated critical by axe-core.

  • 3 text elements with low contrast

    3 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 (191 elements)

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

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

  • The skip-link target should exist and be focusable (1 element)

    The skip-link target should exist and be focusable: 1 element on the page fails this check, rated moderate by axe-core.

  • 11 links without text

    11 visible links have no text or label, so screen readers cannot say where they go.

  • Headings skip levels

    Headings skip levels (h1 → h5, h3 → h6 and h1 → h6), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 31 images in the HTML carry an alt attribute.

  • 50 automated accessibility rules passed

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

SEO

2 to fixGoogle 9293
  • 10 H1 headlines

    There are 10 <h1> headlines (“Unlock the potential of Greater Lexington”, “Franklin” and “Scott”). One clear main headline is easier for people and search engines.

  • 19 links with vague text

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

  • 169 internal links, 30 external

    The homepage links to 169 pages on locateinlexington.com and 30 external pages.

7 checks passed
  • Meta description: 160 characters

    Your meta description is 160 characters: “The region’s vibrant communities, thriving industries, and rich cultural heritage come together to create an environmen…”.

  • Title: 61 characters

    Your title is a healthy 61 characters: “Greater Lexington | Unlock the potential of Greater Lexington”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: Organization, Person 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.

  • XML sitemap found

    Your XML sitemap is reachable at https://locateinlexington.com/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://locateinlexington.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: 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 (3,067 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix90
  • 6 pages without a meta description

    https://locateinlexington.com/get-the-data, https://locateinlexington.com/industry/agtech, https://locateinlexington.com/industry/biotech-biopharma, https://locateinlexington.com/industry/business-financial-services, https://locateinlexington.com/industry/food-and-beverage-processing and https://locateinlexington.com/industry/logistics have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages without an H1

    https://locateinlexington.com/get-the-data and https://locateinlexington.com/business-services/lexington-economic-partnership 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 29 found) and read each the way a search engine does.

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

  • 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 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 5894
  • 2 third-party cookies

    2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix75
  • 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.

  • Thin social proof

    Social proof on the homepage: 6 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,817 words of copy

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

5 checks passed
  • 36 calls to action

    The homepage has 36 calls to action, for example “Contact Us”, “Learn More” and “Contact”.

  • 2 short forms

    2 short forms (2 fields at most) are right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Analytics and Matomo.

  • Direct contact links

    Visitors can reach you directly: 3 phone links and 3 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
  • 2 trackers load before any consent

    2

    Before a visitor clicks anything, the page loads 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.

  • 5 cookies set on arrival

    5

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

  • 9 other companies contacted

    Loading the homepage contacts 9 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 locateinlexington.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
Framework
jQuery
Analytics
Google Analytics | Matomo
Hosting
ReliableSite.Net LLC

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 33 issues on locateinlexington.com, including 16 speed issues, 2 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

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