Website review, no card needed

fknrich.com logo

fknrich.com website review

Visit site (opens in a new tab)Reviewed 6 November 202626 issues · 82 checks

This review found 26 issues worth fixing on fknrich.com, 8 of them high impact, across 82 checks. The most urgent: main-thread work: 5.4 s. 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 s798 msMay 16Oct 31887 ms
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.0 s
May 23, 20261.0 s
May 30, 2026928 ms
Jun 6, 2026875 ms
Jun 13, 2026919 ms
Jun 20, 2026883 ms
Jun 27, 2026982 ms
Jul 4, 2026996 ms
Jul 11, 20261.0 s
Jul 18, 20261.0 s
Jul 25, 2026903 ms
Aug 1, 2026911 ms
Aug 8, 2026915 ms
Aug 15, 2026915 ms
Aug 22, 2026968 ms
Aug 29, 2026969 ms
Sep 5, 2026912 ms
Sep 12, 2026891 ms
Sep 19, 2026878 ms
Sep 26, 2026830 ms
Oct 3, 2026844 ms
Oct 10, 2026857 ms
Oct 17, 2026840 ms
Oct 24, 2026887 ms
Oct 31, 2026887 ms
Real-visitor tap response (INP)75th percentile, phones
116 ms74 msMay 16Oct 31110 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 202688 ms
May 23, 202689 ms
May 30, 202691 ms
Jun 6, 202695 ms
Jun 13, 202695 ms
Jun 20, 202695 ms
Jun 27, 202696 ms
Jul 4, 202695 ms
Jul 11, 202689 ms
Jul 18, 202682 ms
Jul 25, 202679 ms
Aug 1, 202681 ms
Aug 8, 202683 ms
Aug 15, 202687 ms
Aug 22, 202691 ms
Aug 29, 202695 ms
Sep 5, 2026103 ms
Sep 12, 2026104 ms
Sep 19, 2026104 ms
Sep 26, 2026103 ms
Oct 3, 2026103 ms
Oct 10, 2026102 ms
Oct 17, 202699 ms
Oct 24, 2026111 ms
Oct 31, 2026110 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 fknrich.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. fknrich.com at 0.8 s0.8 s
  2. fknrich.com at 1.6 s1.6 s
  3. fknrich.com at 2.4 s2.4 s
  4. fknrich.com at 3.2 s3.2 s
  5. fknrich.com at 4.0 s4.0 s
  6. fknrich.com at 4.8 s4.8 s
  7. fknrich.com at 5.6 s5.6 s
  8. fknrich.com at 6.4 s6.4 s

Speed

7 to fix93
  • Main-thread work: 5.4 s

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

  • 5,099 HTML elements

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

  • Improve image delivery

    963 KiB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (appstle.com, Yotpo and Shopify and others), adding 1.6 MB and 447 ms of main-thread time.

  • Reduce unused JavaScript

    523 KiB

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

  • Render-blocking requests

    450 ms

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

  • Shopify adds 104 ms

    104 ms

    Shopify costs a phone 104 ms of main-thread work and 1.1 MB 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.

  • Use efficient cache lifetimes

    242 KiB

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

  • 9 long tasks on the main thread

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

  • Font display

    50 ms

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

  • Reduce unused CSS

    47 KiB

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

  • Minify JavaScript

    8 KiB

    8 KiB could be saved by minifying JavaScript.

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

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

2 checks passed
  • Mobile performance score: 93

    93/100

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

  • Server response: 11 ms

    11 ms

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

Core Web Vitals

3 to fix100
  • Time to Interactive: 17.8 s

    17.8 s

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

  • Speed Index: 6.1 s

    6.1 s

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

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

    +25%

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

11 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: 0.9 s

    0.9 s

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

  • Real-user INP: 107 ms

    107 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 0.8 s

    0.8 s

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

  • Real-user TTFB: 545 ms

    545 ms

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

  • Largest content (LCP) got 15% faster for real visitors

    -15%

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

  • Total Blocking Time: 113 ms

    113 ms

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

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

  • Cumulative Layout Shift: 0.031

    0.031

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

  • 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 element shown below.

Images and page weight

1 to fix70
  • Page weight: 4.4 MB in 290 requests

    4.4 MB

    Your homepage downloads 4.4 MB in 290 requests on a phone: images 2.1 MB (45), scripts 1.2 MB (118) and other files 784 KiB (107). Under 2 MB keeps phones on slow connections fast.

  • About 1.3 g of CO₂ per visit

    1.26 g

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

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

  • Images are sized for phones

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

Accessibility

7 to fixGoogle 8892
  • Invalid ARIA attributes

    11 elements use ARIA attributes their role does not allow, which confuses screen readers.

  • 17 tap targets too small

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

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

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

  • Alternative text of images should not be repeated as text (2 elements)

    Alternative text of images should not be repeated as text: 2 elements on the page fail this check, rated minor by axe-core.

  • ARIA role should be appropriate for the element (1 element)

    ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.

  • Headings should not be empty (1 element)

    Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (2 elements).

2 checks passed
  • Every image has alt text

    All 801 images in the HTML carry an alt attribute.

  • 50 automated accessibility rules passed

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

SEO

1 to fixGoogle 10095
  • Meta description is long (255 characters)

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

  • 145 internal links, 22 external

    The homepage links to 145 pages on fknrich.com and 22 external pages.

7 checks passed
  • One H1 headline

    Your main headline reads: “FKN Rich”.

  • Title: 52 characters

    Your title is a healthy 52 characters: “FKN Rich Clothing - 2026 Sitewide Sale (ENDING SOON)”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: BreadcrumbList, 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://fknrich.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: 5 of 6 facts

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

  • Text is in the HTML

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

  • llms.txt published

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

Other pages

1 to fix95
  • 15 links to non-canonical URLs

    Your homepage links to 15 pages by a URL that isn't their canonical one, for example https://fknrich.com/collections/tee-collection/tees, whose canonical is https://fknrich.com/a/shop/collections/tee-collection. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 15 internal pages checked

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

6 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • 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

2 to fixGoogle 7791
  • 15 small tap targets

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

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix71
  • No call to action on the first screen

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

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

  • About 698 words of copy

    The homepage carries about 698 words of visible text.

4 checks passed
  • 16 calls to action

    The homepage has 16 calls to action, for example “Contact”, “Track My Order” and “Shop Now”.

  • 23 short forms

    23 short forms (1 field at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 1 trust badge and “LOVED BY 100,000+ CUSTOMERS”.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

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

  • 15 cookies set on arrival

    15

    Opening the homepage sets 15 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.

  • 23 other companies contacted

    Loading the homepage contacts 23 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 fknrich.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 7 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Inbox · Yotpo Subscriptions · Yotpo Loyalty Rewards · Judge Me Reviews · Page Speed Optimizer · Forms · Essential Cart Drawer

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 Hosted

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 26 issues on fknrich.com, including 10 speed issues, 1 SEO issue and 3 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