vogheracountryfestival.com
Voghera Country Festival |
1 failed · 11 warnings · 18 passed
Audited Fri, 17 Jul 2026 00:00:19 GMT · https://www.vogheracountryfestival.com/
Meta & Head
20.8/25
Title, description, canonical, social tags — what search engines read first.
Title taghigh impactlow effort
<title> is "Voghera Country Festival |" (26 characters)
Search engines truncate titles past roughly 60 characters and often rewrite very short or vague ones, so the message you wrote may never actually be shown. Rewrite the title to 30–60 characters that lead with the primary keyword and end with your brand, e.g. "Merge PDF Files Online Free | YourBrand". Front-load the important words, since truncation always cuts from the end. Don't pad a short title with repeated keywords just to hit the range — clarity wins clicks, not length.
Open Graph tagsmedium impactlow effort
Missing Open Graph tags: og:image
Your Open Graph markup is incomplete, so social platforms fall back to guessed text or drop the preview image entirely when this page is shared — a broken card gets far fewer clicks than a complete one. Add the missing og:image tag to <head>. For og:image, use an absolute https:// URL to an image around 1200x630 pixels; relative paths are the usual reason previews break. Re-check with a platform's sharing debugger afterwards, since preview cards are cached.
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.
6 passing checks
- Meta descriptionMeta description is "Voghera Country Festival Awards 2025 Prossimamente Clicca qui per votare COMUNICATO STAMPA: Cambio date Voghera Country..." (136 characters)
- Canonical URLCanonical href is "https://www.vogheracountryfestival.com/"
- Viewport meta tagViewport is "width=device-width, initial-scale=1.0"
- Character encoding declaredCharacter encoding is declared
- FaviconA <link rel="icon"> is present
- Page allows indexingNo restrictive robots meta tag
Content & Structure
20.6/25
Headings, copy depth, images, structured data, internal linking.
Image alt textmedium impactlow effort
37 of 49 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.
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.
Heading hierarchylow impactlow effort
Heading level jumps from h1 ("") to h3 ("")
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.
Hreflang annotationslow impactlow effort
2 hreflang link(s) present but no x-default entry
Your hreflang set has no x-default entry, so search engines must guess which version to show visitors whose language you don't list — and they often pick a poorly matched one. Add <link rel="alternate" hreflang="x-default" href="https://www.example.com/"> pointing at your fallback page, typically the English version or a language-selector page. Remember that hreflang must be reciprocal: every version, including the x-default target, should carry the full set of alternate links back to all the others.
5 passing checks
- Single H1 heading1 h1 found: ""
- Word count1417 words of visible text
- HTML lang attribute<html lang="it-IT">
- JavaScript-dependent contentvisible text ~4235 chars in the initial HTML
- Internal linking46 internal, 21 external links
Technical
17.6/25
HTTPS, redirects, robots, sitemap, speed, crawlability.
Fast time to first bytehigh impactmedium effort
1940 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.
No mixed contentmedium impactlow effort
1 http:// subresource reference
Some images, scripts, or styles load over insecure http:// on this HTTPS page; browsers block insecure scripts outright and flag the page, which breaks functionality and undermines the padlock users look for. Update each reference to https:// — most hosts serve the same asset on both schemes — or re-host assets whose origins don't support TLS. Adding <meta http-equiv="Content-Security-Policy" content="upgrade-insecure-requests"> is a quick safety net, but fix the underlying URLs too: hard-coded http:// links in databases and old content are the usual source.
Short redirect chainmedium impactlow effort
https://cowboys.dance/ (301) → http://www.vogheracountryfestival.com/ (301) → https://www.vogheracountryfestival.com/
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.
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.
7 passing checks
- Served over HTTPSfinal URL uses https://
- HTTP redirects to HTTPShttp:// redirects to https://
- robots.txt present and permissiverobots.txt exists and allows crawling
- Reasonable HTML size93.1 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.