foreignrider.com website review

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

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

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

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

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

8 third-party services load with your homepage (Shopify, Klaviyo and LoyaltyLion and others), adding 1.4 MB and 576 ms of main-thread time.

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

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

Klaviyo costs a phone 139 ms of main-thread work and 327 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.

LoyaltyLion costs a phone 124 ms of main-thread work and 357 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.

About 221 KiB of JavaScript is downloaded but never used on this page.

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

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

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

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

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.

2 KiB could be saved by minifying CSS.

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

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

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

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

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

Your homepage downloads 3.7 MB in 344 requests on a phone: images 1.7 MB (98), scripts 913 KiB (105) and other files 791 KiB (108). Under 2 MB keeps phones on slow connections fast.

2 images are downloaded at several times the size a phone draws them, for example 3971874007816435115.jpg at 1,080 px wide, shown at 170 px. Resized copies would save about 254 KiB.

2 images (375 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.

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

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

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

Your title is only 17 characters: “Foreign Rider Co.”. Between 30 and 65 characters leaves room to say what you do and for whom.

Your meta description is only 17 characters: “Foreign Rider Co.”. 70 to 160 characters is enough to sell the click.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

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

The homepage links to 67 pages on foreignrider.com and 4 external pages.

/policies/shipping-policy, /collections/denim, /collections/all, /collections/new-releases, /collections/t-shirts and /collections/long-sleeve-t-shirts and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.

/collections/all, /collections/t-shirts, /collections/long-sleeve-t-shirts, /collections/sweatshirts, /collections/analog-series and /pages/about have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

HSTS is set, but max-age is 91 days; one year is the recommended minimum.

1 link go through two or more redirects, for example http://instagram.com/foreignriderco.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

foreignrider.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

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

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

DMARC is set to p=none, so mail pretending to be foreignrider.com is still delivered. Add a report address, check the reports, then move to quarantine.

We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

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 15 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 34 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.