agongym.com website review

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

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

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

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

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

Shopify costs a phone 91 ms of main-thread work and 380 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.

8 third-party services load with your homepage (Klarna, Klaviyo and Shopify and others), adding 865 KiB and 352 ms of main-thread time.

6 images could be 97 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.

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

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

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

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

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

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

The page becomes fully interactive after 10.5 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.

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

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

Your homepage downloads 2.3 MB in 215 requests on a phone: scripts 996 KiB (69), other files 804 KiB (113) and images 442 KiB (20). Under 2 MB keeps phones on slow connections fast.

1 image further down the page (103 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.66 g of CO₂e: 79.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

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.

Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.

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

Your title is only 20 characters: “AGONGYM : Sportswear”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

The homepage links to 199 pages on agongym.com and 6 external pages.

/en/products/hoodie-limitless-black-white, /en/products/hoodie-limitless-black-mustard, /en/products/hoodie-limitless-camel-dark-brown and /en/products/pullover-limitless-camel-dark-brown all use the title “BB TEAM HOODIE - BLACK”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

/en/collections/black-month, /en/collections/lifting-culture, /en/collections/training-club-1 and /en/collections/liquidacion have no meta description, so Google writes the search snippet from whatever text it finds.

/en/products/hoodie-limitless-black-white, /en/products/hoodie-limitless-black-mustard, /en/products/hoodie-limitless-camel-dark-brown and /en/products/pullover-limitless-camel-dark-brown use the same meta description. A description written for each page earns more clicks.

/en/collections/black-month, /en/collections/lifting-culture, /en/collections/training-club-1 and /en/collections/liquidacion have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

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.

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

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