Website review, no card needed

ericflag.com logo

ericflag.com website review

Visit site (opens in a new tab)Reviewed 6 November 202621 issues · 98 checks

This review found 21 issues worth fixing on ericflag.com, 4 of them high impact, across 98 checks. The most urgent: page weight: 22.6 MB in 49 requests. 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 s922 msMay 16Oct 311.0 s
Show as table
DateReal-visitor load time (LCP)
May 16, 2026975 ms
May 23, 2026968 ms
May 30, 2026972 ms
Jun 6, 2026995 ms
Jun 13, 2026992 ms
Jun 20, 2026990 ms
Jun 27, 2026979 ms
Jul 4, 2026965 ms
Jul 11, 2026974 ms
Jul 18, 2026964 ms
Jul 25, 2026964 ms
Aug 1, 2026956 ms
Aug 8, 2026938 ms
Aug 15, 2026943 ms
Aug 22, 2026956 ms
Aug 29, 2026969 ms
Sep 5, 2026988 ms
Sep 12, 20261.0 s
Sep 19, 20261.0 s
Sep 26, 20261.0 s
Oct 3, 20261.0 s
Oct 10, 20261.0 s
Oct 17, 20261.0 s
Oct 24, 20261.0 s
Oct 31, 20261.0 s
Real-visitor tap response (INP)75th percentile, phones
190 ms148 msMay 16Oct 31184 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026155 ms
May 23, 2026153 ms
May 30, 2026153 ms
Jun 6, 2026155 ms
Jun 13, 2026157 ms
Jun 20, 2026158 ms
Jun 27, 2026159 ms
Jul 4, 2026159 ms
Jul 11, 2026161 ms
Jul 18, 2026161 ms
Jul 25, 2026160 ms
Aug 1, 2026163 ms
Aug 8, 2026162 ms
Aug 15, 2026164 ms
Aug 22, 2026164 ms
Aug 29, 2026162 ms
Sep 5, 2026166 ms
Sep 12, 2026170 ms
Sep 19, 2026173 ms
Sep 26, 2026177 ms
Oct 3, 2026179 ms
Oct 10, 2026180 ms
Oct 17, 2026184 ms
Oct 24, 2026185 ms
Oct 31, 2026184 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 ericflag.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. ericflag.com at 0.4 s0.4 s
  2. ericflag.com at 0.8 s0.8 s
  3. ericflag.com at 1.1 s1.1 s
  4. ericflag.com at 1.5 s1.5 s
  5. ericflag.com at 1.9 s1.9 s
  6. ericflag.com at 2.3 s2.3 s
  7. ericflag.com at 2.6 s2.6 s
  8. ericflag.com at 3.0 s3.0 s

ericflag.com does not allow embedding, so this is Google's rendering of the page.

Speed

1 to fix99
  • Render-blocking requests

    750 ms

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

  • Font display

    100 ms

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

  • Use efficient cache lifetimes

    97 KiB

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

  • Improve image delivery

    85 KiB

    5 images could be 85 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Reduce unused CSS

    23 KiB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Shopify, shop.app and gorgias.chat and others), adding 144 KiB and 0 ms of main-thread time.

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

  • Minify CSS

    4 KiB

    4 KiB could be saved by minifying CSS.

3 checks passed
  • Mobile performance score: 99

    99/100

    Your mobile performance score is 99. That is in Google's “good” band (90 and up).

  • Main-thread work: 0.2 s

    A phone's processor spends 0.2 s on main-thread work while loading, 22 ms of it running JavaScript. That is comfortably low.

  • Server response: 26 ms

    26 ms

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

Core Web Vitals

1 to fix100
  • Tap response (INP) got 20% slower for real visitors

    +20%

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

  • Largest content (LCP) held steady for real visitors

    +4%

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

12 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.0 s

    1.0 s

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

  • Real-user INP: 169 ms

    169 ms

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

  • Real-user CLS: 0.05

    0.05

    For real visitors the layout shifts by 0.05 (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: 719 ms

    719 ms

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

  • Cumulative Layout Shift: 0.056

    0.056

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

  • First Contentful Paint: 1.2 s

    1.2 s

    The first text or image appears after 1.2 s, inside the 1.8 s “good” threshold.

  • Speed Index: 2.2 s

    2.2 s

    Visually, the page fills in at 2.2 s (Speed Index), inside the 3.4 s “good” threshold.

  • Largest Contentful Paint: 1.2 s

    1.2 s

    Your largest element renders in 1.2 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Γ”.

  • Total Blocking Time: 0 ms

    0 ms

    Scripts block the page for only 0 ms while loading. Good is under 200 ms.

  • Time to Interactive: 1.2 s

    1.2 s

    The page is fully interactive after 1.2 s.

Images and page weight

1 to fix70
  • Page weight: 22.6 MB in 49 requests

    22.6 MB

    Your homepage downloads 22.6 MB in 49 requests on a phone: media 21.8 MB (2), images 350 KiB (16) and scripts 288 KiB (25). Under 2 MB keeps phones on slow connections fast.

  • 1 image in older formats

    1 image (104 KiB) 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.

  • About 6.4 g of CO₂ per visit

    6.40 g

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

2 checks passed
  • Images load when needed

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

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

5 to fixGoogle 8893
  • 4 tap targets too small

    4 tap targets are too small or too close together to hit reliably with a finger.

  • 4 images without alt text

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

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    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.

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • 3 links without text

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

1 checks passed
  • 45 automated accessibility rules passed

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

SEO

1 to fixGoogle 9297
  • No social preview image

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

  • 63 internal links, 13 external

    The homepage links to 63 pages on ericflag.com and 13 external pages.

7 checks passed
  • Meta description: 131 characters

    Your meta description is 131 characters: “Boutique d'équipements sportifs spécialisée dans le Street Workout et la Musculation. Découvrez également nos programme…”.

  • One H1 headline

    Your main headline reads: “Eric Flag”.

  • Title: 61 characters

    Your title is a healthy 61 characters: “Eric Flag - Boutique/Programmes Musculation et Street Workout”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: BreadcrumbList, OnlineStore, Organization, WebPage and WebSite.

  • 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://ericflag.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: 6 of 6 facts

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

  • Text is in the HTML

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

  • llms.txt published

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

Other pages

3 to fix83
  • 2 linked pages hidden from search

    /products/gilet-leste-30kg and /pages/sales are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 2 pages without a meta description

    /products/gilet-leste-30kg and /pages/sales have no meta description, so Google writes the search snippet from whatever text it finds.

  • 4 pages without an H1

    /collections/equipements, /collections/packs, /pages/guide-achat and /pages/sales have 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 29 found) and read each the way a search engine does.

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

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9687
  • 12 small tap targets

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

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Security and trust

100
  • Short HSTS lifetime

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

  • 2 links through redirect chains

    2 links go through two or more redirects, for example https://ericflag.com/account.

  • No Referrer-Policy

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

  • No Permissions-Policy

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

  • Deprecated X-XSS-Protection

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

  • No security.txt

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

7 checks passed
  • Served over HTTPS

    The homepage is served over HTTPS (ericflag.com).

  • Valid certificate (87 days left)

    The certificate from Let's Encrypt · YE2 verifies for ericflag.com and is valid for another 87 days.

  • Protected from clickjacking

    X-Frame-Options or a frame-ancestors policy stops other sites framing yours.

  • Content-Security-Policy set

    A Content-Security-Policy is set, the main browser-side defence against injected scripts.

  • http:// redirects to https

    http://ericflag.com redirects to the secure version.

  • HTTP/2

    The server speaks HTTP/2, so browsers load many files over one connection.

  • All 36 links work

    All 36 links checked from your homepage (32 internal, 4 external) answered without errors.

Domain and trust

  • No CAA record

    ericflag.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

  • DNSSEC is off

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

2 checks passed
  • Domain is 9 years old

    9 years

    ericflag.com was registered in Jun 2017 through Infomaniak Network SA. An established domain carries more trust with email providers and search engines.

  • Registered until Jun 2027

    ericflag.com is registered until Jun 2027.

Content and conversion

4 to fix75
  • Local business without LocalBusiness data

    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.

  • No phone number on the homepage

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

  • Thin social proof

    Social proof on the homepage: 6 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 opening hours

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

  • No map or directions link

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

  • 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 549 words of copy

    The homepage carries about 549 words of visible text.

  • Urgency cues

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

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “BUY THE DOOR BAR”.

  • 1 call to action

    The homepage has 1 call to action, for example “Aide & Contact”.

  • 1 short form

    A short form (0 fields at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager, Microsoft Clarity and Hotjar.

Email authentication

2 to fix35
  • No SPF record

    ericflag.com has no SPF record, so mail servers can't tell which servers may send email as you. Your mail lands in spam more often, and anyone can send mail pretending to be you.

  • DMARC is monitor-only (p=none)

    DMARC is set to p=none, so mail pretending to be ericflag.com is still delivered. Reports are on, so moving to quarantine is the next step.

  • Email authentication score: 35/100

    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.

1 checks passed
  • DKIM signing found

    A DKIM key is published (selector “mail”), so receivers can verify mail really came from you.

Privacy and tracking

1 to fix
  • 1 tracker load before any consent

    1

    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.

  • 6 cookies set on arrival

    6

    Opening the homepage sets 6 cookies (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.

  • 9 other companies contacted

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

Apps on your store

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

None of the apps your storefront loads is on the list of apps with a known security problem.

Apps your storefront loads

Pandectes Gdpr · Judge Me Reviews · Smart Seo · Instaindex · Weglot Translate Your Store · Blocky Fraud Blocker · Klaviyo Email Marketing Sms · Gorgias Live Chat Helpdesk · Gdpr Cookie Consent · Countdown Timer · trustpilot.com · amazonaws.com · web.app · goaffpro.com

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

No signs of neglect in what was checked: the copyright year, CMS and plugin versions, and jQuery.

Stack

Framework
Bootstrap
E-commerce
Shopify
Analytics
Google Tag Manager | Hotjar
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 21 issues on ericflag.com, including 2 speed issues, 1 SEO issue and 4 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