Website review, no card needed
amandabywinther.com website review
Visit site (opens in a new tab)Reviewed 13 November 202625 issues · 70 checks
This review found 25 issues worth fixing on amandabywinther.com, 6 of them high impact, across 70 checks. The most urgent: 24 text elements with low contrast. 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
One score from every part of this review. How it works
How it loaded on a phone
0.5 s
1.1 s
1.6 s
2.1 s
2.6 s
3.2 s
3.7 s
4.2 s
Speed
Mobile performance score: 88
88/100Your mobile performance score is 88. Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
850 ms4 files block the first paint until they finish downloading. Deferring or inlining them could save about 850 ms.
Reduce unused JavaScript
470 ms · 269 KiBAbout 269 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 470 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Google CDN and Google Analytics and others), adding 572 KiB and 294 ms of main-thread time.
Improve image delivery
150 ms · 92 KiB6 images could be 92 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.
2 long tasks on the main thread
2 long tasks block the main thread while loading, the longest for 147 ms. During a long task the page ignores taps.
Use efficient cache lifetimes
74 KiB7 files are served with short cache lifetimes, so returning visitors download them again (74 KiB).
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Reduce unused CSS
20 ms · 13 KiBAbout 13 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 20 ms faster on a phone.
Minify JavaScript
23 KiB23 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.
2 checks passed
Main-thread work: 1.1 s
A phone's processor spends 1.1 s on main-thread work while loading, 512 ms of it running JavaScript. That is comfortably low.
Server response: 5 ms
5 msYour server sent the HTML in 5 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 3.6 s
3.6 sYour largest element takes 3.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “MEST POPULÆRE SE ALLE”.
Time to Interactive: 5.3 s
5.3 sThe page becomes fully interactive after 5.3 s. Good is under 3.8 s.
Speed Index: 3.7 s
3.7 sVisually, the page fills in at 3.7 s (Speed Index). Good is under 3.4 s.
Not enough real-visitor data yet
Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.
3 checks passed
Cumulative Layout Shift: 0.046
0.046The layout barely moves while loading (CLS 0.046, good is under 0.1).
Total Blocking Time: 76 ms
76 msScripts block the page for only 76 ms while loading. Good is under 200 ms.
First Contentful Paint: 0.9 s
0.9 sThe first text or image appears after 0.9 s, inside the 1.8 s “good” threshold.
Images and page weight
1 image below the first screen load straight away
1 image further down the page (29 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 0.6 g of CO₂ per visit
0.56 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.56 g of CO₂e: 66.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Page weight: 2.0 MB in 149 requests
2.0 MBYour homepage downloads 2.0 MB in 149 requests on a phone: other files 784 KiB (98), scripts 700 KiB (26) and images 389 KiB (13). That is a lean page.
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
24 text elements with low contrast
24 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
ARIA input fields must have an accessible name (1 element)
ARIA input fields must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.
ARIA toggle fields must have an accessible name (1 element)
ARIA toggle fields must have an accessible name: 1 element on the page fails this check, rated serious 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.
Headings skip levels
Headings skip levels (h2 → h4, h2 → h5 and h2 → h5), which makes the page harder to scan with a screen reader.
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 37 images in the HTML carry an alt attribute.
49 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 54 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 passed and 5 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (87 characters)
Your title is 87 characters, so Google will cut it off around 60: “Håndlavede uldhatte, julepynt, uldsokker, accessories og meget mere – Amanda by Winther”.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
2 H1 headlines
There are 2 <h1> headlines (“Amanda by Winther” and “Messer:”). One clear main headline is easier for people and search engines.
Meta description is long (191 characters)
Your meta description is 191 characters; Google truncates after about 160, so the end of your pitch is cut.
72 internal links, 5 external
The homepage links to 72 pages on amandabywinther.com and 5 external pages.
4 checks passed
Canonical URL set
The canonical URL is https://www.amandabywinther.com/.
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.amandabywinther.com/sitemap.xml.
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.
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 (597 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.amandabywinther.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a title
https://www.amandabywinther.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.
1 linked page hidden from search
https://www.amandabywinther.com/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://www.amandabywinther.com/pages/kontakt-os and https://www.amandabywinther.com/customer_authentication/redirect have no meta description, so Google writes the search snippet from whatever text it finds.
9 links to non-canonical URLs
Your homepage links to 9 pages by a URL that isn't their canonical one, for example https://www.amandabywinther.com/collections/mest-populaere/products/tynde-sokker-i-uld-alpaca, whose canonical is https://www.amandabywinther.com/products/tynde-sokker-i-uld-alpaca. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
2 pages without an H1
https://www.amandabywinther.com/collections and https://www.amandabywinther.com/customer_authentication/redirect have no <h1> headline, so visitors and search engines get no clear main topic.
2 pages with very little text
https://www.amandabywinther.com/collections and https://www.amandabywinther.com/pages/kontakt-os have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 49 found) and read each the way a search engine does.
2 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Titles are unique
Every page we checked has its own title.
Best practices
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “Shopify's Google Analytics stub called with: [array Array] See https://help.shopify.com/manual/promoting-marketing/pixe…”.
2 checks passed
Tap targets are thumb-sized
22 of 24 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.
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 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 375 words of copy
The homepage carries about 375 words of visible text.
3 checks passed
2 calls to action
The homepage has 2 calls to action, for example “Shop”.
4 short forms
4 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Analytics.
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.
10 cookies set on arrival
10Opening the homepage sets 10 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.
16 other companies contacted
Loading the homepage contacts 16 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 amandabywinther.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 2 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Eu Cookie Bar · aaawebstore.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
- Analytics
- Google Analytics
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 25 issues on amandabywinther.com, including 6 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.