maap.cc website review

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

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

Your mobile performance score is 28. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

56 images could be 5.8 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

8 third-party services load with your homepage (Google Tag Manager, ContentSquare and Facebook and others), adding 2.2 MB and 1.5 s of main-thread time.

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

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

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

ZenDesk costs a phone 133 ms of main-thread work and 431 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.

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

7 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 150 ms faster on a phone.

About 24 KiB of CSS is downloaded but never applied on this page.

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

2 KiB could be saved by minifying JavaScript.

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

For real visitors the layout shifts by 0.41 (75th percentile). Good is under 0.1.

Your largest element takes 11.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Seen at Speed.”.

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

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

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

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

Real visitors wait 2.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.

Real visitors wait 296 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

Real visitors see the first content after 2.4 s (75th percentile). Good is under 1.8 s.

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

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

Your homepage downloads 10.8 MB in 295 requests on a phone: images 7.2 MB (83), scripts 3.1 MB (94) and fonts 203 KiB (3). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example knwMpNuIowoCAEAC_ROAD_CLP_SH_HEADER_MOBILE_GAMMA.png at 1,280 px wide, shown at 390 px. Resized copies would save about 14 KiB.

By the Sustainable Web Design model, a visit to your homepage emits about 3.05 g of CO₂e: 366.4 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”.

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

1 tap target is too small or too close together to hit reliably with a finger.

All page content should be contained by landmarks: 84 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.

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

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

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

There are 2 <h1> headlines (“Seen at Speed.” and “Cycling Clothing”). One clear main headline is easier for people and search engines.

No Open Graph image (also missing: og:title, og:description), 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.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 66 pages on maap.cc and 14 external pages.

There is no https://maap.cc/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://maap.cc/pages/careers has no <title>, so Google invents the link text in results.

https://maap.cc/products/training-jersey-2-0-blue-ink and https://maap.cc/products/training-jersey-2-0-ash-pink all use the title “Training Jersey 2.0 - MAAP Cycling Apparel”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

https://maap.cc/pages/careers has no meta description, so Google writes the search snippet from whatever text it finds.

https://maap.cc/bundles, https://maap.cc/about-us, https://maap.cc/pages/stockist and https://maap.cc/labs use the same meta description. A description written for each page earns more clicks.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://maap.cc/pages/stockist, whose canonical is https://maap.cc/pages/undefined. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://maap.cc/collections/gamma, https://maap.cc/collections/alt-road, https://maap.cc/collections/aeon, https://maap.cc/collections/training, https://maap.cc/bundles and https://maap.cc/collections/core-icon and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://maap.cc/bundles, https://maap.cc/pages/stockist and https://maap.cc/labs 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.

https://maap.cc/products/training-thermal-ls-jersey-2-0-pomegranate took over 3 s to send its HTML from our server.

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

2 images failed to load on a phone, for example https://d.adroll.com/uev/U3NP3TIEYFDLJNMXNDFNU5/YOTRPVE4H5FZ3MXNPL4AQU/?adroll_tpc=lx3%3Dlex-875dcf7e-8824-4efd-8dd5-36b3b8e5e127&af0=0fe6f973&adroll_fpc=54701731541b929209f7ee0339e59f9d-1794022704009.

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

Chrome logged issues while loading the page (“Content security policy”).

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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 237 words of visible text; thin pages give Google and first-time buyers little to go on.

There is no form on the homepage, so every lead has to click through to another page first.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and LinkedIn Insight and 5 mores (measured from a US location before any click). A consent tool (Osano) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 29 cookies, 3 of them by other companies (measured from a US location before any click).

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