pagen.se website review

38 files are served with short cache lifetimes, so returning visitors download them again (1.3 MB).

elfsightcdn.com costs a phone 1.2 s of main-thread work and 719 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

A phone's processor spends 4.5 s on main-thread work while loading, 2.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

7 third-party services load with your homepage (elfsightcdn.com, Google Tag Manager and Cookiebot and others), adding 1.6 MB and 2.0 s of main-thread time.

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

About 464 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 750 ms faster on a phone.

Your mobile performance score is 52 (desktop: 48). Pages that score under 90 lose visitors before the first paint.

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

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 350 ms).

About 48 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.

1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 300 ms.

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

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

3 KiB could be saved by minifying CSS.

Your largest element takes 6.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Två brödnyheter - Protein Sandwih och Skördefest”.

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

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

Scripts block taps and scrolling for 685 ms in total while the page loads. Good is under 200 ms.

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

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

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

Your homepage downloads 3.4 MB in 63 requests on a phone: images 2.0 MB (32), scripts 1.2 MB (11) and other files 85 KiB (14). Under 2 MB keeps phones on slow connections fast.

muslibrod-reminder-4x5-receptbild.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).

5 images (156 KiB) 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.

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

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

Some list items are not inside a list.

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

All page content should be contained by landmarks: 26 elements on the page fail this check, rated moderate by axe-core.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

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. (1 element).

7 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

The homepage links to 110 pages on pagen.se and 15 external pages.

There is no https://www.pagen.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.

https://www.pagen.se/sok is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://www.pagen.se/recept and https://www.pagen.se/link/f8fb821ef123442793b7d060b2014899.aspx all use the title “Inspiration till mat och bakning - få våra tips här | Pågen”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.pagen.se/recept and https://www.pagen.se/link/f8fb821ef123442793b7d060b2014899.aspx use the same meta description. A description written for each page earns more clicks.

Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://www.pagen.se/link/f8fb821ef123442793b7d060b2014899.aspx, whose canonical is https://www.pagen.se/recept. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

We fetched 15 pages linked from your homepage (of 77 found) and read each the way a search engine does.

65 of 95 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage shows no opening hours. If customers visit or call, show when.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 731 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 6 cookies (measured from a US location before any click).

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