Website review, no card needed

localedge.com logo

localedge.com website review

Visit site (opens in a new tab)Reviewed 4 November 202624 issues · 72 checks

This review found 24 issues worth fixing on localedge.com, 6 of them high impact, across 72 checks. The most urgent: input buttons must have discernible text (1 element). 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
1.9 s1.3 sMay 16Oct 311.8 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.7 s
May 23, 20261.6 s
May 30, 20261.6 s
Jun 6, 20261.6 s
Jun 13, 20261.5 s
Jun 20, 20261.5 s
Jun 27, 20261.5 s
Jul 4, 20261.5 s
Jul 11, 20261.6 s
Jul 18, 20261.7 s
Jul 25, 20261.9 s
Aug 1, 20261.9 s
Aug 8, 20261.8 s
Aug 15, 20261.6 s
Aug 22, 20261.4 s
Aug 29, 20261.5 s
Sep 5, 20261.5 s
Sep 12, 20261.4 s
Sep 19, 20261.4 s
Sep 26, 20261.5 s
Oct 3, 20261.6 s
Oct 10, 20261.7 s
Oct 17, 20261.7 s
Oct 24, 20261.8 s
Oct 31, 20261.8 s
Real-visitor tap response (INP)75th percentile, phones
80 ms62 msMay 16Oct 3164 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 202669 ms
May 23, 202669 ms
May 30, 202669 ms
Jun 6, 202668 ms
Jun 13, 202669 ms
Jun 20, 202669 ms
Jun 27, 202670 ms
Jul 4, 202673 ms
Jul 11, 202677 ms
Jul 18, 202678 ms
Jul 25, 202678 ms
Aug 1, 202672 ms
Aug 8, 202672 ms
Aug 15, 202672 ms
Aug 22, 202671 ms
Aug 29, 202671 ms
Sep 5, 202671 ms
Sep 12, 202672 ms
Sep 19, 202675 ms
Sep 26, 202673 ms
Oct 3, 202675 ms
Oct 10, 202671 ms
Oct 17, 202666 ms
Oct 24, 202664 ms
Oct 31, 202664 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 localedge.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. localedge.com at 0.4 s0.4 s
  2. localedge.com at 0.8 s0.8 s
  3. localedge.com at 1.1 s1.1 s
  4. localedge.com at 1.5 s1.5 s
  5. localedge.com at 1.9 s1.9 s
  6. localedge.com at 2.3 s2.3 s
  7. localedge.com at 2.6 s2.6 s
  8. localedge.com at 3.0 s3.0 s

Speed

3 to fix97
  • Render-blocking requests

    900 ms

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

  • Use efficient cache lifetimes

    300 ms · 278 KiB

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

  • Improve image delivery

    300 ms · 69 KiB

    1 image could be 69 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.

  • 5 third-party services on the page

    5 third-party services load with your homepage (Google Tag Manager, jQuery CDN and JSDelivr CDN and others), adding 243 KiB and 213 ms of main-thread time.

  • 2 long tasks on the main thread

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

  • Reduce unused JavaScript

    68 KiB

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

  • Reduce unused CSS

    21 KiB

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

3 checks passed
  • Mobile performance score: 97

    97/100

    Your mobile performance score is 97. That is in Google's “good” band (90 and up).

  • Main-thread work: 0.3 s

    A phone's processor spends 0.3 s on main-thread work while loading, 148 ms of it running JavaScript. That is comfortably low.

  • Server response: 1 ms

    1 ms

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

Core Web Vitals

1 to fix100
  • 1 image without width and height

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

  • Tap response (INP) held steady for real visitors

    -7%

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

  • Largest content (LCP) held steady for real visitors

    +6%

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

12 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: 1.8 s

    1.8 s

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

  • Real-user INP: 69 ms

    69 ms

    Real visitors wait 69 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.7 s

    1.7 s

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

  • Real-user TTFB: 656 ms

    656 ms

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

  • Time to Interactive: 3.7 s

    3.7 s

    The page is fully interactive after 3.7 s.

  • Largest Contentful Paint: 2.4 s

    2.4 s

    Your largest element renders in 2.4 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the element shown below.

  • First Contentful Paint: 1.7 s

    1.7 s

    The first text or image appears after 1.7 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0.001

    0.001

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

  • Speed Index: 1.7 s

    1.7 s

    Visually, the page fills in at 1.7 s (Speed Index), inside the 3.4 s “good” threshold.

  • Total Blocking Time: 60 ms

    60 ms

    Scripts block the page for only 60 ms while loading. Good is under 200 ms.

Images and page weight

1 to fix90
  • 1 image far larger than shown

    67 KiB

    1 image is downloaded at several times the size a phone draws it, for example logo.png at 3,000 px wide, shown at 200 px. Resized copies would save about 67 KiB.

  • 2 images in older formats

    2 images (257 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.

  • About 0.1 g of CO₂ per visit

    0.15 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.15 g of CO₂e: 17.5 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: 526 KiB in 19 requests

    526 KiB

    Your homepage downloads 526 KiB in 19 requests on a phone: images 276 KiB (9), scripts 206 KiB (4) and stylesheets 26 KiB (3). That is a lean page.

  • Images load when needed

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

Accessibility

8 to fixGoogle 8487
  • Input buttons must have discernible text (1 element)

    Input buttons must have discernible text: 1 element on the page fails this check, rated critical by axe-core.

  • 15 tap targets too small

    15 tap targets are too small or too close together to hit reliably with a finger.

  • 4 images without alt text

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

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

    All page content should be contained by landmarks: 2 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.

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • 7 form fields without a label

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

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

1 checks passed
  • 34 automated accessibility rules passed

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

SEO

5 to fixGoogle 10078
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Meta description is long (199 characters)

    Your meta description is 199 characters; Google truncates after about 160, so the end of your pitch is cut.

  • No XML sitemap

    No XML sitemap at https://localedge.com/sitemap.xml, so Google discovers your pages only by following links.

  • Only 1 internal link

    The homepage links to only 1 page on your own site, so visitors and crawlers find few routes into the rest of it.

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

5 checks passed
  • Title: 37 characters

    Your title is a healthy 37 characters: “LocalEdge: Digital Marketing Services”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: ProfessionalService.

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

AI search readiness

100
  • No llms.txt

    There is no https://localedge.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.

  • Organization data: 5 of 6 facts

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

Best practices

2 to fixGoogle 10087
  • 15 small tap targets

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

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_TUNNEL_CONNECTION_FAILED”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • Only about 102 words

    The homepage has only about 102 words of visible text; thin pages give Google and first-time buyers little to go on.

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

6 checks passed
  • 1 call to action

    The homepage has 1 call to action, for example “Contact Us”.

  • 2 short forms

    2 short forms (5 fields at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Analytics.

  • Opening hours shown

    Your opening hours are on the homepage.

  • Phone number on the homepage

    Your phone number is on the homepage.

  • LocalBusiness structured data

    Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.

Privacy and tracking

1 to fix
  • 1 tracker load before any consent

    1

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

  • 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 localedge.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
jQuery
Analytics
Google Analytics
Hosting
Azure

Company

Headquarters
Buffalo

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 24 issues on localedge.com, including 4 speed issues, 5 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