retro-rifle.com website review

37 images could be 2.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.9 s faster on a phone.

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

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

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

About 79 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.

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

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

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

16 KiB could be saved by minifying CSS.

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

7 third-party services load with your homepage (JSDelivr CDN, Shopify and Google Fonts and others), adding 720 KiB and 1 ms of main-thread time.

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

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.

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.

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

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

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

Real visitors wait 271 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 122 ms to 189 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Real visitors see the first content after 2.2 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.

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

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

Your homepage downloads 36.2 MB in 251 requests on a phone: images 35.0 MB (200), fonts 431 KiB (11) and scripts 391 KiB (27). Under 2 MB keeps phones on slow connections fast.

Memory-Flannel-Product-GIF.gif weighs 2.2 MB. On a phone connection a single image that size takes seconds.

2 images are downloaded at several times the size a phone draws them, for example Graffiti.png at 1,200 px wide, shown at 212 px. Resized copies would save about 511 KiB.

1 image (2.2 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.

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

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

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

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

Contentinfo landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

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

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.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

There is no <h1>, so neither visitors nor Google get a clear main headline.

Structured data found ((untyped), BreadcrumbList, Organization and WebSite) but with 8 problems, for example “untyped block: missing @context (expected "https://schema.org")”.

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

The homepage links to 262 pages on retro-rifle.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://retro-rifle.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

https://retro-rifle.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://retro-rifle.com/customer_authentication/redirect and https://retro-rifle.com/pages/rewards have no meta description, so Google writes the search snippet from whatever text it finds.

https://retro-rifle.com/collections/hybrid-shorts and https://retro-rifle.com/collections/bold-mens-apparel 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://retro-rifle.com/pages/sizing-1, whose canonical is https://retro-rifle.com/pages/sizing. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://retro-rifle.com/customer_authentication/redirect, https://retro-rifle.com/pages/rewards and https://retro-rifle.com/pages/sizing-1 have no <h1> headline, so visitors and search engines get no clear main topic.

https://retro-rifle.com/pages/sizing-1 and https://retro-rifle.com/products/22-retro-street-polo took over 3 s to send their HTML from our server.

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

2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://cdn.xotiny.com/assets/shop/the-can-co/gallery/main.min.css?v=1790799510994' from o…”.

6 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

Social proof on the homepage: 4 trust badges. 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 phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage shows no opening hours. If customers visit or call, show when.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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 1,083 words of visible text.

The page uses urgency cues (a countdown or limited-time wording).

Before a visitor clicks anything, the page loads Klaviyo (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 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 9 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.