Speed
Does the page show up quickly and react straight away?
97/100
Hotel Trinserhof
trinserhof.at
At a glance
Website 3 scored 36 for speed on a phone; website 4 scores 97 now. The main content appears after 2.0 s instead of 18 s, and the home page downloads 353 KB instead of 7.2 MB.
Findability
Can search engines read and list the page properly?
100/100
Accessibility
Can everyone use it, including people with a disability?
100/100
Trust & safety
Is it built safely and without errors?
100/100
AI assistants
Can AI assistants such as ChatGPT, Gemini or Copilot read and use the website?
50/100
What we changed, and what it did
Every change is logged with the measurements taken just before and just after it, so you can see whether it made a difference.
23 Oct 2026
Right-sized photos on website 4
Home page photos now come in three sizes, so phones no longer download photos meant for large screens.
24 Oct 2026
Back to website 4
The main address showed website 3 (Squarespace) for one day, 23 October, to measure it for the first reports. It then switched back to website 4.
24 Oct 2026
Accessibility fixes
The menu, prices and booking pages of website 4 were brought to 100 in Google's accessibility check.
1 Nov 2026
Error tracking service removed
The last outside company the website contacted (Sentry) was removed.
Measured before (1 Sept, Website 4) and after (4 Nov, Website 4)
| Measure | Before | After | Change |
|---|---|---|---|
| Speed | 90 | 97 | +7, an improvement |
| Findability | 100 | 100 | ±0, unchanged |
| Accessibility | 100 | 100 | ±0, unchanged |
| Trust & safety | 100 | 100 | ±0, unchanged |
| Main content appears | 3.0 s | 2.0 s | −1.0 s, an improvement |
| Data to download | 750 KB | 353 KB | −397 KB, an improvement |
Scores over time
Google Lighthouse scores each area from 0 to 100. 90 or more is good, 50 to 89 needs work. Numbered lines mark the changes listed above. The gray squares in the shaded strip on the left are website 1 and website 2, which were never measured and are set to 0.
Speed
Lighthouse Performance
Visitors leave slow pages, and Google ranks fast pages higher. The score combines how quickly the main content appears, how still the page stays while loading and how quickly it reacts to taps.
1·2·3·4
- trinserhof.at
- Not measured, set to 0
Show as table
| Measured | trinserhof.at |
|---|---|
| 4 Nov 2026, 09:04 | 97 |
| 1 Sept 2026, 02:00 | 90 |
| 31 Aug 2026, 02:00 | 37 |
| 1 Jan 2014, 01:00 | 36 |
| 1 Sept 2005 | 0, not measured |
| 1 May 2001 | 0, not measured |
Findability
Lighthouse SEO
The basics Google needs to list a page: a title and description, a page it is allowed to read, working links, image descriptions and the language versions it should show.
1·2·3·4
- trinserhof.at
- Not measured, set to 0
Show as table
| Measured | trinserhof.at |
|---|---|
| 4 Nov 2026, 09:04 | 100 |
| 1 Sept 2026, 02:00 | 100 |
| 31 Aug 2026, 02:00 | 100 |
| 1 Jan 2014, 01:00 | 100 |
| 1 Sept 2005 | 0, not measured |
| 1 May 2001 | 0, not measured |
Accessibility
Lighthouse Accessibility
Readable contrast, descriptions for photos, buttons with names and a page structure that screen readers understand. Since June 2025 the European Accessibility Act makes this a legal requirement for websites that sell online.
1·2·3·4
- trinserhof.at
- Not measured, set to 0
Show as table
| Measured | trinserhof.at |
|---|---|
| 4 Nov 2026, 09:04 | 100 |
| 1 Sept 2026, 02:00 | 100 |
| 31 Aug 2026, 02:00 | 96 |
| 1 Jan 2014, 01:00 | 96 |
| 1 Sept 2005 | 0, not measured |
| 1 May 2001 | 0, not measured |
Trust & safety
Lighthouse Best Practices
A secure connection, no errors in the background, no outdated code, correctly sized images and no surprise requests such as asking for a location on arrival.
1·2·3·4
- trinserhof.at
- Not measured, set to 0
Show as table
| Measured | trinserhof.at |
|---|---|
| 4 Nov 2026, 09:04 | 100 |
| 1 Sept 2026, 02:00 | 100 |
| 31 Aug 2026, 02:00 | 57 |
| 1 Jan 2014, 01:00 | 57 |
| 1 Sept 2005 | 0, not measured |
| 1 May 2001 | 0, not measured |
How fast it feels
The home page on a mid-range phone on a slow mobile connection. The shaded area is what Google considers good.
Main content appears
Largest Contentful Paint (LCP) · Core Web Vital
2.0 s
When the biggest photo or text block is visible. Google counts up to 2.5 seconds as good.
Was 18 s on 1 Jan
1·2·3·4
Show as table
| Measured | trinserhof.at |
|---|---|
| 4 Nov 2026, 09:04 | 2.0 s |
| 1 Sept 2026, 02:00 | 3.0 s |
| 31 Aug 2026, 02:00 | 17 s |
| 1 Jan 2014, 01:00 | 18 s |
Page ignores taps
Total Blocking Time (TBT) · lab stand-in for INP
157 ms
How long the page is too busy to react while it loads. Up to 200 milliseconds feels instant.
Was 1.2 s on 1 Jan
1·2·3·4
Show as table
| Measured | trinserhof.at |
|---|---|
| 4 Nov 2026, 09:04 | 157 ms |
| 1 Sept 2026, 02:00 | 194 ms |
| 31 Aug 2026, 02:00 | 1.2 s |
| 1 Jan 2014, 01:00 | 1.2 s |
Page jumps while loading
Cumulative Layout Shift (CLS) · Core Web Vital
0.00
How much text and buttons move around as the page loads, which leads to mis-taps. Below 0.1 is good.
Was 0.00 on 1 Jan
1·2·3·4
Show as table
| Measured | trinserhof.at |
|---|---|
| 4 Nov 2026, 09:04 | 0.00 |
| 1 Sept 2026, 02:00 | 0.00 |
| 31 Aug 2026, 02:00 | 0.00 |
| 1 Jan 2014, 01:00 | 0.00 |
First thing appears
First Contentful Paint (FCP)
887 ms
When the visitor first sees anything other than a blank screen. Up to 1.8 seconds is good.
Was 3.9 s on 1 Jan
1·2·3·4
Show as table
| Measured | trinserhof.at |
|---|---|
| 4 Nov 2026, 09:04 | 887 ms |
| 1 Sept 2026, 02:00 | 1.9 s |
| 31 Aug 2026, 02:00 | 3.7 s |
| 1 Jan 2014, 01:00 | 3.9 s |
Page looks complete
Speed Index
887 ms
How quickly the visible part of the page fills in. Up to 3.4 seconds is good.
Was 9.3 s on 1 Jan
1·2·3·4
Show as table
| Measured | trinserhof.at |
|---|---|
| 4 Nov 2026, 09:04 | 887 ms |
| 1 Sept 2026, 02:00 | 2.1 s |
| 31 Aug 2026, 02:00 | 8.5 s |
| 1 Jan 2014, 01:00 | 9.3 s |
Server answers
Time to First Byte (TTFB)
33 ms
How quickly the web server starts sending the page. Up to 0.8 seconds is good.
Was 52 ms on 1 Jan
1·2·3·4
Show as table
| Measured | trinserhof.at |
|---|---|
| 4 Nov 2026, 09:04 | 33 ms |
| 1 Sept 2026, 02:00 | 42 ms |
| 31 Aug 2026, 02:00 | 50 ms |
| 1 Jan 2014, 01:00 | 52 ms |
Page weight and footprint
Data to download for the home page
Total transfer size
Heavy pages are slow on mobile data and cost visitors part of their data plan. Photos are usually the biggest part.
1·2·3·4
Show as table
| Measured | trinserhof.at |
|---|---|
| 4 Nov 2026, 09:04 | 353 KB |
| 1 Sept 2026, 02:00 | 750 KB |
| 31 Aug 2026, 02:00 | 7.2 MB |
| 1 Jan 2014, 01:00 | 7.2 MB |
Files fetched
Each photo, font and piece of code is a separate request. Fewer requests load faster.
38was 97, an improvement on 1 JanCO₂ per 1,000 visits
An estimate of the electricity used to send the home page, from the Sustainable Web Design model (version 3).
126 gwas 2.6 kg, an improvement on 1 Jan
At a glance
Website 3 scored 61 for speed on a computer; website 4 scores 100 now. The main content appears after 531 ms instead of 4.5 s, and the home page downloads 586 KB instead of 7.3 MB.
Speed
Does the page show up quickly and react straight away?
100/100
Findability
Can search engines read and list the page properly?
100/100
Accessibility
Can everyone use it, including people with a disability?
100/100
Trust & safety
Is it built safely and without errors?
100/100
AI assistants
Can AI assistants such as ChatGPT, Gemini or Copilot read and use the website?
50/100
What we changed, and what it did
Every change is logged with the measurements taken just before and just after it, so you can see whether it made a difference.
23 Oct 2026
Right-sized photos on website 4
Home page photos now come in three sizes, so phones no longer download photos meant for large screens.
24 Oct 2026
Back to website 4
The main address showed website 3 (Squarespace) for one day, 23 October, to measure it for the first reports. It then switched back to website 4.
24 Oct 2026
Accessibility fixes
The menu, prices and booking pages of website 4 were brought to 100 in Google's accessibility check.
1 Nov 2026
Error tracking service removed
The last outside company the website contacted (Sentry) was removed.
Measured before (1 Sept, Website 4) and after (4 Nov, Website 4)
| Measure | Before | After | Change |
|---|---|---|---|
| Speed | 94 | 100 | +6, an improvement |
| Findability | 100 | 100 | ±0, unchanged |
| Accessibility | 86 | 100 | +14, an improvement |
| Trust & safety | 100 | 100 | ±0, unchanged |
| Main content appears | 1.3 s | 531 ms | −769 ms, an improvement |
| Data to download | 1.5 MB | 586 KB | −894 KB, an improvement |
Scores over time
Google Lighthouse scores each area from 0 to 100. 90 or more is good, 50 to 89 needs work. Numbered lines mark the changes listed above. The gray squares in the shaded strip on the left are website 1 and website 2, which were never measured and are set to 0.
Speed
Lighthouse Performance
Visitors leave slow pages, and Google ranks fast pages higher. The score combines how quickly the main content appears, how still the page stays while loading and how quickly it reacts to taps.
1·2·3·4
- trinserhof.at
- Not measured, set to 0
Show as table
| Measured | trinserhof.at |
|---|---|
| 4 Nov 2026, 09:04 | 100 |
| 1 Sept 2026, 02:00 | 94 |
| 31 Aug 2026, 02:00 | 61 |
| 1 Jan 2014, 01:00 | 61 |
| 1 Sept 2005 | 0, not measured |
| 1 May 2001 | 0, not measured |
Findability
Lighthouse SEO
The basics Google needs to list a page: a title and description, a page it is allowed to read, working links, image descriptions and the language versions it should show.
1·2·3·4
- trinserhof.at
- Not measured, set to 0
Show as table
| Measured | trinserhof.at |
|---|---|
| 4 Nov 2026, 09:04 | 100 |
| 1 Sept 2026, 02:00 | 100 |
| 31 Aug 2026, 02:00 | 100 |
| 1 Jan 2014, 01:00 | 100 |
| 1 Sept 2005 | 0, not measured |
| 1 May 2001 | 0, not measured |
Accessibility
Lighthouse Accessibility
Readable contrast, descriptions for photos, buttons with names and a page structure that screen readers understand. Since June 2025 the European Accessibility Act makes this a legal requirement for websites that sell online.
1·2·3·4
- trinserhof.at
- Not measured, set to 0
Show as table
| Measured | trinserhof.at |
|---|---|
| 4 Nov 2026, 09:04 | 100 |
| 1 Sept 2026, 02:00 | 86 |
| 31 Aug 2026, 02:00 | 91 |
| 1 Jan 2014, 01:00 | 91 |
| 1 Sept 2005 | 0, not measured |
| 1 May 2001 | 0, not measured |
Trust & safety
Lighthouse Best Practices
A secure connection, no errors in the background, no outdated code, correctly sized images and no surprise requests such as asking for a location on arrival.
1·2·3·4
- trinserhof.at
- Not measured, set to 0
Show as table
| Measured | trinserhof.at |
|---|---|
| 4 Nov 2026, 09:04 | 100 |
| 1 Sept 2026, 02:00 | 100 |
| 31 Aug 2026, 02:00 | 56 |
| 1 Jan 2014, 01:00 | 56 |
| 1 Sept 2005 | 0, not measured |
| 1 May 2001 | 0, not measured |
How fast it feels
The home page on a computer on a fast connection. The shaded area is what Google considers good.
Main content appears
Largest Contentful Paint (LCP) · Core Web Vital
531 ms
When the biggest photo or text block is visible. Google counts up to 2.5 seconds as good.
Was 4.5 s on 1 Jan
1·2·3·4
Show as table
| Measured | trinserhof.at |
|---|---|
| 4 Nov 2026, 09:04 | 531 ms |
| 1 Sept 2026, 02:00 | 1.3 s |
| 31 Aug 2026, 02:00 | 4.9 s |
| 1 Jan 2014, 01:00 | 4.5 s |
Page ignores taps
Total Blocking Time (TBT) · lab stand-in for INP
0 ms
How long the page is too busy to react while it loads. Up to 200 milliseconds feels instant.
Was 172 ms on 1 Jan
1·2·3·4
Show as table
| Measured | trinserhof.at |
|---|---|
| 4 Nov 2026, 09:04 | 0 ms |
| 1 Sept 2026, 02:00 | 0 ms |
| 31 Aug 2026, 02:00 | 149 ms |
| 1 Jan 2014, 01:00 | 172 ms |
Page jumps while loading
Cumulative Layout Shift (CLS) · Core Web Vital
0.00
How much text and buttons move around as the page loads, which leads to mis-taps. Below 0.1 is good.
Was 0.00 on 1 Jan
1·2·3·4
Show as table
| Measured | trinserhof.at |
|---|---|
| 4 Nov 2026, 09:04 | 0.00 |
| 1 Sept 2026, 02:00 | 0.00 |
| 31 Aug 2026, 02:00 | 0.00 |
| 1 Jan 2014, 01:00 | 0.00 |
First thing appears
First Contentful Paint (FCP)
276 ms
When the visitor first sees anything other than a blank screen. Up to 1.8 seconds is good.
Was 1.4 s on 1 Jan
1·2·3·4
Show as table
| Measured | trinserhof.at |
|---|---|
| 4 Nov 2026, 09:04 | 276 ms |
| 1 Sept 2026, 02:00 | 1.1 s |
| 31 Aug 2026, 02:00 | 1.9 s |
| 1 Jan 2014, 01:00 | 1.4 s |
Page looks complete
Speed Index
308 ms
How quickly the visible part of the page fills in. Up to 3.4 seconds is good.
Was 2.8 s on 1 Jan
1·2·3·4
Show as table
| Measured | trinserhof.at |
|---|---|
| 4 Nov 2026, 09:04 | 308 ms |
| 1 Sept 2026, 02:00 | 1.1 s |
| 31 Aug 2026, 02:00 | 2.9 s |
| 1 Jan 2014, 01:00 | 2.8 s |
Server answers
Time to First Byte (TTFB)
32 ms
How quickly the web server starts sending the page. Up to 0.8 seconds is good.
Was 57 ms on 1 Jan
1·2·3·4
Show as table
| Measured | trinserhof.at |
|---|---|
| 4 Nov 2026, 09:04 | 32 ms |
| 1 Sept 2026, 02:00 | 49 ms |
| 31 Aug 2026, 02:00 | 49 ms |
| 1 Jan 2014, 01:00 | 57 ms |
Page weight and footprint
Data to download for the home page
Total transfer size
Heavy pages are slow on mobile data and cost visitors part of their data plan. Photos are usually the biggest part.
1·2·3·4
Show as table
| Measured | trinserhof.at |
|---|---|
| 4 Nov 2026, 09:04 | 586 KB |
| 1 Sept 2026, 02:00 | 1.5 MB |
| 31 Aug 2026, 02:00 | 7.3 MB |
| 1 Jan 2014, 01:00 | 7.3 MB |
Files fetched
Each photo, font and piece of code is a separate request. Fewer requests load faster.
43was 101, an improvement on 1 JanCO₂ per 1,000 visits
An estimate of the electricity used to send the home page, from the Sustainable Web Design model (version 3).
210 gwas 2.6 kg, an improvement on 1 Jan
The website through the years
trinserhof.at has had 4 versions. Only website 3 and website 4 could be measured; the versions before them are set to 0.
Overall score through the years
Speed, findability, accessibility, trust & safety and privacy in one number
One number from 0 to 100 that combines everything measured, on a phone and on a computer. How it is calculated
1·2·3·4
- trinserhof.at
- Not measured, set to 0
Show as table
| Measured | trinserhof.at |
|---|---|
| 4 Nov 2026, 09:04 | 100 |
| 1 Sept 2026, 02:00 | 96 |
| 31 Aug 2026, 02:00 | 66 |
| 1 Jan 2014, 01:00 | 66 |
| 1 Sept 2005 | 0, not measured |
| 1 May 2001 | 0, not measured |
Website 1
Overall score0/100Not measured, set to 0Since at least 1 May 2001 until 1 Sept 2005 · at least 4 years
The first website of the hotel, with a yellow background. It was online on 1 May 2001 at the latest.
- Made with
- Unknown
- Look
- Yellow background
- Measured
- Never, it predates this report
Website 2
Overall score0/100Not measured, set to 0From 1 Sept 2005 until 1 Jan 2014 · 8 years
Online from 1 September 2005. Possibly the same website as before, redesigned in gray.
- Made with
- Unknown
- Look
- Gray look
- Measured
- Never, it predates this report
Website 3
Overall score66/100Measured 31 Aug 2026From 1 Jan 2014 until 1 Sept 2026 · 13 years
A Squarespace website made by Jess, online from 1 January 2014 until website 4 replaced it on the live address on 1 September 2026. It was not measured while it was online. Its two entries in this report, on its first and its last day, hold the oldest and the newest measurement of it, taken overnight on 23 and 24 October 2026, when it was put back on the main address for one day so it could be measured.
- Made with
- Squarespace
- Measured
- 2 times
Website 4
CurrentOverall score100/100Measured 4 Nov 2026From 1 Sept 2026 · 2 months so far
The custom-built website with its own booking form. It replaced website 3 directly on the live address, www.trinserhof.at, on 1 September 2026. Its two entries in this report hold its first measurement, taken on 23 October 2026 and shown on its first day, and its latest measurement, taken on 4 November 2026.
- Made with
- Custom-built
- Measured
- 2 times
Findability
Whether people searching online, and the AI assistants they increasingly ask, can find and understand the website.
Pages listed for Google
The sitemap tells search engines which pages exist. Every important page should be on it.
9was 6, an improvement on 31 AugLanguages
Each language version is a new way to be found by guests searching in their own language.
4was 1, an improvement on 31 AugBusiness details for Google (JSON-LD)
A hidden label that tells search engines and AI assistants exactly what the business is. It describes the page, the website, the hotel, the restaurant. Details are below.
80 of 100Guide for AI assistants
An llms.txt file gives assistants such as ChatGPT a short summary of the website and its most important pages. It is new and optional, but cheap to add.
Missing
Business details for search engines (JSON-LD)
What the website tells Google and AI assistants about the business behind it, read from every page at each measurement and scored on how complete it is. Check it yourself
What is JSON-LD?
A website is written for people: photos, headings and text. JSON-LD is a small label hidden in the page and written for computers. In a fixed format it says what the page is about: “this is a hotel, called Hotel Trinserhof, at Trins 106, check-in from 16:00, dogs welcome”. Visitors never see it.
JSON-LD stands for JavaScript Object Notation for Linked Data. The words it uses come from schema.org, a shared vocabulary agreed on by Google, Microsoft, Yahoo and Yandex.
What is it used for?
Search engines and AI assistants read the label instead of guessing from the text. Google uses it for the extras around a search result and on Maps: the name, address, price level, opening hours and reviews. AI assistants such as ChatGPT, Gemini and Copilot use the same details when someone asks for “a dog-friendly hotel with a sauna in Tyrol”.
What does it bring?
The website is understood exactly, without misreadings, in every language. The business gets correct details wherever it shows up, a better chance at the eye-catching search results that get more clicks, and answers in AI assistants that come from its own website rather than from a booking platform. JSON-LD does not move a website higher in Google by itself, and once in place it costs nothing to run; it only needs to stay up to date.
JSON-LD score over time
Structured data completeness, 0 to 100
How complete the business details are that the website hands to search engines. 0 means there is no JSON-LD at all. How it is scored
1·2·3·4
- trinserhof.at
- Not measured, set to 0
Show as table
| Measured | trinserhof.at |
|---|---|
| 4 Nov 2026, 11:34 | 80 |
| 31 Aug 2026 | 0, not measured |
| 1 Jan 2014 | 0, not measured |
| 1 Sept 2005 | 0, not measured |
| 1 May 2001 | 0, not measured |
What the website tells search engines, best first
Measured 4 Nov 2026, 11:34 on 8 pages
The page
WebPage · on HomeDescribes the page itself: its title, what it is about and which website it belongs to.
- Page titlename
- Hotel Trinserhof – Direkt buchen | Gschnitztal, Tirol
- Page addressurl
- https://www.trinserhof.at/
- Short descriptiondescription
- Familiengeführtes Hotel & Restaurant aus den 1920er-Jahren in Trins im Gschnitztal, Tirol. Zimmer mit Frühstück, Sauna und Slow-Food-Küche — direkt buchen, ohn…
- LanguageinLanguage
- de-AT
- Belongs to the websiteisPartOf
- Linked to https://www.trinserhof.at/#website
- What it is aboutabout
- Linked to https://www.trinserhof.at/#hotel
- Main photoprimaryImageOfPage
- https://www.trinserhof.at/og-image.jpg
Missing: Where it sits on the website
The website
WebSite · on HomeTells search engines the name of the website. Google shows this site name above the page title in its search results.
- Site namename
- Hotel Trinserhof – Direkt buchen | Gschnitztal, Tirol
- Website addressurl
- https://www.trinserhof.at/
- LanguageinLanguage
- de-AT
- Who runs itpublisher
- Linked to https://www.trinserhof.at/#hotel
Missing: Short or alternative name
The hotel
Hotel · on HomeTells search engines that this is a hotel, where it is, how to reach it and what it offers. This is the basis for the details next to the hotel in Google Search and Maps.
- Namename
- Hotel Trinserhof
- Addressaddress
- Trins 106, 6152, Trins, Tirol, AT
- Phone numbertelephone
- +43 676 961 9393
- Website addressurl
- https://www.trinserhof.at/
- Photosimage
- https://www.trinserhof.at/og-image.jpg, https://www.trinserhof.at/photos/trinserhof-facade-full.jpg, https://www.trinserhof.at/photos/trinserhof-in-gschnitztal…
- Short descriptiondescription
- Familiengeführtes Hotel & Restaurant aus den 1920er-Jahren in Trins im Gschnitztal, Tirol. Zimmer mit Frühstück, Sauna und Slow-Food-Küche — direkt buchen, ohn…
- Price levelpriceRange
- €€
- Check-in timecheckinTime
- 16:00
- Check-out timecheckoutTime
- 10:00
- FacilitiesamenityFeature
- Frühstück inklusive, Restaurant, Bar, Sauna and 13 more
- Logologo
- https://www.trinserhof.at/trinserhof-logo.svg
- Other profilessameAs
- https://trinserhof.at
Missing: Map position, Opening hours, Review score, Star rating
10 more details included
- legalName
- Trinserhof GmbH
- slogan
- Ein Haus mit Geschichte. Offen für Heute.
- hotel@trinserhof.at
- hasMap
- https://maps.app.goo.gl/5TB6avVm8Uw38apM6
- elevation
- 1226
- currenciesAccepted
- EUR
- petsAllowed
- Yes
- availableLanguage
- de, en, it, nl
- containsPlace
- Suite, Standard Zimmer, Familien Zimmer, 'Bergsteiger' Zimmer
- potentialAction
- Zahlungspflichtig reservieren
The restaurant
Restaurant · on HomeTells search engines that there is a restaurant, what it serves and whether you can book a table. Google uses it for restaurant searches such as “dinner near me”.
- Namename
- Restaurant Trinserhof
- Addressaddress
- Trins 106, 6152, Trins, Tirol, AT
- Phone numbertelephone
- +43 676 961 9393
- Website addressurl
- https://www.trinserhof.at/
- Short descriptiondescription
- In der Bauernstube und der Bücherstube kochen wir hausgemacht und mit regionalen Zutaten — Slow Food statt Inszenierung, gemeinsam an einem Tisch. Danach ein G…
- Price levelpriceRange
- €€
- Type of foodservesCuisine
- Tiroler Küche, Österreichisch, Slow Food
- Takes reservationsacceptsReservations
- Yes
Missing: Photos, Map position, Opening hours, Review score, Menu
2 more details included
- hotel@trinserhof.at
- isPartOf
- Linked to https://www.trinserhof.at/#hotel
No JSON-LD on Rooms, Restaurant menu, Gallery, Fein haben, Contact, Prices, Booking form. Those pages rely on the description on the home page.
| Measured | Website | What it described, best first | Score |
|---|---|---|---|
| 4 Nov 2026, 11:34 | Website 4trinserhof.at |
| |
| 31 Aug 2026 | Website 3Not measured | No JSON-LD, according to the owner | 0, not measured |
| 1 Jan 2014 | Website 3Not measured | No JSON-LD, according to the owner | 0, not measured |
| 1 Sept 2005 | Website 2Not measured | No JSON-LD, according to the owner | 0, not measured |
| 1 May 2001 | Website 1Not measured | No JSON-LD, according to the owner | 0, not measured |
Privacy and safety
Measured by opening the home page in a fresh phone browser without clicking anything.
Protections switched on
Browser settings that block common attacks, such as fake copies of the page or code slipped in by someone else.
5 of 5was 3 of 5, an improvement on 31 AugOutside companies contacted
Every outside service that loads with the page (analytics, fonts, chat widgets, trackers) costs speed and may need to be named in the privacy policy.
0was 5, an improvement on 31 AugCookies before the visitor agrees
Cookies set as soon as the page opens, before anyone clicks anything. Under the GDPR, tracking cookies need consent first.
0was 5, an improvement on 31 AugErrors while loading
Errors in the background are invisible to visitors but can break parts of the page.
0was 2, an improvement on 31 Aug
Every page
The speed score of each page on a phone, with the change since its first measurement.
| Page | Speed score | Change | Main content | Data | Trend |
|---|---|---|---|---|---|
| Home/ | +60, an improvement | 2.0 s | 353 KB | ||
| Rooms/zimmer | +66, an improvement | 943 ms | 645 KB | ||
| Restaurant menu/menu | +62, an improvement | 969 ms | 470 KB | ||
| Gallery/galerie | +62, an improvement | 961 ms | 2.7 MB | ||
| Fein haben/fein-haben | +70, an improvement | 2.0 s | 341 KB | ||
| Contact/kontakt | +64, an improvement | 945 ms | 187 KB | ||
| Prices/preise | New | 957 ms | 178 KB | ||
| Booking form/buchen | +68, an improvement | 2.6 s | 817 KB |
What can still be improved
Everything Lighthouse flagged on the home page on 4 Nov 2026, on a phone and on a computer.
Speed 8
- Photos could be sent in a smaller sizeImprove image delivery
- Files are loaded one after another instead of side by sideNetwork dependency tree
- Some files hold up the first view of the pageRender-blocking requests
- The page may react slowly to the very first tapMax Potential First Input Delay
- Code is downloaded but never usedReduce unused JavaScript
- Code takes a long time to run on a phoneReduce JavaScript execution time
- The phone’s processor is kept busy for a long timeMinimize main-thread work
- Photos have no fixed size, so the page can jumpImage elements do not have explicit width and height
AI assistants 2
- No guide for AI assistants (llms.txt)llms.txt does not follow recommendations
- No resource list for AI agents (ARD manifest)ARD manifest is invalid
Check it yourself
Free tools that show the same things this report measures, straight from the source.
- Google’s rich results testsearch.google.com
Shows which JSON-LD details Google can use for its eye-catching search results, and warns about anything it cannot read.
- Schema.org validatorvalidator.schema.org
Lists every JSON-LD detail on the home page exactly as a computer reads it, with errors and warnings.
- Earlier versions in the Internet Archiveweb.archive.org, the Wayback Machine
Copies of trinserhof.at saved over the years, to see what the website looked like and contained at the time.
- Google’s speed testPageSpeed Insights
The same Lighthouse measurement this report uses, run by Google on demand for the home page.
Measurement history
All 6 measurements
| Measured | Website | Overall | Phone | Computer | ||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Speed | Findability | Accessibility | Trust & safety | Speed | Findability | Accessibility | Trust & safety | |||
| 4 Nov 2026, 09:04 | Website 4trinserhof.at | |||||||||
| 1 Sept 2026, 02:00 | Website 4trinserhof.at | |||||||||
| 31 Aug 2026, 02:00 | Website 3trinserhof.at | |||||||||
| 1 Jan 2014, 01:00 | Website 3trinserhof.at | |||||||||
| 1 Sept 2005 | Website 2Not measured, all values set to 0 | 0, not measured | 0, not measured | 0, not measured | 0, not measured | 0, not measured | 0, not measured | 0, not measured | 0, not measured | 0, not measured |
| 1 May 2001 | Website 1Not measured, all values set to 0 | 0, not measured | 0, not measured | 0, not measured | 0, not measured | 0, not measured | 0, not measured | 0, not measured | 0, not measured | 0, not measured |