Website review, no card needed

shopfre.com logo

shopfre.com website review

Visit site (opens in a new tab)Reviewed 6 November 202629 issues · 77 checks

This review found 29 issues worth fixing on shopfre.com, 10 of them high impact, across 77 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
1.1 s820 msMay 16Oct 31865 ms
Show as table
DateReal-visitor load time (LCP)
May 16, 2026954 ms
May 23, 2026919 ms
May 30, 2026898 ms
Jun 6, 2026888 ms
Jun 13, 2026896 ms
Jun 20, 2026921 ms
Jun 27, 2026965 ms
Jul 4, 2026948 ms
Jul 11, 2026938 ms
Jul 18, 2026948 ms
Jul 25, 2026946 ms
Aug 1, 2026992 ms
Aug 8, 20261.0 s
Aug 15, 20261.1 s
Aug 22, 20261.1 s
Aug 29, 20261.1 s
Sep 5, 20261.1 s
Sep 12, 20261.0 s
Sep 19, 20261.0 s
Sep 26, 2026986 ms
Oct 3, 2026930 ms
Oct 10, 2026894 ms
Oct 17, 2026873 ms
Oct 24, 2026854 ms
Oct 31, 2026865 ms
Real-visitor tap response (INP)75th percentile, phones
117 ms83 msMay 16Oct 31105 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 202687 ms
May 23, 202688 ms
May 30, 202690 ms
Jun 6, 202691 ms
Jun 13, 202693 ms
Jun 20, 202694 ms
Jun 27, 202695 ms
Jul 4, 202694 ms
Jul 11, 202692 ms
Jul 18, 202693 ms
Jul 25, 202692 ms
Aug 1, 202696 ms
Aug 8, 2026104 ms
Aug 15, 2026105 ms
Aug 22, 2026111 ms
Aug 29, 2026113 ms
Sep 5, 2026112 ms
Sep 12, 2026112 ms
Sep 19, 2026112 ms
Sep 26, 2026112 ms
Oct 3, 2026109 ms
Oct 10, 2026105 ms
Oct 17, 2026104 ms
Oct 24, 2026104 ms
Oct 31, 2026105 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of shopfre.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. shopfre.com at 0.7 s0.7 s
  2. shopfre.com at 1.4 s1.4 s
  3. shopfre.com at 2.0 s2.0 s
  4. shopfre.com at 2.7 s2.7 s
  5. shopfre.com at 3.4 s3.4 s
  6. shopfre.com at 4.1 s4.1 s
  7. shopfre.com at 4.8 s4.8 s
  8. shopfre.com at 5.4 s5.4 s

Speed

9 to fix60
  • Use efficient cache lifetimes

    2.4 s · 661 KiB

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

  • Reduce unused JavaScript

    2.5 s · 450 KiB

    About 450 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.5 s faster on a phone.

  • Improve image delivery

    1.1 s · 315 KiB

    7 images could be 315 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.1 s faster on a phone.

  • Mobile performance score: 60

    60/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (returngo.ai, omnisnippet1.com and Shopify and others), adding 1.5 MB and 603 ms of main-thread time.

  • Render-blocking requests

    550 ms

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

  • Main-thread work: 3.5 s

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

  • 2,240 HTML elements

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

  • Shopify adds 85 ms

    85 ms

    Shopify costs a phone 85 ms of main-thread work and 527 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 on the main thread

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

  • Reduce unused CSS

    160 ms · 30 KiB

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

  • Minify JavaScript

    10 ms · 26 KiB

    26 KiB could be saved by minifying JavaScript.

  • Legacy JavaScript

    10 KiB

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

  • Chained critical requests

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

1 checks passed
  • Server response: 4 ms

    4 ms

    Your server sent the HTML in 4 ms, well inside Google's 600 ms guideline.

Core Web Vitals

6 to fix100
  • Largest Contentful Paint: 16.6 s

    16.6 s

    Your largest element takes 16.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Celestial Define Leggings | Hunter Green”.

  • Time to Interactive: 21.4 s

    21.4 s

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

  • Speed Index: 9.7 s

    9.7 s

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

  • 30 images without width and height

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

  • Total Blocking Time: 264 ms

    264 ms

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

  • First Contentful Paint: 1.9 s

    1.9 s

    The first text or image appears after 1.9 s on a phone. Good is under 1.8 s.

  • Tap response (INP) got 19% slower for real visitors

    +19%

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

  • Largest content (LCP) held steady for real visitors

    -8%

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

7 checks passed
  • Passes Core Web Vitals for real visitors

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

  • Real-user LCP: 1.7 s

    1.7 s

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

  • Real-user INP: 98 ms

    98 ms

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

  • Real-user CLS: 0.04

    0.04

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

  • Real-user FCP: 1.0 s

    1.0 s

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

  • Real-user TTFB: 589 ms

    589 ms

    Real visitors wait 589 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Cumulative Layout Shift: 0.037

    0.037

    The layout barely moves while loading (CLS 0.037, good is under 0.1).

Images and page weight

2 to fix60
  • Page weight: 15.1 MB in 543 requests

    15.1 MB

    Your homepage downloads 15.1 MB in 543 requests on a phone: media 8.9 MB (1), images 3.0 MB (108) and scripts 1.5 MB (165). Under 2 MB keeps phones on slow connections fast.

  • 1 image far larger than shown

    197 KiB

    1 image is downloaded at several times the size a phone draws it, for example Untitled_Design_-_1.png at 8,000 px wide, shown at 240 px. Resized copies would save about 197 KiB.

  • About 4.3 g of CO₂ per visit

    4.28 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

Accessibility

3 to fixGoogle 9495
  • Summary elements must have discernible text (1 element)

    Summary elements must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

  • All page content should be contained by landmarks (2 elements)

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

  • Headings skip levels

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

1 checks passed
  • 48 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 4 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

1 to fixGoogle 9290
  • No H1 headline

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

  • 112 internal links, 2 external

    The homepage links to 112 pages on shopfre.com and 2 external pages.

7 checks passed
  • Meta description: 154 characters

    Your meta description is 154 characters: “Free Ride Equestrian designs athletic apparel for Equestrians. We strive to create products that make riders feel comfo…”.

  • Title: 57 characters

    Your title is a healthy 57 characters: “Free Ride Equestrian™️ - Athletic Apparel for Equestrians”.

  • Canonical URL set

    The canonical URL is https://shopfre.com/.

  • Structured data in place

    Structured data found: Organization and WebSite.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://shopfre.com/sitemap.xml.

AI search readiness

100
4 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (763 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://shopfre.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

2 to fix90
  • 10 pages without a meta description

    https://shopfre.com/pages/about-us, https://shopfre.com/collections/womens-breeches, https://shopfre.com/collections/pro-breeches, https://shopfre.com/collections/riding-leggings-1, https://shopfre.com/collections/winter-breeches and https://shopfre.com/collections/womens-tops and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://shopfre.com/pages/faqs has no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

5 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Titles are unique

    Every page we checked has its own title.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

3 to fixGoogle 9285
  • 8 small tap targets

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

  • 5 JavaScript errors while loading

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

  • 3 distorted images

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix83
  • Thin social proof

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

  • No direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

  • No risk reducer

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

  • About 689 words of copy

    The homepage carries about 689 words of visible text.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Shop Best Sellers” and “START SHOPPING”.

  • 13 calls to action

    The homepage has 13 calls to action, for example “Shop All Women's Breeches”, “Shop All Women's Tops” and “Shop Men's Breeches”.

  • 3 short forms

    3 short forms (2 fields at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Meta Pixel.

Privacy and tracking

1 to fix
  • 6 trackers load before any consent

    6

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Ads 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.

  • 24 cookies set on arrival

    24

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

  • No consent tool detected

    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.

  • 45 other companies contacted

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

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at shopfre.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Apps on your store

Your storefront loads 12 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Returngo Returns Exchanges · Product Reviews Addon · Omnisend · Avada Cookie Bar · Cartbite · stamped.io · cloudfront.net · printful.com · okasconcepts.com · hextom.com · cart-bot.net · vwa.la

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

Stack

E-commerce
Shopify
Hosting
Shopify

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 29 issues on shopfre.com, including 15 speed issues, 1 SEO issue and 2 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25