Website review, no card needed

saintbasics.com logo

saintbasics.com website review

Visit site (opens in a new tab)Reviewed 6 November 202634 issues · 83 checks

This review found 34 issues worth fixing on saintbasics.com, 9 of them high impact, across 83 checks. The most urgent: reduce unused JavaScript. 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.7 s1.3 sMay 16Oct 311.4 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.7 s
May 23, 20261.6 s
May 30, 20261.5 s
Jun 6, 20261.4 s
Jun 13, 20261.4 s
Jun 20, 20261.4 s
Jun 27, 20261.4 s
Jul 4, 20261.4 s
Jul 11, 20261.4 s
Jul 18, 20261.4 s
Jul 25, 20261.4 s
Aug 1, 20261.5 s
Aug 8, 20261.5 s
Aug 15, 20261.5 s
Aug 22, 20261.5 s
Aug 29, 20261.4 s
Sep 5, 20261.4 s
Sep 12, 20261.4 s
Sep 19, 20261.4 s
Sep 26, 20261.4 s
Oct 3, 20261.4 s
Oct 10, 20261.4 s
Oct 17, 20261.4 s
Oct 24, 20261.4 s
Oct 31, 20261.4 s
Real-visitor tap response (INP)75th percentile, phones
170 ms121 msMay 16Oct 31164 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026144 ms
May 23, 2026137 ms
May 30, 2026131 ms
Jun 6, 2026128 ms
Jun 13, 2026127 ms
Jun 20, 2026130 ms
Jun 27, 2026137 ms
Jul 4, 2026139 ms
Jul 11, 2026141 ms
Jul 18, 2026145 ms
Jul 25, 2026145 ms
Aug 1, 2026145 ms
Aug 8, 2026145 ms
Aug 15, 2026146 ms
Aug 22, 2026147 ms
Aug 29, 2026154 ms
Sep 5, 2026160 ms
Sep 12, 2026159 ms
Sep 19, 2026162 ms
Sep 26, 2026162 ms
Oct 3, 2026158 ms
Oct 10, 2026158 ms
Oct 17, 2026157 ms
Oct 24, 2026160 ms
Oct 31, 2026164 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 saintbasics.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. saintbasics.com at 0.6 s0.6 s
  2. saintbasics.com at 1.2 s1.2 s
  3. saintbasics.com at 1.8 s1.8 s
  4. saintbasics.com at 2.4 s2.4 s
  5. saintbasics.com at 3.0 s3.0 s
  6. saintbasics.com at 3.6 s3.6 s
  7. saintbasics.com at 4.2 s4.2 s
  8. saintbasics.com at 4.8 s4.8 s

Speed

10 to fix65
  • Reduce unused JavaScript

    2.2 s · 606 KiB

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

  • Render-blocking requests

    2.5 s

    33 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.5 s.

  • Improve image delivery

    750 ms · 801 KiB

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

  • Use efficient cache lifetimes

    500 ms · 543 KiB

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

  • Mobile performance score: 65

    65/100

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

  • 6 third-party services on the page

    6 third-party services load with your homepage (Google Tag Manager, Bing Ads and ahrefs.com and others), adding 4.6 MB and 364 ms of main-thread time.

  • Key CDN adds 0 ms

    0 ms

    Key CDN costs a phone 0 ms of main-thread work and 4.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.

  • Google Tag Manager adds 350 ms

    350 ms

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

  • Reduce unused CSS

    300 ms · 33 KiB

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

  • 2,087 HTML elements

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

  • 7 long tasks on the main thread

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

  • 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
  • Main-thread work: 1.6 s

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

  • Server response: 311 ms

    311 ms

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

Core Web Vitals

4 to fix100
  • Largest Contentful Paint: 12.1 s

    12.1 s

    Your largest element takes 12.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Women Explore”.

  • Time to Interactive: 14.6 s

    14.6 s

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

  • Speed Index: 8.7 s

    8.7 s

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

  • 54 images without width and height

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

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

    +15%

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

10 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: 2.0 s

    2.0 s

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

  • Real-user INP: 195 ms

    195 ms

    Real visitors wait 195 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: 1.4 s

    1.4 s

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

  • Real-user TTFB: 591 ms

    591 ms

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

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

    -13%

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

  • First Contentful Paint: 1.7 s

    1.7 s

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

  • Total Blocking Time: 116 ms

    116 ms

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

4 to fix43
  • Page weight: 6.5 MB in 350 requests

    6.5 MB

    Your homepage downloads 6.5 MB in 350 requests on a phone: images 5.0 MB (260), scripts 1.2 MB (43) and HTML 130 KiB (1). Under 2 MB keeps phones on slow connections fast.

  • 25 images in older formats

    25 images (1.6 MB) 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.

  • 24 images below the first screen load straight away

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

  • 1 image far larger than shown

    148 KiB

    1 image is downloaded at several times the size a phone draws it, for example Men's Boots.png at 500 px wide, shown at 35 px. Resized copies would save about 148 KiB.

  • About 1.8 g of CO₂ per visit

    1.83 g

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

Accessibility

4 to fixGoogle 9391
  • 8 images without alt text

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

  • Zoom is disabled

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

  • 30 links without text

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

  • 3 form fields without a label

    3 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • Headings skip levels

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

1 checks passed
  • 25 automated accessibility rules passed

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

SEO

1 to fixGoogle 9298
  • 30 links crawlers can't follow

    30 links have no real href, so search engines can't follow them.

  • 317 internal links, 10 external

    The homepage links to 317 pages on saintbasics.com and 10 external pages.

8 checks passed
  • Meta description: 156 characters

    Your meta description is 156 characters: “The world's largest 100% vegan fashion shop: 25,000+ items, 230 brands. No, we call none of it 'sustainable'. Yes, all …”.

  • One H1 headline

    Your main headline reads: “Vegan Fashion & Shoes, Vetted on Worker Pay and Materials”.

  • Title: 57 characters

    Your title is a healthy 57 characters: “Vegan Fashion & Shoes, Vetted on Worker Pay and Materials”.

  • Canonical URL set

    The canonical URL is https://www.shoplikeyougiveadamn.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://www.shoplikeyougiveadamn.nl/sitemap.xml.

AI search readiness

1 to fix88
  • Organization data is thin (2 of 6 facts)

    Your Organization JSON-LD is missing logo, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

  • Opted out of AI training for 5 crawlers

    robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.

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

  • Text is in the HTML

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

  • llms.txt published

    The site publishes https://www.shoplikeyougiveadamn.com/llms.txt (4 KiB, 25 links), a plain-text guide to the site for AI tools.

Other pages

3 to fix75
  • 1 page without a title

    https://www.shoplikeyougiveadamn.com/mijnaccount/favorites has no <title>, so Google invents the link text in results.

  • 1 page without a meta description

    https://www.shoplikeyougiveadamn.com/mijnaccount/favorites has no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

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

  • 3 pages slow to respond

    https://www.shoplikeyougiveadamn.com/women/clothing/hoodies-sweatshirts/c-100, https://www.shoplikeyougiveadamn.com/women/clothing/coats-jackets/c-103 and https://www.shoplikeyougiveadamn.com/women/clothing/jeans/c-108 took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 197 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.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

Best practices

Google 100100
  • Missing source maps

    Large scripts ship without source maps.

3 checks passed
  • No console errors

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

  • Tap targets are thumb-sized

    58 of 60 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • Local business without LocalBusiness data

    Your homepage shows a map 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: 2 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No analytics detected

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

  • A 8-field form

    Your longest form asks for 8 fields (1 required). Every extra field lowers completion.

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

    The homepage carries about 914 words of visible text.

1 checks passed
  • 4 calls to action

    The homepage has 4 calls to action, for example “Shop all brands”, “Shop all brands →” and “Shop By”.

Privacy and tracking

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

  • 1 other company contacted

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

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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 saintbasics.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
SvelteKit
Hosting
Leaseweb

Company

Headquarters
The Hague

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 34 issues on saintbasics.com, including 14 speed issues, 1 SEO issue and 7 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