Website review, no card needed

lomma.se logo

lomma.se website review

Visit site (opens in a new tab)Reviewed 29 October 202619 issues · 72 checks

This review found 19 issues worth fixing on lomma.se, 6 of them high impact, across 72 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
946 ms738 msMay 9Oct 24836 ms
Show as table
DateReal-visitor load time (LCP)
May 9, 2026780 ms
May 16, 2026762 ms
May 23, 2026763 ms
May 30, 2026802 ms
Jun 6, 2026836 ms
Jun 13, 2026836 ms
Jun 20, 2026846 ms
Jun 27, 2026854 ms
Jul 4, 2026868 ms
Jul 11, 2026894 ms
Jul 18, 2026922 ms
Jul 25, 2026920 ms
Aug 1, 2026901 ms
Aug 8, 2026869 ms
Aug 15, 2026846 ms
Aug 22, 2026835 ms
Aug 29, 2026823 ms
Sep 5, 2026826 ms
Sep 12, 2026821 ms
Sep 19, 2026822 ms
Sep 26, 2026834 ms
Oct 3, 2026843 ms
Oct 10, 2026836 ms
Oct 17, 2026836 ms
Oct 24, 2026836 ms
Real-visitor tap response (INP)75th percentile, phones
89 ms78 msMay 9Oct 2488 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 202682 ms
May 16, 202681 ms
May 23, 202681 ms
May 30, 202681 ms
Jun 6, 202684 ms
Jun 13, 202683 ms
Jun 20, 202682 ms
Jun 27, 202681 ms
Jul 4, 202680 ms
Jul 11, 202679 ms
Jul 18, 202679 ms
Jul 25, 202681 ms
Aug 1, 202680 ms
Aug 8, 202679 ms
Aug 15, 202679 ms
Aug 22, 202679 ms
Aug 29, 202679 ms
Sep 5, 202681 ms
Sep 12, 202681 ms
Sep 19, 202683 ms
Sep 26, 202684 ms
Oct 3, 202684 ms
Oct 10, 202685 ms
Oct 17, 202687 ms
Oct 24, 202688 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of lomma.se (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. lomma.se at 0.8 s0.8 s
  2. lomma.se at 1.7 s1.7 s
  3. lomma.se at 2.5 s2.5 s
  4. lomma.se at 3.4 s3.4 s
  5. lomma.se at 4.2 s4.2 s
  6. lomma.se at 5.1 s5.1 s
  7. lomma.se at 5.9 s5.9 s
  8. lomma.se at 6.8 s6.8 s

Speed

3 to fix79
  • Render-blocking requests

    2.9 s

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

  • Improve image delivery

    3.4 MB

    2 images could be 3.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Mobile performance score: 79

    79/100

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

  • Reduce unused CSS

    50 ms · 31 KiB

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

  • 2 third-party services on the page

    2 third-party services load with your homepage (rekai.se and Plausible), adding 30 KiB and 72 ms of main-thread time.

  • 2 long tasks on the main thread

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

  • Use efficient cache lifetimes

    24 KiB

    1 file is served with short cache lifetimes, so returning visitors download them again (24 KiB).

  • Legacy JavaScript

    16 KiB

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

  • 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.

  • Forced reflow

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

  • Minify JavaScript

    3 KiB

    3 KiB could be saved by minifying JavaScript.

2 checks passed
  • Main-thread work: 1.0 s

    A phone's processor spends 1.0 s on main-thread work while loading, 321 ms of it running JavaScript. That is comfortably low.

  • Server response: 201 ms

    201 ms

    Your server sent the HTML in 201 ms, well inside Google's 600 ms guideline.

Core Web Vitals

5 to fix100
  • Speed Index: 6.8 s

    6.8 s

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

  • First Contentful Paint: 2.8 s

    2.8 s

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

  • Largest Contentful Paint: 3.3 s

    3.3 s

    Your largest element takes 3.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Pausa/spela upp video”. Most of its time is element render delay (1.9 s).

  • Cumulative Layout Shift: 0.113

    0.113

    The layout shifts by 0.113 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Time to Interactive: 4.1 s

    4.1 s

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

  • Tap response (INP) held steady for real visitors

    +7%

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

  • Largest content (LCP) held steady for real visitors

    +8%

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

7 checks passed
  • Passes Core Web Vitals for real visitors

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

  • Real-user LCP: 1.2 s

    1.2 s

    Real visitors wait 1.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 112 ms

    112 ms

    Real visitors wait 112 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.10

    0.10

    For real visitors the layout shifts by 0.10 (75th percentile). Good is under 0.1.

  • Real-user FCP: 0.8 s

    0.8 s

    Real visitors see the first content after 0.8 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 281 ms

    281 ms

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

  • Total Blocking Time: 16 ms

    16 ms

    Scripts block the page for only 16 ms while loading. Good is under 200 ms.

Images and page weight

1 to fix70
  • Page weight: 4.0 MB in 85 requests

    4.0 MB

    Your homepage downloads 4.0 MB in 85 requests on a phone: images 3.6 MB (6), scripts 227 KiB (20) and stylesheets 118 KiB (44). Under 2 MB keeps phones on slow connections fast.

  • 1 image below the first screen load straight away

    1 image further down the page (20 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 1.1 g of CO₂ per visit

    1.14 g

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

2 checks passed
  • 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

1 to fixGoogle 10099
  • 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.

2 checks passed
  • Every image has alt text

    All 4 images in the HTML carry an alt attribute.

  • 42 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 43 WCAG 2.2 A/AA and best-practice rules on the phone render: 42 passed and 1 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 10084
  • Title is short (12 characters)

    Your title is only 12 characters: “Lomma kommun”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

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

  • 3 H1 headlines

    There are 3 <h1> headlines (“Välkommen!”, “Välkommen!” and “Mer om oss”). One clear main headline is easier for people and search engines.

  • 45 internal links, 1 external

    The homepage links to 45 pages on lomma.se and 1 external page.

5 checks passed
  • Meta description: 92 characters

    Your meta description is 92 characters: “Lomma kommun – havsnära boende, starkt näringsliv och hållbar utveckling nära Malmö och Lund”.

  • Canonical URL set

    The canonical URL is https://lomma.se/.

  • 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://lomma.se/sitemapindex.xml.

AI search readiness

1 to fix88
  • 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.

  • No llms.txt

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

2 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 (568 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix95
  • 12 pages without a meta description

    https://lomma.se/kommunochpolitik/politikochdemokrati/dialogochsynpunkter/eforslag.3489.html, https://lomma.se/ovrigasidor/kontaktaoss.1908.html, https://lomma.se/barnochutbildning.762.html, https://lomma.se/omsorgochstod.769.html, https://lomma.se/byggaboochmiljo.795.html and https://lomma.se/jobbochforetagande.796.html and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 3 pages with very little text

    https://lomma.se/barnochutbildning.762.html, https://lomma.se/upplevaochgora.770.html and https://lomma.se/trafikochgator.797.html 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 27 found) and read each the way a search engine does.

6 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • 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 15 pages that loaded have a <title>.

Best practices

1 to fixGoogle 10093
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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

3 to fix50
  • 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 social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust 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 479 words of copy

    The homepage carries about 479 words of visible text.

3 checks passed
  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Plausible.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 1 email link.

Privacy and tracking

  • 2 cookies set on arrival

    2

    Opening the homepage sets 2 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.

  • 4 other companies contacted

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

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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 lomma.se, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Analytics
Plausible
Hosting
Sitevision

Company

Employees
1,375
Founded
1971

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 19 issues on lomma.se, including 8 speed issues, 3 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25