freshxl.com website review

4 images could be 494 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.5 s faster on a phone.

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

About 52 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.

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

1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 150 ms.

1 file is served with short cache lifetimes, so returning visitors download them again (5 KiB).

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

1 third-party service load with your homepage (Shopify), adding 13 KiB and 4 ms of main-thread time.

Your largest element takes 4.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

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

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.

miami_300x300.gif weighs 549 KiB. On a phone connection a single image that size takes seconds.

2 images (889 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 further down the page (549 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

<dl> elements must only directly contain properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements: 1 element on the page fails this check, rated serious by axe-core.

No meta description, so Google writes its own snippet from whatever text it finds.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

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

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

The homepage links to 24 pages on freshxl.com and 2 external pages.

Your Organization JSON-LD is missing logo, description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

https://freshxl.com/collections/frontpage/products/short-sleeve-t-shirt-1 and https://freshxl.com/collections/frontpage/products/short-sleeve-t-shirt all use the title “Short sleeve t-shirt – FRESH XL”. Search engines can't tell which page to show for a search, so each competes with the others.

https://freshxl.com/collections/frontpage, https://freshxl.com/blogs/news, https://freshxl.com/pages/contact, https://freshxl.com/blogs/news/la-games-conference-vip-edition-skybound and https://freshxl.com/blogs/news/ar-house-closing-party-2022 have no meta description, so Google writes the search snippet from whatever text it finds.

https://freshxl.com/collections/frontpage/products/short-sleeve-t-shirt-1 and https://freshxl.com/collections/frontpage/products/short-sleeve-t-shirt use the same meta description. A description written for each page earns more clicks.

Your homepage links to 3 pages by a URL that isn't their canonical one, for example https://freshxl.com/collections/frontpage/products/short-sleeve-t-shirt-1, whose canonical is https://freshxl.com/products/short-sleeve-t-shirt-1. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://freshxl.com/blogs/news, https://freshxl.com/pages/live, https://freshxl.com/pages/contact, https://freshxl.com/blogs/news/la-games-conference-vip-edition-skybound, https://freshxl.com/blogs/news/ar-house-closing-party-2022 and https://freshxl.com/blogs/news/art-basel have 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 10 pages linked from your homepage and read each the way a search engine does.

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

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

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 testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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.

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

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

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