localdialog.com website review

About 1.3 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 7.1 s faster on a phone.

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

9 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 900 ms faster on a phone.

5 third-party services load with your homepage (apigateway.co, JSDelivr CDN and Stripe and others), adding 6.4 MB and 620 ms of main-thread time.

Your mobile performance score is 61. Pages that score under 90 lose visitors before the first paint.

apigateway.co costs a phone 300 ms of main-thread work and 1.6 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.

ghost.io costs a phone 0 ms of main-thread work and 4.0 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.

JSDelivr CDN costs a phone 166 ms of main-thread work and 556 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.

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

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

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

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

6 KiB JavaScript is shipped twice across bundles.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

Your largest element takes 19.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Answering your 'local' questions with unique data & insights”.

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

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

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

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

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

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.

Your homepage downloads 6.5 MB in 59 requests on a phone: images 4.0 MB (10), scripts 2.4 MB (24) and other files 74 KiB (16). Under 2 MB keeps phones on slow connections fast.

6 images (940 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 is downloaded at several times the size a phone draws it, for example dialogo-only.png at 1,600 px wide, shown at 56 px. Resized copies would save about 77 KiB.

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

4 buttons have no accessible name, so screen readers announce just “button”.

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

Elements must only use permitted ARIA attributes: 1 element on the page fails this check, rated serious by axe-core.

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

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

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

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

The homepage links to 100 pages on localdialog.com and 1 external page.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

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

https://www.localdialog.com/membership, https://www.localdialog.com/research, https://www.localdialog.com/contact, https://www.localdialog.com/about and https://www.localdialog.com/dax-your-local-data-expert have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.localdialog.com/ai-shopping-listicle-love-chatgpt-yelp-only-6-hollywoods-ai-future and https://www.localdialog.com/ranking-factors-let-google-call-openai-spending-ai-visibility-trade-school use the same meta description. A description written for each page earns more clicks.

https://www.localdialog.com/contact has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

We fetched 15 pages linked from your homepage (of 87 found) and read each the way a search engine does.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 906 words of visible text.

Opening the homepage sets 4 cookies (measured from a US location before any click).

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.

Loading the homepage contacts 11 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.