Tools & Wizards About Us
hofburg.wien.info screenshot

Report Summary

  • 32

    Performance

    Renders faster than
    52% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 67% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

hofburg.wien.info

Vienna Imperial Palace: The imperial legacy of the Habsburg dynasty. - vienna.info

Page Load Speed

4.6 sec in total

First Response

722 ms

Resources Loaded

3.3 sec

Page Rendered

589 ms

hofburg.wien.info screenshot

About Website

Click here to check amazing Hofburg Wien content for Austria. Otherwise, check out these important facts you probably never knew about hofburg.wien.info

Sisi Museum, Spanish Riding School, Imperial Apartments, and Heldenplatz are the highlights of the Imperial Palace, one of the biggest palace complexes in the world.

Visit hofburg.wien.info

Key Findings

We analyzed Hofburg.wien.info page load time and found that the first response time was 722 ms and then it took 3.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

hofburg.wien.info performance score

32

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.2 s

8/100

10%

LCP (Largest Contentful Paint)

Value8.2 s

2/100

25%

SI (Speed Index)

Value18.6 s

0/100

10%

TBT (Total Blocking Time)

Value410 ms

67/100

30%

CLS (Cumulative Layout Shift)

Value0.161

72/100

15%

TTI (Time to Interactive)

Value28.0 s

0/100

10%

Network Requests Diagram

hofburg.wien.info

722 ms

hofburg-vienna

327 ms

hofburg-vienna

543 ms

main.css

105 ms

built.js

505 ms

Our browser made a total of 48 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Hofburg.wien.info, 88% (42 requests) were made to Wien.info and 6% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Wien.info.

Page Optimization Overview & Recommendations

Page size can be reduced by 586.7 kB (24%)

Content Size

2.5 MB

After Optimization

1.9 MB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Hofburg.wien.info main page is 2.5 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 45% of websites need less resources to load. Images take 1.7 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 112.6 kB

  • Original 141.2 kB
  • After minification 120.9 kB
  • After compression 28.6 kB

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. This page needs HTML code to be minified as it can gain 20.2 kB, which is 14% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 112.6 kB or 80% of the original size.

Image Optimization

-4%

Potential reduce by 69.2 kB

  • Original 1.7 MB
  • After minification 1.7 MB

Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Hofburg Wien images are well optimized though.

JavaScript Optimization

-66%

Potential reduce by 405.0 kB

  • Original 615.3 kB
  • After minification 615.3 kB
  • After compression 210.3 kB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 405.0 kB or 66% of the original size.

Requests Breakdown

Number of requests can be reduced by 7 (16%)

Requests Now

45

After Optimization

38

  • Images
  • JavaScript
  • CSS

The browser has sent 45 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Hofburg Wien. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 5 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

hofburg.wien.info

hofburg.wien.info

722 ms

hofburg-vienna

hofburg-vienna

327 ms

hofburg-vienna

hofburg-vienna

543 ms

main.css

main.css

105 ms

built.js

built.js

505 ms

api.js

api.js

48 ms

analytics.js

analytics.js

42 ms

en.svg

en.svg

291 ms

image_header-medium

image_header-medium

612 ms

logo_wtfront-en.png

logo_wtfront-en.png

494 ms

image_claim-500

image_claim-500

621 ms

image_nav_teaser

image_nav_teaser

522 ms

image_nav_teaser

image_nav_teaser

524 ms

image_nav_teaser

image_nav_teaser

481 ms

image_nav_teaser

image_nav_teaser

585 ms

image_nav_teaser

image_nav_teaser

596 ms

image_nav_teaser

image_nav_teaser

623 ms

image_leading_article_teaser

image_leading_article_teaser

726 ms

image_teaser

image_teaser

785 ms

image_teaser

image_teaser

899 ms

image_teaser

image_teaser

814 ms

image_teaser

image_teaser

823 ms

image_teaser

image_teaser

927 ms

image_teaser

image_teaser

928 ms

image_teaser

image_teaser

888 ms

image_teaser

image_teaser

1017 ms

image_teaser

image_teaser

1027 ms

image_teaser

image_teaser

991 ms

image_teaser

image_teaser

1101 ms

image_teaser

image_teaser

1029 ms

image_teaser

image_teaser

1031 ms

image_teaser

image_teaser

1093 ms

image_teaser

image_teaser

1119 ms

image_teaser

image_teaser

1129 ms

image_teaser

image_teaser

1131 ms

image_teaser

image_teaser

1134 ms

image_teaser

image_teaser

1195 ms

image_teaser

image_teaser

1204 ms

image_teaser

image_teaser

1221 ms

image_teaser

image_teaser

1231 ms

image_wienkarte_promotion

image_wienkarte_promotion

1233 ms

recaptcha__en.js

recaptcha__en.js

35 ms

image_footer_promotion

image_footer_promotion

1235 ms

linkid.js

linkid.js

17 ms

collect

collect

14 ms

icons.data.svg.css

icons.data.svg.css

957 ms

icons.data.svg.css

icons.data.svg.css

862 ms

print.css

print.css

104 ms

Accessibility Review

hofburg.wien.info accessibility score

87

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

Names and labels

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

[lang] attributes do not have a valid value

Best Practices

hofburg.wien.info best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

hofburg.wien.info SEO score

92

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

Mobile Friendly

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hofburg.wien.info can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Hofburg.wien.info main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

hofburg.wien.info

Open Graph data is detected on the main page of Hofburg Wien. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: