Website review, no card needed
pryloasen.se website review
Visit site (opens in a new tab)Reviewed 6 November 202633 issues · 74 checks
This review found 33 issues worth fixing on pryloasen.se, 10 of them high impact, across 74 checks. The most urgent: reduce unused JavaScript. 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
Speed
Reduce unused JavaScript
1.6 s · 320 KiBAbout 320 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.6 s faster on a phone.
Improve image delivery
1.1 s · 429 KiB5 images could be 429 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.1 s faster on a phone.
Render-blocking requests
1.3 s6 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.3 s.
Mobile performance score: 69
69/100Your mobile performance score is 69. Pages that score under 90 lose visitors before the first paint.
Reduce unused CSS
450 ms · 84 KiBAbout 84 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.
2 long tasks on the main thread
2 long tasks block the main thread while loading, the longest for 412 ms. During a long task the page ignores taps.
5 third-party services on the page
5 third-party services load with your homepage (Shopify, Klaviyo and shop.app and others), adding 1.2 MB and 267 ms of main-thread time.
Main-thread work: 3.8 s
A phone's processor spends 3.8 s on main-thread work while loading, 1.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Shopify adds 205 ms
205 msShopify costs a phone 205 ms of main-thread work and 939 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.
2,031 HTML elements
The page has 2,031 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Legacy JavaScript
150 ms · 30 KiBPolyfills for old browsers add 30 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Use efficient cache lifetimes
38 KiB7 files are served with short cache lifetimes, so returning visitors download them again (38 KiB).
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.
1 checks passed
Server response: 41 ms
41 msYour server sent the HTML in 41 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 11.0 s
11.0 sYour largest element takes 11.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 11.1 s
11.1 sThe page becomes fully interactive after 11.1 s. Good is under 3.8 s.
Speed Index: 4.8 s
4.8 sVisually, the page fills in at 4.8 s (Speed Index). Good is under 3.4 s.
3 images without width and height
3 images have no width and height attributes, so the layout jumps as each one loads.
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
Total Blocking Time: 188 ms
188 msScripts block the page for only 188 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0.004
0.004The layout barely moves while loading (CLS 0.004, good is under 0.1).
First Contentful Paint: 1.1 s
1.1 sThe first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.
Images and page weight
Page weight: 3.9 MB in 381 requests
3.9 MBYour homepage downloads 3.9 MB in 381 requests on a phone: images 1.3 MB (14), scripts 1.1 MB (180) and other files 931 KiB (155). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
hf_20260914_112010_19ca88c0-e51e-40a7-b594-b13878c95725_2000 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).
2 images far larger than shown
293 KiB2 images are downloaded at several times the size a phone draws them, for example hf_20260914_112010_19ca88c0-e51e-40a7-b594-b13878c95725_2000 at 2,000 px wide, shown at 378 px. Resized copies would save about 293 KiB.
About 1.1 g of CO₂ per visit
1.10 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.10 g of CO₂e: 132.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Accessibility
9 text elements with low contrast
9 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
4 tap targets too small
4 tap targets are too small or too close together to hit reliably with a finger.
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.
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.
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 (3 elements)
Alternative text of images should not be repeated as text: 3 elements on the page fail this check, rated minor by axe-core.
2 checks passed
Every image has alt text
All 26 images in the HTML carry an alt attribute.
43 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 49 WCAG 2.2 A/AA and best-practice rules on the phone render: 43 passed and 6 failed. 4 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.
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
155 internal links, 2 external
The homepage links to 155 pages on pryloasen.se and 2 external pages.
7 checks passed
Meta description: 139 characters
Your meta description is 139 characters: “Shoppa prisvärt inom köksprylar, heminredning, prylar för trädgården och mycket mer. Här får du ✓ lägre priser ✓ snabb …”.
Title: 52 characters
Your title is a healthy 52 characters: “Pryloasen - Kvalitativa Produkter Till Bättre Priser”.
Canonical URL set
The canonical URL is https://pryloasen.se/.
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://pryloasen.se/sitemap.xml.
AI search readiness
No llms.txt
There is no https://pryloasen.se/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 description; contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (871 words), so crawlers that don't run JavaScript still read it.
Other pages
2 pages without a meta description
https://pryloasen.se/collections/julgranspynt and https://pryloasen.se/collections/juldekorationer-1 have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages share a meta description
https://pryloasen.se/collections/fardiga-presentpaket and https://pryloasen.se/collections/nyheter use the same meta description. A description written for each page earns more clicks.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 67 found) and read each the way a search engine does.
6 checks passed
Linked pages load
10 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.
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 10 pages that loaded have a <title>.
Best practices
13 small tap targets
13 of 44 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
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
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 calls to action
We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.
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.
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 291 words of copy
The homepage carries about 291 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
2 checks passed
2 short forms
2 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 61 testimonial or review blocks and a star rating.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 1 more (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.
14 cookies set on arrival
14Opening the homepage sets 14 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.
21 other companies contacted
Loading the homepage contacts 21 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 pryloasen.se, 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 6 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Ta Labels Badges · Kaching Bundles · Inbox · Kaching Cart · Klaviyo Email Marketing Sms · Kaching Popup
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
- Framework
- jQuery
- 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 33 issues on pryloasen.se, including 14 speed issues, 2 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.