SEO report for www.visittromso.no
https://www.visittromso.no/ · checked Sun, 01 Nov 2026 19:40 GMT
Fix these first
- Render-blocking resourceshigh
4 blocking script(s) and 28 stylesheet(s) in <head>.
Fix: Add defer to scripts, inline critical CSS and load the rest asynchronously.
- LocalBusiness markuphigh
No LocalBusiness structured data.
Fix: Add LocalBusiness JSON-LD with address or areaServed, telephone, geo, opening hours and url.
- H1 headingcritical
“Welcome to the Arctic”
Fix: Use one H1 that states the page topic with its main keyword.
- Scripts & third partiesmedium
41 script tag(s); files loaded from 6 other domain(s): cdn-cookieyes.com, cdn.jsdelivr.net, kit.fontawesome.com, googletagmanager.com, altek-hospitality-chatbot-agent.web.app, cdnjs.cloudflare.com.
Fix: Remove unused tracking and widget scripts; every third party adds connection time.
- HSTSmedium
No Strict-Transport-Security header.
Fix: Add Strict-Transport-Security: max-age=63072000; includeSubDomains.
- Form labelsmedium
2 of 2 form field(s) have no label.
Fix: Give every form field a <label> or aria-label (a placeholder isn't a label).
- Open Graph & social cardsmedium
Open Graph title or image missing.
Fix: Add og:title, og:description, og:image (1200×630 PNG/JPG, absolute URL) and twitter:card=summary_large_image.
- Heading structuremedium
80 headings for 1232 words – a lot for the amount of text.
Fix: Use H2s for main sections and H3s inside them, without skipping levels.
Real-world speed Google PageSpeed
Loading Core Web Vitals from Google… this can take up to 30 seconds.
Authority & backlinks
Looking up which websites link to visittromso.no…
Indexing & crawling 100%
Can search engines reach, read and index this page?
- ✓
Status codecritical
The page returned HTTP 200.
- ✓
Indexablecritical
No noindex instruction – the page can appear in search.
- ✓
robots.txthigh
robots.txt found.
Googlebot is allowed to crawl this page.
- ✓
XML sitemaphigh
Sitemap found at https://www.visittromso.no/sitemap.xml with 1,749 URLs.
Declared in robots.txt.
This page is listed in it.
Most recent lastmod: 2026-10-27T14:29:44+01:00.
- ✓
Canonical URLhigh
Canonical: https://www.visittromso.no/
Points to this page (self-referencing).
- ✓
Redirectshigh
1 redirect before the page loaded.
https://visittromso.no/ → https://www.visittromso.no/
A single redirect to your preferred address is normal; just make sure your own links use the final address.
- ✓
www / non-wwwmedium
visittromso.no redirects to www.visittromso.no.
- ✓
hreflangmedium
2 hreflang link(s).
All language codes are valid.
No x-default (recommended for a language picker or fallback page).
Search snippet & sharing 92%
How the page looks in Google results and when shared.
- ✓
Title tagcritical
“Home | Visit Tromso | Norway”
About 265px of Google's ~580px desktop width.
- ✓
Meta descriptionhigh
142 characters, ~845px of ~990px.
Good length.
Google sometimes rewrites descriptions to match the search; a good one is still used most often.
- ✓
Faviconlow
Favicon linked (Google shows it next to results).
- ✓
Languagelow
lang="en"
Content quality 73%
Is there enough clear, useful text that matches what the page targets?
- ✓
Word countmedium
1,232 words of main content (inside <main>).
Google has no minimum word count – this is a rough guide to whether the page answers the question in full.
- ✓
Readabilitymedium
Flesch reading ease 60 (plain English), about 11 words per sentence.
- ✓
Topic focushigh
3 of 4 title keywords appear in the main content (missing: tromso).
- !
H1 headingcritical
“Welcome to the Arctic”
The H1 shares no keywords with the title.
Fix: Use one H1 that states the page topic with its main keyword.
- !
Heading structuremedium
80 headings for 1232 words – a lot for the amount of text.
Levels are in order.
Fix: Use H2s for main sections and H3s inside them, without skipping levels.
- !
Text-to-code ratiolow
5% of the HTML is visible text.
Fix: Trim unused markup, inline scripts and builder bloat.
AI search readiness 81%
Can ChatGPT, Claude, Perplexity and Google AI Overviews read, understand and cite this site?
- ✓
AI crawler accesshigh
Search and AI-search crawlers (Googlebot, Bingbot, OAI-SearchBot, Claude-SearchBot, PerplexityBot…) can read this page.
- ✓
Snippet controlshigh
No snippet restrictions – search and AI answers can quote this page.
- ✗
llms.txtlow
No /llms.txt file. It's an optional, emerging convention – few AI tools are confirmed to read it yet, so this is low priority.
Fix: Optionally add /llms.txt: a short Markdown summary of who you are with links to your key pages.
- !
Question-led contentmedium
2 heading(s) phrased as questions, e.g. “Visiting by cruise?”.
Fix: Add headings that match real questions ("How much does…?") followed by a direct one- or two-sentence answer – an easy format for search and AI answers to quote.
- ✓
Entity clarityhigh
Identified as: Organization.
3 official profile link(s) (sameAs).
- ✓
Freshness signalsmedium
The page shows when it was published or last updated.
- !
Trust pages (E-E-A-T)medium
Links found to about and privacy; missing contact.
Fix: Link to About, Contact and Privacy pages from every page – they help visitors, Google and AI tools see who stands behind the content.
Structured data 100%
Machine-readable facts for rich results and AI.
- ✓
JSON-LD present & validhigh
2 JSON-LD block(s): WebPage, Organization, WebSite, ImageObject, ContactPoint.
All blocks parse correctly.
- ✓
Required propertiesmedium
Key types include Google's required properties.
Links 100%
Internal linking, anchor text and broken links.
- ✓
Internal linkinghigh
160 internal and 11 external links.
- ✓
Anchor text qualitymedium
No link text points to two different pages.
- ✓
Broken links (sample)high
Checked 12 internal link(s).
No broken links found.
Performance 46%
Speed signals from the HTML and server. Real-user Core Web Vitals load below.
- ✓
Server response (TTFB)high
262 ms until the first response from our checker, including connection setup (Google rates TTFB good under 0.8 s, poor over 1.8 s).
- !
HTML sizemedium
175 kB of HTML.
Fix: Remove inline bloat, base64 images and unused markup.
- i
Compressionmedium
Couldn't be measured from our server (our fetch decodes compressed pages before we see them). Check in your browser's developer tools that HTML is sent with br or gzip.
- ✗
Render-blocking resourceshigh
4 blocking script(s) and 28 stylesheet(s) in <head>.
Fix: Add defer to scripts, inline critical CSS and load the rest asynchronously.
- ✗
Scripts & third partiesmedium
41 script tag(s); files loaded from 6 other domain(s): cdn-cookieyes.com, cdn.jsdelivr.net, kit.fontawesome.com, googletagmanager.com, altek-hospitality-chatbot-agent.web.app, cdnjs.cloudflare.com.
Fix: Remove unused tracking and widget scripts; every third party adds connection time.
- !
Imagesmedium
81 image(s).
All images reserve their space.
8 image(s) after the first three aren't lazy-loaded.
68 use WebP/AVIF or responsive srcset.
Fix: Give every image width and height, lazy-load images below the fold (but not the main image) and serve WebP/AVIF.
- ✓
Cachinglow
Cache-Control: max-age=300, public
- i
HTTP/3low
Couldn't be confirmed from our server – the alt-svc header that advertises HTTP/3 isn't always visible to it. Your site is on Cloudflare, which offers HTTP/3 under Network settings.
Security 75%
Visitor safety signals that browsers and Google check.
- ✓
HTTPScritical
Secure HTTPS with no mixed content.
- ✓
HTTP → HTTPS redirecthigh
http:// redirects to https://.
- ✗
HSTSmedium
No Strict-Transport-Security header.
Fix: Add Strict-Transport-Security: max-age=63072000; includeSubDomains.
- ✗
Security headerslow
Present: nosniff, clickjacking protection.
Fix: Add X-Content-Type-Options, Referrer-Policy, Permissions-Policy and X-Frame-Options (or a CSP).
- ✓
Server fingerprintlow
No X-Powered-By header (server: cloudflare).
Mobile & accessibility 83%
Usable on phones and by everyone – Google indexes the mobile version.
- ✓
Mobile viewportcritical
viewport: width=device-width, initial-scale=1.0
- ✓
Image alt textmedium
All 81 images have alt text.
- ✗
Form labelsmedium
2 of 2 form field(s) have no label.
Fix: Give every form field a <label> or aria-label (a placeholder isn't a label).
- ✓
Link nameslow
Every link has a readable name.
- ✓
Tap-to-contactmedium
One-tap contact: phone.
Local SEO 33%
Signals that help you appear in Google Maps and 'near me' searches.
- ✗
LocalBusiness markuphigh
No LocalBusiness structured data.
Fix: Add LocalBusiness JSON-LD with address or areaServed, telephone, geo, opening hours and url.
- ✓
Contact details on pagemedium
A UK phone number is shown.
No postcode found (fine for service-area businesses).
- ✗
Map & directionslow
No map or directions link.
Fix: Add a Google Maps directions link so customers can find you.