dailygreatnessjournal.com website review

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

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

8 third-party services load with your homepage (Google Tag Manager, convertflow.co and Cloudflare CDN and others), adding 749 KiB and 624 ms of main-thread time.

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

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

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

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

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

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

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

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 KiB could be saved by minifying CSS.

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

Your largest element takes 5.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Unleash your inner warrior and defeat overwhelm for good.”.

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

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

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

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 2.9 MB in 201 requests on a phone: images 1.1 MB (55), scripts 1,022 KiB (55) and other files 644 KiB (76). Under 2 MB keeps phones on slow connections fast.

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

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

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

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

[role="img"] and [role="image"] elements must have alternative text: 3 elements on the page fail this check, rated serious by axe-core.

Form elements should have a visible label: 2 elements on the page fail this check, rated serious by axe-core.

Interactive controls must not be nested: 2 elements on the page fail this check, rated serious by axe-core.

Some lists contain elements other than list items, which screen readers announce wrongly.

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

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.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

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

Alternative text of images should not be repeated as text: 10 elements on the page fail this check, rated minor by axe-core.

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

Your title is only 26 characters: “Dailygreatness UK & Europe”. Between 30 and 65 characters leaves room to say what you do and for whom.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

2 links have no real href, so search engines can't follow them.

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

The homepage links to 54 pages on dailygreatnessjournal.com and 6 external pages.

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://dailygreatness.co.uk/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://dailygreatness.co.uk/collections/rocking-fit has no meta description, so Google writes the search snippet from whatever text it finds.

https://dailygreatness.co.uk/collections/rocking-fit 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 32 found) and read each the way a search engine does.

1 image failed to load on a phone, for example https://lantern.roeye.com/track.php?fingerprint=8a18ffd9-3ace-4562-b527-198b3a7ad152&referrer=&landingpage=https%3A%2F%2Fdailygreatness.co.uk%2F&useragent=Mozilla%2F5.0%20(iPhone%3B%20CPU%20iPhone%20O.

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

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

The homepage carries about 892 words of visible text.

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

Opening the homepage sets 25 cookies, 4 of them by other companies (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 40 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.