Website review, no card needed
shirtstore.eu website review
Visit site (opens in a new tab)Reviewed 9 November 202632 issues · 84 checks
This review found 32 issues worth fixing on shirtstore.eu, 7 of them high impact, across 84 checks. The most urgent: 3,874 HTML elements. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
90A- #2,491 of 124,235 reviewed websitesbeats 97%
- #1,187 of 69,818 online storesbeats 97%
- #1,149 of 63,496 Shopify storesbeats 97%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 1.7 s |
| May 30, 2026 | 1.7 s |
| Jun 6, 2026 | 1.6 s |
| Jun 13, 2026 | 1.6 s |
| Jun 20, 2026 | 1.7 s |
| Jun 27, 2026 | 1.6 s |
| Jul 4, 2026 | 1.6 s |
| Jul 11, 2026 | 1.6 s |
| Jul 18, 2026 | 1.5 s |
| Jul 25, 2026 | 1.5 s |
| Aug 1, 2026 | 1.5 s |
| Aug 8, 2026 | 1.5 s |
| Aug 15, 2026 | 1.5 s |
| Aug 22, 2026 | 1.5 s |
| Aug 29, 2026 | 1.6 s |
| Sep 5, 2026 | 1.5 s |
| Sep 12, 2026 | 1.5 s |
| Sep 19, 2026 | 1.5 s |
| Sep 26, 2026 | 1.5 s |
| Oct 3, 2026 | 1.5 s |
| Oct 10, 2026 | 1.5 s |
| Oct 17, 2026 | 1.5 s |
| Oct 24, 2026 | 1.5 s |
| Oct 31, 2026 | 1.5 s |
| Nov 7, 2026 | 1.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 154 ms |
| May 30, 2026 | 165 ms |
| Jun 6, 2026 | 165 ms |
| Jun 13, 2026 | 154 ms |
| Jun 20, 2026 | 147 ms |
| Jun 27, 2026 | 143 ms |
| Jul 4, 2026 | 135 ms |
| Jul 11, 2026 | 143 ms |
| Jul 18, 2026 | 144 ms |
| Jul 25, 2026 | 140 ms |
| Aug 1, 2026 | 141 ms |
| Aug 8, 2026 | 138 ms |
| Aug 15, 2026 | 145 ms |
| Aug 22, 2026 | 146 ms |
| Aug 29, 2026 | 152 ms |
| Sep 5, 2026 | 146 ms |
| Sep 12, 2026 | 144 ms |
| Sep 19, 2026 | 143 ms |
| Sep 26, 2026 | 137 ms |
| Oct 3, 2026 | 137 ms |
| Oct 10, 2026 | 137 ms |
| Oct 17, 2026 | 134 ms |
| Oct 24, 2026 | 136 ms |
| Oct 31, 2026 | 133 ms |
| Nov 7, 2026 | 133 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
Speed
3,874 HTML elements
The page has 3,874 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Mobile performance score: 86
86/100Your mobile performance score is 86. 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 (elfsight.com, spoks.com and Shopify and others), adding 1.0 MB and 479 ms of main-thread time.
Render-blocking requests
500 ms3 files block the first paint until they finish downloading. Deferring or inlining them could save about 500 ms.
Improve image delivery
431 KiB27 images could be 431 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
elfsight.com adds 341 ms
341 mselfsight.com costs a phone 341 ms of main-thread work and 400 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.
Use efficient cache lifetimes
331 KiB15 files are served with short cache lifetimes, so returning visitors download them again (331 KiB).
Main-thread work: 2.8 s
A phone's processor spends 2.8 s on main-thread work while loading, 843 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Shopify adds 58 ms
58 msShopify costs a phone 58 ms of main-thread work and 427 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 JavaScript
245 KiBAbout 245 KiB of JavaScript is downloaded but never used on this page.
4 long tasks on the main thread
4 long tasks block the main thread while loading, the longest for 125 ms. During a long task the page ignores taps.
Legacy JavaScript
17 KiBPolyfills for old browsers add 17 KiB JavaScript that modern phones do not need.
Minify JavaScript
15 KiB15 KiB could be saved by minifying JavaScript.
Reduce unused CSS
13 KiBAbout 13 KiB of CSS is downloaded but never applied on this page.
Duplicated JavaScript
8 KiB8 KiB JavaScript is shipped twice across bundles.
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.
1 checks passed
Server response: 16 ms
16 msYour server sent the HTML in 16 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 10.8 s
10.8 sThe page becomes fully interactive after 10.8 s. Good is under 3.8 s.
Speed Index: 5.2 s
5.2 sVisually, the page fills in at 5.2 s (Speed Index). Good is under 3.4 s.
Largest Contentful Paint: 3.5 s
3.5 sYour largest element takes 3.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Largest content (LCP) held steady for real visitors
-8%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.7 s to 1.5 s 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: 1.2 s
1.2 sReal visitors wait 1.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 126 ms
126 msReal visitors wait 126 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.1 s
1.1 sReal visitors see the first content after 1.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 570 ms
570 msReal visitors wait 570 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 17% faster for real visitors
-17%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 154 ms to 133 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 1.4 s
1.4 sThe first text or image appears after 1.4 s, inside the 1.8 s “good” threshold.
Total Blocking Time: 117 ms
117 msScripts block the page for only 117 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 3.4 MB in 214 requests
3.4 MBYour homepage downloads 3.4 MB in 214 requests on a phone: images 1.4 MB (54), other files 960 KiB (82) and scripts 857 KiB (52). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
MTV_SQUARE.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).
About 1.0 g of CO₂ per visit
0.97 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.97 g of CO₂e: 116.7 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 are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
2 text elements with low contrast
2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Scrollable region must have keyboard access (2 elements)
Scrollable region must have keyboard access: 2 elements on the page fail this check, rated serious by axe-core.
2 images without alt text
2 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (9 elements)
All page content should be contained by landmarks: 9 elements on the page fail this check, rated moderate by axe-core.
34 links without text
34 visible links have no text or label, so screen readers cannot say where they go.
Elements use prohibited ARIA attributes
Elements use prohibited ARIA attributes (2 elements).
1 checks passed
51 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 55 WCAG 2.2 A/AA and best-practice rules on the phone render: 51 passed and 4 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
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.
Structured data has 1 problem
Structured data found (Organization and WebSite) but with 1 problem, for example “Organization: url points at a different host (https://shirtstore.se)”.
One H1 headline
Your <h1> is empty.
689 internal links, 8 external
The homepage links to 689 pages on shirtstore.eu and 8 external pages.
5 checks passed
Title: 33 characters
Your title is a healthy 33 characters: “Shirtstore - Buy t-shirts online!”.
Canonical URL set
The canonical URL is https://shirtstore.eu/.
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://shirtstore.eu/sitemap.xml.
AI search readiness
No llms.txt
There is no https://shirtstore.eu/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.
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.
Organization data: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (2,746 words), so crawlers that don't run JavaScript still read it.
Other pages
1 page without a title
https://shirtstore.eu/customer_authentication/redirect has no <title>, so Google invents the link text in results.
1 linked page hidden from search
https://shirtstore.eu/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
2 pages without a meta description
https://shirtstore.eu/customer_authentication/redirect and https://shirtstore.eu/collections/male have no meta description, so Google writes the search snippet from whatever text it finds.
1 page without an H1
https://shirtstore.eu/customer_authentication/redirect 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 198 found) and read each the way a search engine does.
3 checks passed
Linked pages load
7 pages of 15 loaded without an error (the rest turned automated requests away).
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.
Best practices
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
86 of 86 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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.
About 1,571 words of copy
The homepage carries about 1,571 words of visible text.
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “SHOP NOW” and “SHOP MTV”.
21 calls to action
The homepage has 21 calls to action, for example “SHOP NOW”, “SHOP MTV” and “SHOP CHEVY”.
5 short forms
5 short forms (1 field at most) are right on the homepage.
Direct contact links
Visitors can reach you directly: 0 phone links and 1 email link.
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
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Meta 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.
13 cookies set on arrival
13Opening the homepage sets 13 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.
18 other companies contacted
Loading the homepage contacts 18 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 shirtstore.eu, 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 9 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Geo Pro Geolocation · Xcloud Search Filter · Xo Insert Code · Mulwi Feeds · Easylocation · Givy · kxcdn.com · gropulse.com · elfsight.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
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 32 issues on shirtstore.eu, including 12 speed issues, 3 SEO issues 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.