storstadning.nu
Storstädning - Göteborg - storstadning.nu
1 failed · 12 warnings · 16 passed
Audited Tue, 14 Jul 2026 11:15:51 GMT · https://storstadning.nu/
Meta & Head
19.4/25
Title, description, canonical, social tags — what search engines read first.
Open Graph tagsmedium impactlow effort
No Open Graph tags found
Open Graph tags control how your page looks when shared on Facebook, LinkedIn, Slack, WhatsApp, and most chat apps; without them, links render as a bare URL or with guessed text, and far fewer people click through. Add four meta tags to <head>: og:title, og:description, og:url, and og:image — an image around 1200x630 pixels works well across platforms. Use absolute https:// URLs for og:image and og:url; relative paths are the most common reason preview images silently fail to appear.
Canonical URLmedium impactlow effort
No <link rel="canonical"> found
When the same page is reachable at several URLs — tracking parameters, trailing-slash variants, http vs https — search engines may split ranking signals across the duplicates. A canonical tag names the one version that should get all the credit. Add <link rel="canonical" href="https://www.example.com/page/"> to the <head>, pointing at the page's preferred absolute URL. Double-check it's self-referencing on the primary version: a canonical that points at the wrong page can quietly de-index the right one.
Faviconlow impactlow effort
No <link rel="icon"> and /favicon.ico does not respond
Google displays favicons beside mobile search results, and browsers show them in tabs, bookmarks, and history — a missing icon makes your listing look generic and less trustworthy next to competitors. Create an icon of at least 48x48 pixels, serve it at /favicon.ico, and reference it with <link rel="icon" href="/favicon.png" type="image/png"> in <head>. Make sure robots.txt doesn't block the icon's path — search engines must be able to crawl it to display it.
Twitter card taglow impactlow effort
No twitter:card meta tag found
X (Twitter) layers its own card markup on top of Open Graph, and without a twitter:card tag your shared links may render as plain text instead of a large image preview. Add <meta name="twitter:card" content="summary_large_image"> alongside your Open Graph tags; X will fill in the title, description, and picture from og:title, og:description, and og:image. Keep og:image an absolute URL — a relative or missing image is the usual reason cards show up without a picture.
5 passing checks
- Title tag<title> is "Storstädning - Göteborg - storstadning.nu" (41 characters)
- Meta descriptionMeta description is "Alltid lågt pris för din hemstädning. För företag och privatpersoner. Kontakta oss." (83 characters)
- Viewport meta tagViewport is "width=device-width, initial-scale=1"
- Character encoding declaredCharacter encoding is declared
- Page allows indexingNo restrictive robots meta tag
Content & Structure
19.5/25
Headings, copy depth, images, structured data, internal linking.
Word counthigh impactlow effort
529 words of visible text
With only a few hundred words, this page gives search engines little to index and often loses to more thorough competitors targeting the same query. Expand it toward 600+ words of genuinely useful material: answer the questions visitors arrive with, and add examples, specifics, an FAQ section, or step-by-step detail. Don't pad with fluff or repeat keywords to hit a number — length should be a byproduct of covering the topic properly, never the goal itself.
Structured data (JSON-LD)medium impactmedium effort
No JSON-LD structured data blocks found
Structured data makes your listing eligible for rich results — star ratings, FAQs, breadcrumbs, product prices — which occupy more space on the results page and draw more clicks than plain blue links. Add a <script type="application/ld+json"> block with a schema.org type that matches the page: Organization or WebSite for a homepage, Article for posts, Product for product pages. Only mark up content actually visible on the page — markup for invisible content violates Google's guidelines and can earn a manual action.
Internal linkinglow impactlow effort
2 internal, 18 external links
Only a couple of internal links means crawlers see this page as loosely connected to the rest of your site, and less of its authority flows onward. Add contextual links to your most important related pages — in-body links with descriptive anchor text carry the most weight.
5 passing checks
- Single H1 heading1 h1 found: "Storstädning"
- Heading hierarchy22 headings in order without skipped levels
- Image alt text13 of 14 images have alt text
- HTML lang attribute<html lang="sv">
- JavaScript-dependent contentvisible text ~6033 chars in the initial HTML
Technical
18.8/25
HTTPS, redirects, robots, sitemap, speed, crawlability.
Fast time to first bytehigh impactmedium effort
952 ms
Time to first byte is the floor under every other speed metric — the browser can't parse, render, or fetch anything until the first byte arrives, so a slow TTFB drags down all Core Web Vitals and tests crawlers' patience. Add caching in front of the origin: full-page caching at a CDN (Cloudflare, Fastly) helps most, followed by server-side caches (Redis, object caching) and indexes on slow database queries. Measure from locations near your actual users — tuning only your fastest region leaves distant visitors just as slow.
HTTP redirects to HTTPSmedium impactlow effort
http:// version serves content without redirecting
Your http:// URLs serve content instead of redirecting, so search engines can crawl and index two parallel copies of every page and split ranking signals between them. Add a permanent 301 redirect from http to https at the server or CDN level — in nginx, "return 301 https://$host$request_uri;" in the port-80 server block; in Apache, a RewriteRule in .htaccess; on Cloudflare, enable "Always Use HTTPS". Use a 301, not a 302 — temporary redirects don't consolidate ranking signals — and preserve the full path in the redirect target.
robots.txt present and permissivemedium impactlow effort
no robots.txt found
Without a robots.txt, crawlers assume everything is allowed — not fatal, but you lose the ability to keep them out of low-value areas (internal search results, carts, admin paths) and the standard place to advertise your sitemap. Create a plain-text robots.txt at the site root with at least a "User-agent: *" line and "Sitemap: https://www.example.com/sitemap.xml". Don't use it to hide sensitive URLs, though — the file is public, and disallowing a page doesn't remove it from the index; use noindex or authentication for that.
XML sitemap availablemedium impactlow effort
no sitemap.xml found
Without an XML sitemap, search engines discover pages only by following links, so new, deep, or weakly linked pages get found slowly or not at all. Generate one at /sitemap.xml — most frameworks and CMSs have a generator built in or as a plugin — listing every canonical, indexable URL, then add "Sitemap: https://www.example.com/sitemap.xml" to robots.txt and submit it in Google Search Console. Keep it clean: listing redirected, noindexed, or 404 URLs erodes crawler trust in the whole file.
Response compression enabledlow impactlow effort
no content-encoding header
This HTML is served uncompressed, so every visitor downloads far more bytes than necessary — text compresses extremely well, and the savings directly speed up first render on slow connections. Enable Brotli or gzip on your server or CDN: in nginx it's "gzip on;" (or the brotli module), in Apache it's mod_deflate via .htaccess, and on most CDNs it's a single toggle. Make sure compression covers all text types (HTML, CSS, JS, JSON, SVG), but skip already-compressed images — recompressing them wastes CPU for no gain.
Missing pages return 404low impactlow effort
missing paths return a non-404 status (soft 404)
URLs that don't exist on your site return a success status instead of 404 — search engines call these soft 404s, keep recrawling them, and may index the useless placeholder pages, wasting crawl budget that should go to real content. Configure your server or framework to return an actual 404 status (or 410 for permanently removed content) along with your error page. The classic mistake is serving a friendly "page not found" template with a 200 status — crawlers ignore the visible message; only the status code counts.
6 passing checks
- Served over HTTPSfinal URL uses https://
- No mixed content0 http:// subresource references
- Short redirect chainno redirects; URL resolves directly
- Reasonable HTML size19.1 KB
- www and non-www resolve consistentlywww and non-www converge on the same host
- HTML5 doctype<!DOCTYPE html> present
Performance
Core Web Vitals scoring via Google PageSpeed is coming soon.
Share your score
Embed this live badge on your site — it updates whenever the audit is re-run.