Catalog / hype.it
63

SEO audit for hype.it

HYPE: conto digitale e app per pagamenti | HYPE

other

Health 63/100 (fair) · 50 pages crawled · generated 2026-08-26

Download Markdown report (feed to ChatGPT / Claude / Cursor)

Il conto tutto italiano che ti semplifica la vita. Registrati e approfitta delle promozioni attive!

50
pages crawled
45
indexable pages
2
errors
182
warnings
256
notices
0
orphan pages
1
broken links
Category breakdown
CategoryScoreErrorsWarningsNotices
Crawlability 96 1 4 0
Links 98 1 0 0
Security 71 0 48 95
Performance 72 0 47 46
Headings 80 0 33 0
Canonical 86 0 24 1
Duplicate 92 0 14 9
Content 97 0 5 43
Indexability 98 0 4 0
Sitemap 99 0 2 0
Budget 99 0 1 0
Agent Readiness 100 0 0 52
Meta Description 100 0 0 8
Titles 100 0 0 1
URL 100 0 0 1
Findings

Errors (2 rules)

error Broken internal link (target 4xx/5xx)

Rule links.broken_internal · Links · 1 occurrence(s)

error Client error (4xx) response

Rule status.4xx · Crawlability · 1 occurrence(s)

Warnings (12 rules)

warning Noindex page receives internal links (crawl-budget waste)

Rule budget.noindex_linked · Budget · 1 occurrence(s)

  • https://www.hype.it/landing-minori — this noindex page has 3 internal inlink(s) — Googlebot follows them, fetches the page, then drops it unindexed, spending crawl budget for no indexing benefit (and the links leak equity). Remove/redirect the links, or drop the noindex if the page should be indexed. Linked from: https://www.hype.it/privati/confronta-conti, https://www.hype.it/landing-upgrade, https://www.hype.it/landing-upgrade-plus.

warning Missing canonical tag

Rule canonical.missing · Canonical · 24 occurrence(s)

warning Thin content (low word count)

Rule content.thin · Content · 5 occurrence(s)

warning Duplicate page content

Rule duplicate.content · Duplicate · 5 occurrence(s)

warning Duplicate <title> across pages

Rule duplicate.title · Duplicate · 9 occurrence(s)

warning Missing <h1>

Rule h1.missing · Headings · 33 occurrence(s)

warning Content-Type header doesn't match the actual content

Rule headers.content_type_mismatch · Security · 48 occurrence(s)

  • https://www.hype.it/ — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://www.hype.it/about — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://www.hype.it/apple-pay — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://www.hype.it/blog/apple-wallet — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://www.hype.it/business — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://www.hype.it/business/conto-iban — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://www.hype.it/buyon-terms — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://www.hype.it/click-to-pay — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://www.hype.it/google-pay — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://www.hype.it/i-nostri-valori — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://www.hype.it/la-nostra-storia — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://www.hype.it/landing-upgrade — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://www.hype.it/landing-upgrade-plus — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://www.hype.it/media-press — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://www.hype.it/not-found — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://www.hype.it/prevenzione-frodi — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://www.hype.it/privacy — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://www.hype.it/privacy-policy — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://www.hype.it/privacy-policy-web — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://www.hype.it/privati/confronta-conti — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://www.hype.it/promotions/archive — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://www.hype.it/psd2 — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://www.hype.it/reclami — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://www.hype.it/send — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://www.hype.it/trasparenza — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".

warning Hero/LCP image is lazy-loaded (loading=lazy delays LCP)

Rule images.no_lazy_lcp_candidate · Performance · 47 occurrence(s)

  • https://www.hype.it/ — the likely hero/LCP image (1773674622-logo-hype-positive.svg) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • https://www.hype.it/about — the likely hero/LCP image (1773674622-logo-hype-positive.svg) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • https://www.hype.it/apple-pay — the likely hero/LCP image (1773674622-logo-hype-positive.svg) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • https://www.hype.it/blog — the likely hero/LCP image (1773674622-logo-hype-positive.svg) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • https://www.hype.it/blog/apple-wallet — the likely hero/LCP image (1773674622-logo-hype-positive.svg) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • https://www.hype.it/business — the likely hero/LCP image (1773674630-logo-hype-negative.svg) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • https://www.hype.it/business/conto-iban — the likely hero/LCP image (1773674630-logo-hype-negative.svg) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • https://www.hype.it/click-to-pay — the likely hero/LCP image (1773674622-logo-hype-positive.svg) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • https://www.hype.it/google-pay — the likely hero/LCP image (1773674622-logo-hype-positive.svg) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • https://www.hype.it/i-nostri-valori — the likely hero/LCP image (1773674622-logo-hype-positive.svg) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • https://www.hype.it/la-nostra-storia — the likely hero/LCP image (1773674622-logo-hype-positive.svg) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • https://www.hype.it/landing-upgrade — the likely hero/LCP image (1773674622-logo-hype-positive.svg) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • https://www.hype.it/landing-upgrade-plus — the likely hero/LCP image (1773674622-logo-hype-positive.svg) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • https://www.hype.it/media-press — the likely hero/LCP image (1773674622-logo-hype-positive.svg) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • https://www.hype.it/not-found — the likely hero/LCP image (1773674622-logo-hype-positive.svg) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • https://www.hype.it/prevenzione-frodi — the likely hero/LCP image (1773674622-logo-hype-positive.svg) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • https://www.hype.it/privacy — the likely hero/LCP image (1773674622-logo-hype-positive.svg) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • https://www.hype.it/privacy-policy — the likely hero/LCP image (1773674622-logo-hype-positive.svg) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • https://www.hype.it/privacy-policy-web — the likely hero/LCP image (1773674622-logo-hype-positive.svg) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • https://www.hype.it/privati/confronta-conti — the likely hero/LCP image (1773674622-logo-hype-positive.svg) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • https://www.hype.it/promotions/archive — the likely hero/LCP image (1773674622-logo-hype-positive.svg) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • https://www.hype.it/psd2 — the likely hero/LCP image (1773674622-logo-hype-positive.svg) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • https://www.hype.it/reclami — the likely hero/LCP image (1773674622-logo-hype-positive.svg) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • https://www.hype.it/send — the likely hero/LCP image (1773674622-logo-hype-positive.svg) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.
  • https://www.hype.it/trasparenza — the likely hero/LCP image (1773674622-logo-hype-positive.svg) has loading="lazy" — Google explicitly warns against lazy-loading the LCP image, because it delays the fetch until layout completes. Remove loading="lazy" from the first significant image and add fetchpriority="high" instead.

warning Page is noindex

Rule index.noindex · Indexability · 4 occurrence(s)

warning Redirect chain (multiple hops)

Rule redirect.chain · Crawlability · 3 occurrence(s)

warning Non-indexable URL listed in sitemap

Rule sitemap.non_indexable · Sitemap · 2 occurrence(s)

warning Soft 404 (200 OK but content signals not found)

Rule status.soft_404 · Crawlability · 1 occurrence(s)

  • https://www.hype.it/not-found — HTTP 200 but only 195 words and a not-found marker ("404") in the title/H1 — return a real 404/410 or add content

Notices (11 rules)

notice Invalid ARIA role

Rule agent.aria_invalid_role · Agent Readiness · 47 occurrence(s)

notice Heading levels skip a level

Rule agent.heading_skip · Agent Readiness · 5 occurrence(s)

notice Canonical points to a different URL

Rule canonical.non_self · Canonical · 1 occurrence(s)

notice Low text-to-HTML ratio

Rule content.low_ratio · Content · 43 occurrence(s)

notice Duplicate meta description across pages

Rule duplicate.meta_desc · Duplicate · 9 occurrence(s)

notice Meta description too short

Rule meta_desc.too_short · Meta Description · 8 occurrence(s)

notice Legacy image format (jpg/png/gif) with no next-gen fallback

Rule perf.images_legacy_format · Performance · 46 occurrence(s)

  • https://www.hype.it/ — 6 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://www.hype.it/about — 6 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://www.hype.it/apple-pay — 8 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://www.hype.it/blog — 5 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://www.hype.it/blog/apple-wallet — 5 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://www.hype.it/business — 8 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://www.hype.it/business/conto-iban — 9 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://www.hype.it/click-to-pay — 5 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://www.hype.it/google-pay — 5 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://www.hype.it/i-nostri-valori — 6 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://www.hype.it/la-nostra-storia — 5 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://www.hype.it/landing-upgrade — 5 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://www.hype.it/landing-upgrade-plus — 5 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://www.hype.it/media-press — 5 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://www.hype.it/not-found — 5 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://www.hype.it/prevenzione-frodi — 16 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://www.hype.it/privacy — 5 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://www.hype.it/privacy-policy — 5 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://www.hype.it/privacy-policy-web — 5 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://www.hype.it/privati/confronta-conti — 8 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://www.hype.it/promotions/archive — 5 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://www.hype.it/psd2 — 5 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://www.hype.it/reclami — 5 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://www.hype.it/send — 5 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://www.hype.it/trasparenza — 5 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.

notice Missing recommended security headers

Rule security.missing_headers · Security · 49 occurrence(s)

notice target=_blank link without rel=noopener (tab-napping)

Rule security.unsafe_cross_origin_links · Security · 46 occurrence(s)

  • https://www.hype.it/ — 9 external link(s) use target="_blank" without rel="noopener" — the opened page can hijack your tab (reverse tab-napping). Add rel="noopener noreferrer".
  • https://www.hype.it/about — 8 external link(s) use target="_blank" without rel="noopener" — the opened page can hijack your tab (reverse tab-napping). Add rel="noopener noreferrer".
  • https://www.hype.it/apple-pay — 8 external link(s) use target="_blank" without rel="noopener" — the opened page can hijack your tab (reverse tab-napping). Add rel="noopener noreferrer".
  • https://www.hype.it/blog — 8 external link(s) use target="_blank" without rel="noopener" — the opened page can hijack your tab (reverse tab-napping). Add rel="noopener noreferrer".
  • https://www.hype.it/blog/apple-wallet — 8 external link(s) use target="_blank" without rel="noopener" — the opened page can hijack your tab (reverse tab-napping). Add rel="noopener noreferrer".
  • https://www.hype.it/business — 10 external link(s) use target="_blank" without rel="noopener" — the opened page can hijack your tab (reverse tab-napping). Add rel="noopener noreferrer".
  • https://www.hype.it/business/conto-iban — 10 external link(s) use target="_blank" without rel="noopener" — the opened page can hijack your tab (reverse tab-napping). Add rel="noopener noreferrer".
  • https://www.hype.it/click-to-pay — 8 external link(s) use target="_blank" without rel="noopener" — the opened page can hijack your tab (reverse tab-napping). Add rel="noopener noreferrer".
  • https://www.hype.it/google-pay — 8 external link(s) use target="_blank" without rel="noopener" — the opened page can hijack your tab (reverse tab-napping). Add rel="noopener noreferrer".
  • https://www.hype.it/i-nostri-valori — 8 external link(s) use target="_blank" without rel="noopener" — the opened page can hijack your tab (reverse tab-napping). Add rel="noopener noreferrer".
  • https://www.hype.it/la-nostra-storia — 8 external link(s) use target="_blank" without rel="noopener" — the opened page can hijack your tab (reverse tab-napping). Add rel="noopener noreferrer".
  • https://www.hype.it/landing-upgrade — 4 external link(s) use target="_blank" without rel="noopener" — the opened page can hijack your tab (reverse tab-napping). Add rel="noopener noreferrer".
  • https://www.hype.it/landing-upgrade-plus — 4 external link(s) use target="_blank" without rel="noopener" — the opened page can hijack your tab (reverse tab-napping). Add rel="noopener noreferrer".
  • https://www.hype.it/media-press — 9 external link(s) use target="_blank" without rel="noopener" — the opened page can hijack your tab (reverse tab-napping). Add rel="noopener noreferrer".
  • https://www.hype.it/not-found — 8 external link(s) use target="_blank" without rel="noopener" — the opened page can hijack your tab (reverse tab-napping). Add rel="noopener noreferrer".
  • https://www.hype.it/prevenzione-frodi — 19 external link(s) use target="_blank" without rel="noopener" — the opened page can hijack your tab (reverse tab-napping). Add rel="noopener noreferrer".
  • https://www.hype.it/privacy — 33 external link(s) use target="_blank" without rel="noopener" — the opened page can hijack your tab (reverse tab-napping). Add rel="noopener noreferrer".
  • https://www.hype.it/privacy-policy — 8 external link(s) use target="_blank" without rel="noopener" — the opened page can hijack your tab (reverse tab-napping). Add rel="noopener noreferrer".
  • https://www.hype.it/privacy-policy-web — 8 external link(s) use target="_blank" without rel="noopener" — the opened page can hijack your tab (reverse tab-napping). Add rel="noopener noreferrer".
  • https://www.hype.it/privati/confronta-conti — 9 external link(s) use target="_blank" without rel="noopener" — the opened page can hijack your tab (reverse tab-napping). Add rel="noopener noreferrer".
  • https://www.hype.it/promotions/archive — 8 external link(s) use target="_blank" without rel="noopener" — the opened page can hijack your tab (reverse tab-napping). Add rel="noopener noreferrer".
  • https://www.hype.it/psd2 — 13 external link(s) use target="_blank" without rel="noopener" — the opened page can hijack your tab (reverse tab-napping). Add rel="noopener noreferrer".
  • https://www.hype.it/reclami — 12 external link(s) use target="_blank" without rel="noopener" — the opened page can hijack your tab (reverse tab-napping). Add rel="noopener noreferrer".
  • https://www.hype.it/send — 9 external link(s) use target="_blank" without rel="noopener" — the opened page can hijack your tab (reverse tab-napping). Add rel="noopener noreferrer".
  • https://www.hype.it/trasparenza — 18 external link(s) use target="_blank" without rel="noopener" — the opened page can hijack your tab (reverse tab-napping). Add rel="noopener noreferrer".

notice Title is very short

Rule title.too_short · Titles · 1 occurrence(s)

notice Uppercase letters in URL path

Rule url.uppercase · URL · 1 occurrence(s)

Pages (showing 50 of 50)
URLStatusIndexableWordsIn-links
https://www.hype.it/privacy
Cookie Policy e gestione cookie del sito | HYPE		 200 yes 1809 46
https://www.hype.it/promozioni
Promozioni HYPE: bonus e offerte attive | HYPE		 200 yes 177 46
https://www.hype.it/trasparenza
Trasparenza | HYPE		 200 yes 535 46
https://www.hype.it/
HYPE: conto digitale e app per pagamenti | HYPE		 200 yes 724 43
https://www.hype.it/blog
Blog HYPE: guide su pagamenti, risparmio e finanza personale		 200 yes 190 43
https://www.hype.it/business
Conto aziendale online | HYPE		 200 yes 534 43
https://www.hype.it/about
A proposito di noi | HYPE		 200 yes 535 42
https://www.hype.it/apple-pay
HYPE con Apple Pay: effettua pagamenti contactless | HYPE		 200 yes 481 42
https://www.hype.it/click-to-pay
HYPE con Click to Pay | HYPE		 200 yes 473 42
https://www.hype.it/google-pay
Google Pay | HYPE		 200 yes 452 42
https://www.hype.it/la-nostra-storia
Una storia italiana | HYPE		 200 yes 502 42
https://www.hype.it/media-press
Media & Press | HYPE		 200 yes 292 42
https://www.hype.it/prevenzione-frodi
Conosci le truffe più diffuse? | HYPE		 200 yes 911 42
https://www.hype.it/privacy-policy-web
Privacy Policy | HYPE		 200 yes 1874 42
https://www.hype.it/psd2
PSD2 Gateway | HYPE		 200 yes 236 42
https://www.hype.it/reclami
Reclami, ricorsi e mediazione | HYPE		 200 yes 545 42
https://www.hype.it/send
SEND | HYPE		 200 yes 504 42
https://www.hype.it/privati/confronta-conti
Costi e Condizioni | HYPE | HYPE		 200 yes 1168 41
https://www.hype.it/privati/conto-hype
Conto online a zero spese | HYPE		 200 yes 646 21
https://www.hype.it/privati/hype-next
HYPE Next: conto con carta fisica Mastercard | HYPE		 200 yes 784 21
https://www.hype.it/privati/hype-premium
HYPE Premium: prelievi gratis, bonifici istantanei | HYPE		 200 yes 817 21
https://www.hype.it/landing-minori
Conto e carta prepagata, con IBAN per minorenni da 12 anni		 200 no 688 3
https://www.hype.it/privati/splithype
SplitHYPE | HYPE		 200 yes 418 4
https://www.hype.it/privati/pagamenti
Pagamenti | HYPE		 200 yes 667 4
https://www.hype.it/privati/box-risparmi
Risparmi | HYPE		 200 yes 540 3
https://www.hype.it/promotions/archive
Archivio Promozioni | HYPE | HYPE		 200 yes 179 1
https://www.hype.it/business/conto-iban
Conto aziendale online | HYPE		 200 yes 548 1
https://www.hype.it/privati/carte
Carte virtuali e fisiche per pagare ovunque | HYPE | HYPE		 200 yes 577 2
https://www.hype.it/privati/cashback
App per cashback e rimborsi online | HYPE		 200 yes 502 3
https://www.hype.it/privati/gestione-spese
App di gestione spese e aggregazione conti | HYPE		 200 yes 495 3
https://www.hype.it/privati/scambia-denaro
App per scambiare denaro e dividere le spese | HYPE		 200 yes 562 2
https://www.hype.it/privati/conto-iban
Conto con IBAN: Bonifici, pagamenti e accredito stipendio		 200 yes 522 1
https://www.hype.it/privati/prestiti-personali
Prestiti personali | HYPE		 200 yes 645 1
https://www.hype.it/accessibility
HYPE Home Page | HYPE		 200 yes 502 0
https://www.hype.it/blog/apple-wallet
Apple Wallet: cos'è e come funziona | HYPE		 200 yes 1341 0
https://www.hype.it/blogs/newsroom
Blog Newroom | HYPE		 200 yes 71 0
https://www.hype.it/buyon-terms
Buyon - Termini e condizioni | HYPE		 200 yes 3513 0
https://www.hype.it/i-nostri-valori
A proposito di noi | HYPE		 200 yes 535 0
https://www.hype.it/il-nostro-team
A proposito di noi | HYPE		 200 yes 535 0
https://www.hype.it/landing-business-prospect-staging
Landing Business Prospect | HYPE		 200 yes 725 0
https://www.hype.it/landing-upgrade
Upgrade a HYPE Next o Premium e ottieni fino a 25€ di bonus		 200 no 770 0
https://www.hype.it/landing-upgrade-plus
Passa a HYPE Plus e ottieni più vantaggi | HYPE		 200 no 770 0
https://www.hype.it/not-found
404 Pagina non trovata | HYPE		 200 yes 195 0
https://www.hype.it/privacy-policy
Cookie Policy e gestione cookie del sito | HYPE		 200 yes 5222 0
https://www.hype.it/privati/comparatore-facile
Comparatore Facile.it | HYPE		 200 yes 715 0
https://www.hype.it/privati/credit-boost
Prestito istantaneo online con accredito immediato | HYPE		 200 yes 673 0
https://www.hype.it/privati/cryptocurrency
Acquista e gestisci Bitcoin | HYPE		 200 yes 662 0
https://www.hype.it/scambia-denaro
App per scambiare denaro e dividere le spese | HYPE		 200 yes 562 0
https://www.hype.it/SSRDocumentDisplayer?dtdPG=PRIVACY_LONG_HYP&dtdPE=1 200 no 0 46
https://www.hype.it/www.giustizia.it/giustizia.
404 Pagina non trovata | HYPE		 404 no 195 1

Audit your own site — free

157 checks, internal PageRank, render-diff. No signup, results in ~30s.

Scan your site →