majema.se website review

6 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.2 s.

8 third-party services load with your homepage (Google Tag Manager, Facebook and Clarity and others), adding 1.4 MB and 1.0 s of main-thread time.

Your mobile performance score is 84. Pages that score under 90 lose visitors before the first paint.

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

About 509 KiB of JavaScript is downloaded but never used on this page.

11 files are served with short cache lifetimes, so returning visitors download them again (259 KiB).

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

LiveChat costs a phone 98 ms of main-thread work and 367 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.

9 images could be 123 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.

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

Polyfills for old browsers add 13 KiB JavaScript that modern phones do not need.

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

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

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

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

Your largest element takes 2.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Home Image”.

The first text or image appears after 1.9 s on a phone. Good is under 1.8 s.

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

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

Your homepage downloads 3.1 MB in 254 requests on a phone: scripts 1.5 MB (51), other files 1.1 MB (175) and images 429 KiB (19). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example 1000x350_banner_matematik_larare_instruerar_majema_1592x.web at 1,000 px wide, shown at 234 px. Resized copies would save about 35 KiB.

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

2 images (111 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.

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

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

1 form field has no label, so screen readers announce an empty box and autofill guesses.

Elements with visible text labels do not have matching accessible names. (11 elements).

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

4 links have no real href, so search engines can't follow them.

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

The homepage links to 118 pages on majema.se and 4 external pages.

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.

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

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=11800767&tm=gtm002&Ver=2&mid=ba1a76c1-b2f2-44a5-8599-6ac2ae34f6f5&bo=1&sid=c7a93d40dd7011f1930f5577b9a84894&vid=c7a93570dd7011f18930cd49fd1d6748&vids=1&msclkid=N&pi=91.

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

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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 320 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Ads 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.

Opening the homepage sets 14 cookies, 1 of them by other companies (measured from a US location before any click).

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.

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