roarkrevival.ca website review

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

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

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

20 long tasks block the main thread while loading, the longest for 2.7 s. During a long task the page ignores taps.

17 images could be 1.8 MB 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 third-party services load with your homepage (Shopify, Google Tag Manager and corso.com and others), adding 1.9 MB and 1.1 s of main-thread time.

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

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

Shopify costs a phone 339 ms of main-thread work and 1.3 MB 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.

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

About 41 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 50 ms).

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

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

4 KiB could be saved by minifying CSS.

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.

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

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

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

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

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

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

The first text or image appears after 2.6 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 224 ms to 260 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 2.4 s to 2.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 7.3 MB in 437 requests on a phone: images 3.8 MB (65), scripts 1.9 MB (144) and other files 1.0 MB (207). Under 2 MB keeps phones on slow connections fast.

HP-Koa-Pod_2.gif weighs 1.0 MB. On a phone connection a single image that size takes seconds.

1 image (1.0 MB) is 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 (25 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 2.08 g of CO₂e: 250.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Elements must only use permitted ARIA attributes: 9 elements on the page fail this check, rated serious by axe-core.

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

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

Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.

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

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

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

Your title is 69 characters, so Google will cut it off around 60: “Roark Adventure-Ready Men's & Women's Clothing – Tops, Bottoms & Gear”.

There are 3 <h1> headlines (“Roark”, “Adventure is the gift” and “Adventure is the gift”). One clear main headline is easier for people and search engines.

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

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

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

The homepage links to 273 pages on roarkrevival.ca and 14 external pages.

https://roark.com/pages/gift has no meta description, so Google writes the search snippet from whatever text it finds.

https://roark.com/collections/best-sellers, https://roark.com/collections/winter-collection-mens-h226 and https://roark.com/collections/shop-all-mens 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 15 pages linked from your homepage (of 103 found) and read each the way a search engine does.

2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_CONNECTION_CLOSED”.

Large scripts ship without source maps.

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

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