r1concepts.com website review

29 files are served with short cache lifetimes, so returning visitors download them again (1.0 MB).

Your mobile performance score is 57 (desktop: 83). Pages that score under 90 lose visitors before the first paint.

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

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

15 images could be 508 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 200 ms faster on a phone.

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

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

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

Attentive costs a phone 49 ms of main-thread work and 359 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.

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

58 KiB could be saved by minifying JavaScript.

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

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

Desktop scores 83 but mobile only 57. A gap that wide usually means heavy scripts and images that hit phones hardest.

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 20.7 s. Good is under 3.8 s.

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

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

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

27 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-17, real Chrome visitors' tap response (inp) went from 148 ms to 162 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 3.4 MB in 148 requests on a phone: scripts 1.7 MB (46), images 1.2 MB (46) and fonts 207 KiB (7). Under 2 MB keeps phones on slow connections fast.

5 images are downloaded at several times the size a phone draws them, for example hq720.webp at 1,280 px wide, shown at 184 px. Resized copies would save about 341 KiB.

9 images further down the page (554 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

5 images (226 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.

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

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

Your title is only 23 characters: “Home Page | R1 Concepts”. Between 30 and 65 characters leaves room to say what you do and for whom.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

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

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 53 pages on r1concepts.com and 16 external pages.

There is no https://www.r1concepts.com/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://www.r1concepts.com/category/brake-drums-and-shoes, https://www.r1concepts.com/category/brake-hardware-adjusters, https://www.r1concepts.com/category/brake-hydraulics, https://www.r1concepts.com/category/brake-sensors, https://www.r1concepts.com/category/brake-stainless-steel-lines and https://www.r1concepts.com/category/brake-calipers all use the title “R1 Concepts - Recaptcha Validate”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.r1concepts.com/category/brake-kits, https://www.r1concepts.com/category/brake-rotors and https://www.r1concepts.com/category/brake-pads have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.r1concepts.com/category/brake-drums-and-shoes, https://www.r1concepts.com/category/brake-hardware-adjusters, https://www.r1concepts.com/category/brake-hydraulics, https://www.r1concepts.com/category/brake-sensors, https://www.r1concepts.com/category/brake-stainless-steel-lines and https://www.r1concepts.com/category/brake-calipers 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://www.r1concepts.com/cms/about-us, whose canonical is https://www.r1concepts.com/about-us. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.r1concepts.com/blog has no <h1> headline, so visitors and search engines get no clear main topic.

https://www.r1concepts.com/category/brake-drums-and-shoes, https://www.r1concepts.com/category/brake-hardware-adjusters, https://www.r1concepts.com/category/brake-hydraulics, https://www.r1concepts.com/category/brake-sensors, https://www.r1concepts.com/category/brake-stainless-steel-lines and https://www.r1concepts.com/category/brake-calipers 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 25 found) and read each the way a search engine does.

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

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 403 ()”.

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

1 image is served at too low a resolution for sharp phone screens.

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

Large scripts ship without source maps.

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

Social proof on the homepage: 6 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and Meta Pixel and 1 more (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 25 cookies (measured from a US location before any click).

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