motala.se website review

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

3 images could be 306 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.

Your mobile performance score is 45 (desktop: 87). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

8 third-party services load with your homepage (rekai.se, Other Google APIs/SDKs and piwik.pro and others), adding 396 KiB and 842 ms of main-thread time.

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

About 54 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 600 ms faster on a phone.

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

rekai.se costs a phone 367 ms of main-thread work and 49 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.

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

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

8 KiB could be saved by minifying CSS.

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

Desktop scores 87 but mobile only 45. A gap that wide usually means heavy scripts and images that hit phones hardest.

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

7 KiB could be saved by minifying JavaScript.

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.

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

Your largest element takes 7.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Skriv in sökord”.

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

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

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

Real visitors wait 862 ms for your server to start answering (75th percentile). Good is under 800 ms.

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

6 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 93 ms to 88 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

1 image is downloaded at several times the size a phone draws it, for example motala_kommun_logo_bla_cookie.png at 2,148 px wide, shown at 120 px. Resized copies would save about 126 KiB.

1 image (130 KiB) is 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.36 g of CO₂e: 43.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Certain ARIA roles must contain particular children: 3 elements on the page fail this check, rated critical by axe-core.

1 element use ARIA attributes their role does not allow, which confuses screen readers.

Some list items are not inside a list.

Some lists contain elements other than list items, which screen readers announce wrongly.

1 frame has no title, so screen-reader users cannot tell what it contains.

Document should not have more than one banner landmark: 1 element on the page fails 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.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

5 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).

Your meta description is only 54 characters: “Information om Motala kommuns service och verksamheter”. 70 to 160 characters is enough to sell the click.

There are 3 <h1> headlines (“”, “Välkommen till Motala kommun!” and “Du använder en omodern webbläsare”). One clear main headline is easier for people and search engines.

The homepage links to 1,439 pages on motala.se and 7 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.

There is no https://www.motala.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.motala.se/skola-och-forskola/arbetsmiljo-i-skola-och-forskola, https://www.motala.se/skola-och-forskola/digitala-verktyg-i-skolan, https://www.motala.se/skola-och-forskola/elevhalsa, https://www.motala.se/skola-och-forskola/elevsystemet-meitner, https://www.motala.se/skola-och-forskola/forskola-och-barnomsorg/ansok-om-plats-i-forskola-eller-fritidshem and https://www.motala.se/skola-och-forskola/forskola-och-barnomsorg/ansok-om-plats-i-forskola-eller-fritidshem/delad-placering-i-forskola-eller-fritidshem and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.

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

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

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

Chrome logged issues while loading the page (“Cookie”).

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.

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

Opening the homepage sets 1 cookie (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 14 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.