cheezixbaits.se
Cheezix Baits | Soft Baits for Trout Fishing
0 failed · 6 warnings · 23 passed
Audited Fri, 07 Aug 2026 13:00:30 GMT · https://cheezixbaits.se/
Meta & Head
24.3/25
Title, description, canonical, social tags — what search engines read first.
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.
8 passing checks
- Title tag<title> is "Cheezix Baits | Soft Baits for Trout Fishing" (44 characters)
- Meta descriptionMeta description is "Extra-soft silicone baits, trout sets and fishing accessories designed for trout, perch and chub. Shop Cheezix Baits, shipped from Sweden." (138 characters)
- Canonical URLCanonical href is "https://cheezixbaits.se/"
- Viewport meta tagViewport is "width=device-width,initial-scale=1"
- Character encoding declaredCharacter encoding is declared
- Open Graph tagsAll core Open Graph tags present (og:title, og:description, og:image, og:url)
- Twitter card tagtwitter:card is "summary_large_image"
- Page allows indexingNo restrictive robots meta tag
Content & Structure
22.7/25
Headings, copy depth, images, structured data, internal linking.
Image alt textmedium impactlow effort
5 of 10 images have alt text
Alt text is how search engines understand what an image shows — it feeds image-search rankings and is what screen readers announce to blind visitors. Add a short, specific alt attribute to every meaningful image, describing the content rather than listing keywords: alt="Golden retriever puppy playing in snow" beats alt="dog puppy pet animal". Give purely decorative images an empty alt="" instead of omitting the attribute, so assistive technology knows to skip them rather than reading out the filename.
Heading hierarchylow impactlow effort
Heading level jumps from h2 ("Search") to h4 ("Products")
Headings form the page's outline; when levels jump (h2 straight to h4), search engines and screen readers get a broken table of contents and the relationship between sections turns ambiguous. Fix the jump by stepping down one level at a time — promote the deeper heading, or add the missing intermediate level. The usual cause is choosing heading tags for their default font size; set sizes in CSS instead and let the tags reflect actual document structure.
6 passing checks
- Single H1 heading1 h1 found: "Cheezix Baits"
- Word count6139 words of visible text
- Structured data (JSON-LD)JSON-LD types found: Organization
- HTML lang attribute<html lang="en">
- JavaScript-dependent contentvisible text ~19655 chars in the initial HTML
- Internal linking40 internal, 1 external links
Technical
21.6/25
HTTPS, redirects, robots, sitemap, speed, crawlability.
Fast time to first bytehigh impactmedium effort
905 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.
Short redirect chainmedium impactlow effort
https://cheezixbaits.com/ (301) → https://cheezixbaits.se/
Every redirect hop adds a round-trip before the visitor sees anything, each hop can leak a little link equity, and crawlers abandon long chains — which can leave the destination page undiscovered. Trace the chain above and point the first URL directly at the final destination in a single 301; commonly this means merging separate http-to-https and non-www-to-www rules into one combined redirect. Also update internal links to reference the final URL directly, so most visitors never enter the chain at all.
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.
9 passing checks
- Served over HTTPSfinal URL uses https://
- HTTP redirects to HTTPShttp:// redirects to https://
- No mixed content0 http:// subresource references
- robots.txt present and permissiverobots.txt exists and allows crawling
- XML sitemap availablesitemap.xml exists and is valid XML
- Reasonable HTML size267.8 KB
- Missing pages return 404missing paths return HTTP 404/410
- 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.