fiestasorpresa.es
Hello world! - fiestasorpresa.es
0 failed · 4 warnings · 25 passed
Audited Sun, 19 Jul 2026 17:00:28 GMT · https://fiestasorpresa.es/
Meta & Head
22.9/25
Title, description, canonical, social tags — what search engines read first.
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.
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.
7 passing checks
- Title tag<title> is "Hello world! - fiestasorpresa.es" (32 characters)
- Meta descriptionMeta description is "Welcome to WordPress. This is your first post. Edit or delete it, then start writing!" (85 characters)
- Canonical URLCanonical href is "https://fiestasorpresa.es/"
- Viewport meta tagViewport is "width=device-width, initial-scale=1.0"
- Character encoding declaredCharacter encoding is declared
- Twitter card tagtwitter:card is "summary_large_image"
- Page allows indexingrobots: max-image-preview:large
Content & Structure
24.2/25
Headings, copy depth, images, structured data, internal linking.
Heading hierarchylow impactlow effort
Heading level jumps from h2 ("Las mamás hablan 💬") to h4 ("Productos")
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.
7 passing checks
- Single H1 heading1 h1 found: "¡La piñata más épica te espera!"
- Word count1135 words of visible text
- Image alt text5 of 5 images have alt text
- Structured data (JSON-LD)JSON-LD types found: BreadcrumbList, CollectionPage, Organization, WebSite
- HTML lang attribute<html lang="es">
- JavaScript-dependent contentvisible text ~6885 chars in the initial HTML
- Internal linking39 internal, 2 external links
Technical
24.4/25
HTTPS, redirects, robots, sitemap, speed, crawlability.
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.
11 passing checks
- Served over HTTPSfinal URL uses https://
- HTTP redirects to HTTPShttp:// redirects to https://
- No mixed content0 http:// subresource references
- Short redirect chainno redirects; URL resolves directly
- robots.txt present and permissiverobots.txt exists and allows crawling
- XML sitemap availablesitemap.xml exists and is valid XML
- Fast time to first byte435 ms
- Reasonable HTML size55.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.