Website review, no card needed
tramontana.eu website review
Visit site (opens in a new tab)Reviewed 19 October 202634 issues · 80 checks
This review found 34 issues worth fixing on tramontana.eu, 16 of them high impact, across 80 checks. The most urgent: use efficient cache lifetimes. 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
75C- #81,212 of 124,051 reviewed websitesbeats 30%
- #51,538 of 69,761 online storesbeats 22%
- #56 of 83 Shopware storesbeats 26%
Closest competitors among Shopware stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Apr 25, 2026 | 786 ms |
| May 2, 2026 | 803 ms |
| May 9, 2026 | 811 ms |
| May 16, 2026 | 839 ms |
| May 23, 2026 | 821 ms |
| May 30, 2026 | 813 ms |
| Jun 6, 2026 | 832 ms |
| Jun 13, 2026 | 847 ms |
| Jun 20, 2026 | 888 ms |
| Jun 27, 2026 | 909 ms |
| Jul 4, 2026 | 896 ms |
| Jul 11, 2026 | 884 ms |
| Jul 18, 2026 | 844 ms |
| Jul 25, 2026 | 850 ms |
| Aug 1, 2026 | 834 ms |
| Aug 8, 2026 | 841 ms |
| Aug 15, 2026 | 802 ms |
| Aug 22, 2026 | 783 ms |
| Aug 29, 2026 | 790 ms |
| Sep 5, 2026 | 773 ms |
| Sep 12, 2026 | 802 ms |
| Sep 19, 2026 | 791 ms |
| Sep 26, 2026 | 778 ms |
| Oct 3, 2026 | 791 ms |
| Oct 10, 2026 | 785 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Apr 25, 2026 | 95 ms |
| May 2, 2026 | 94 ms |
| May 9, 2026 | 94 ms |
| May 16, 2026 | 95 ms |
| May 23, 2026 | 96 ms |
| May 30, 2026 | 98 ms |
| Jun 6, 2026 | 103 ms |
| Jun 13, 2026 | 106 ms |
| Jun 20, 2026 | 106 ms |
| Jun 27, 2026 | 110 ms |
| Jul 4, 2026 | 109 ms |
| Jul 11, 2026 | 107 ms |
| Jul 18, 2026 | 105 ms |
| Jul 25, 2026 | 106 ms |
| Aug 1, 2026 | 108 ms |
| Aug 8, 2026 | 108 ms |
| Aug 15, 2026 | 111 ms |
| Aug 22, 2026 | 109 ms |
| Aug 29, 2026 | 108 ms |
| Sep 5, 2026 | 110 ms |
| Sep 12, 2026 | 110 ms |
| Sep 19, 2026 | 112 ms |
| Sep 26, 2026 | 113 ms |
| Oct 3, 2026 | 113 ms |
| Oct 10, 2026 | 111 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
How it loaded on a phone
0.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Use efficient cache lifetimes
64.9 s · 15.2 MB41 files are served with short cache lifetimes, so returning visitors download them again (15.2 MB).
Improve image delivery
61.9 s · 11.9 MB6 images could be 11.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 61.9 s faster on a phone.
Render-blocking requests
2.3 s2 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.3 s.
Reduce unused JavaScript
1.8 s · 337 KiBAbout 337 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.8 s faster on a phone.
Mobile performance score: 22
22/100Your mobile performance score is 22 (desktop: 39). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
6 third-party services on the page
6 third-party services load with your homepage (Google Tag Manager, cdn-cookieyes.com and leadinfo.net and others), adding 614 KiB and 581 ms of main-thread time.
Google Tag Manager adds 548 ms
548 msGoogle Tag Manager costs a phone 548 ms of main-thread work and 523 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
450 ms · 71 KiBAbout 71 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.
Main-thread work: 2.1 s
A phone's processor spends 2.1 s on main-thread work while loading, 901 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Legacy JavaScript
250 ms · 20 KiBPolyfills for old browsers add 20 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 250 ms faster on a phone.
11 long tasks on the main thread
11 long tasks block the main thread while loading, the longest for 220 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.
1 checks passed
Server response: 4 ms
4 msYour server sent the HTML in 4 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Cumulative Layout Shift: 1.422
1.422The layout shifts by 1.422 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Largest Contentful Paint: 78.4 s
78.4 sYour largest element takes 78.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Speed Index: 20.0 s
20.0 sVisually, the page fills in at 20.0 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 79.3 s
79.3 sThe page becomes fully interactive after 79.3 s. Good is under 3.8 s.
First Contentful Paint: 3.1 s
3.1 sThe first text or image appears after 3.1 s on a phone. Good is under 1.8 s.
Total Blocking Time: 512 ms
512 msScripts block taps and scrolling for 512 ms in total while the page loads. Good is under 200 ms.
6 images without width and height
6 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 19% slower for real visitors
+19%Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' tap response (inp) went from 95 ms to 111 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-1%Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' largest content (lcp) went from 0.8 s to 0.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 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 sReal visitors wait 1.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 76 ms
76 msReal visitors wait 76 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: 0.8 s
0.8 sReal visitors see the first content after 0.8 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 403 ms
403 msReal visitors wait 403 ms for your server to start answering (75th percentile). Good is under 800 ms.
Images and page weight
Page weight: 16.0 MB in 69 requests
16.0 MBYour homepage downloads 16.0 MB in 69 requests on a phone: images 15.0 MB (11), scripts 853 KiB (38) and stylesheets 74 KiB (2). Under 2 MB keeps phones on slow connections fast.
6 images over 500 KB
6 images weigh 15.0 MB together. On a phone connection a single image that size takes seconds.
5 images far larger than shown
7.6 MB5 images are downloaded at several times the size a phone draws them, for example MIDDEN-3_(3).jpg at 1,617 px wide, shown at 320 px. Resized copies would save about 7.6 MB.
6 images in older formats
6 images (15.0 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.
An image on the first screen is lazy-loaded
MIDDEN-1_(3).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).
1 image below the first screen load straight away
1 image further down the page (21 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 4.5 g of CO₂ per visit
4.54 gBy the Sustainable Web Design model, a visit to your homepage emits about 4.54 g of CO₂e: 544.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
All page content should be contained by landmarks (4 elements)
All page content should be contained by landmarks: 4 elements on the page fail this check, rated moderate by axe-core.
Heading levels should only increase by one (1 element)
Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
5 links without text
5 visible links have no text or label, so screen readers cannot say where they go.
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
2 checks passed
Every image has alt text
All 18 images in the HTML carry an alt attribute.
47 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 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
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is short (24 characters)
Your title is only 24 characters: “Your fashion compliment!”. Between 30 and 65 characters leaves room to say what you do and for whom.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No XML sitemap
No XML sitemap at https://www.tramontana.eu/sitemap.xml, so Google discovers your pages only by following links.
80 internal links, 10 external
The homepage links to 80 pages on tramontana.eu and 10 external pages.
4 checks passed
Meta description: 142 characters
Your meta description is 142 characters: “Tramontana, jouw Fashion Compliment, biedt veelzijdige, stijlvolle kleding die je zelfvertrouwen versterkt en je persoo…”.
Canonical URL set
The canonical URL is https://www.tramontana.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.
AI search readiness
No Organization structured data
There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.
No llms.txt
There is no https://www.tramontana.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.
1 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.
Other pages
15 internal pages checked
We fetched 15 pages linked from your homepage (of 52 found) and read each the way a search engine does.
7 checks passed
Linked pages load
14 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.
Every page has a meta description
All 14 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 14 pages that loaded have a <title>.
Best practices
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
9 of 11 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
Only about 24 words
The homepage has only about 24 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
4 checks passed
1 call to action
The homepage has 1 call to action, for example “Contact”.
2 short forms
2 short forms (2 fields at most) are right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 1 phone link and 0 email links.
Privacy and tracking
2 trackers load before any consent
2Before a visitor clicks anything, the page loads Google Ads and Google Tag Manager (measured from a US location before any click). A consent tool (CookieYes) is installed; check it blocks these until visitors agree where the law requires it.
3 cookies set on arrival
3Opening the homepage sets 3 cookies (measured from a US location before any click).
10 other companies contacted
Loading the homepage contacts 10 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: CookieYes
A consent management tool (CookieYes) loads with the page.
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 tramontana.eu, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- Tailwind CSS
- Analytics
- Google Tag Manager
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 tramontana.eu, including 16 speed issues, 4 SEO issues 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.