freddy.ie website review

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

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

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

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

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

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

Mailchimp costs a phone 259 ms of main-thread work and 176 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.

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

6 third-party services load with your homepage (Mailchimp, Google CDN and Shopify and others), adding 448 KiB and 429 ms of main-thread time.

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

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

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

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

9 KiB JavaScript is shipped twice across bundles.

6 KiB could be saved by minifying JavaScript.

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.

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

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

Your largest element takes 3.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Models wearing Freddy WR.UP metallic shaping leggings, 50% …”.

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

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

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

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

3 elements hidden from screen readers can still receive keyboard focus.

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

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 on the page fails this check, rated moderate by axe-core.

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

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

Elements with visible text labels do not have matching accessible names. (24 elements).

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

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

The homepage links to 475 pages on freddy.ie and 16 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.

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

Social proof on the homepage: a star rating. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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 608 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and TikTok Pixel (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 15 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 23 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.