2.9 sec in total
571 ms
2.2 sec
130 ms
Welcome to orpheum.at homepage info - get ready to check Orpheum best content for Austria right away, or after learning these important things about orpheum.at
Willkommen im Orpheum Wien - Erleben Sie einzigartige Kabaretts, Konzerte und vieles mehr in einer einzigartigen Location
Visit orpheum.atWe analyzed Orpheum.at page load time and found that the first response time was 571 ms and then it took 2.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
orpheum.at performance score
name
value
score
weighting
Value4.0 s
23/100
10%
Value10.9 s
0/100
25%
Value10.2 s
9/100
10%
Value200 ms
90/100
30%
Value0.391
26/100
15%
Value9.1 s
33/100
10%
571 ms
117 ms
211 ms
502 ms
216 ms
Our browser made a total of 70 requests to load all elements on the main page. We found that 97% of them (68 requests) were addressed to the original Orpheum.at, 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (639 ms) belongs to the original domain Orpheum.at.
Page size can be reduced by 32.9 kB (19%)
174.0 kB
141.2 kB
In fact, the total size of Orpheum.at main page is 174.0 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 20% of websites need less resources to load. Images take 119.8 kB which makes up the majority of the site volume.
Potential reduce by 503 B
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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 503 B or 64% of the original size.
Potential reduce by 1.4 kB
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. Orpheum images are well optimized though.
Potential reduce by 34 B
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. This website has mostly compressed JavaScripts.
Potential reduce by 30.9 kB
CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Orpheum.at needs all CSS files to be minified and compressed as it can save up to 30.9 kB or 85% of the original size.
Number of requests can be reduced by 42 (66%)
64
22
The browser has sent 64 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Orpheum. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 10 to 1 for CSS and as a result speed up the page load time.
orpheum.at
571 ms
frame_navi.php
117 ms
frame_titel.htm
211 ms
willkommen
502 ms
frame_werbung.htm
216 ms
links_bg.GIF
107 ms
rig.GIF
202 ms
wi_on.GIF
205 ms
pr_up.GIF
210 ms
hi_up.GIF
209 ms
ka_up.GIF
210 ms
th_up.GIF
305 ms
es_up.GIF
308 ms
ko_up.GIF
314 ms
ende.GIF
314 ms
oben_bg.GIF
226 ms
logo_we_rahmen_weiss.jpg
318 ms
a_www01.GIF
322 ms
orpheum.GIF
330 ms
a_at01.GIF
330 ms
ar_up.gif
324 ms
ar_do.gif
395 ms
ar_on.gif
421 ms
li_up.gif
424 ms
li_do.gif
428 ms
li_on.gif
433 ms
spe_up.gif
433 ms
spe_do.gif
499 ms
spe_on.gif
526 ms
board.GIF
528 ms
a_info.GIF
636 ms
newsletter.gif
538 ms
facebook-logo-orpheum.gif
539 ms
oe1.gif
603 ms
ba_logo.png
630 ms
layout_2col_fixed_seo.css
575 ms
main.css
577 ms
zen.css
573 ms
wi_up.GIF
418 ms
wi_do.GIF
429 ms
pr_on.GIF
429 ms
pr_do.GIF
495 ms
hi_on.GIF
521 ms
hi_do.GIF
523 ms
ka_on.GIF
524 ms
ka_do.GIF
533 ms
th_on.GIF
533 ms
th_do.GIF
598 ms
es_on.GIF
627 ms
es_do.GIF
627 ms
ko_do.GIF
628 ms
ko_on.GIF
639 ms
base.css
113 ms
nav_shinybuttons.css
111 ms
basemod.css
108 ms
basemod_2col_fixed_seo.css
211 ms
content.css
213 ms
print_100_draft.css
211 ms
print_base.css
109 ms
ga.js
30 ms
orphkl.GIF
107 ms
sp.gif
106 ms
oj_plakat_04_(c)_jan_frankl100.jpg
213 ms
Mike_Supancic_30x20MoritzSchell100.jpg
213 ms
Presse_Weltfremd_02-(c)LukasBeck100.jpg
215 ms
Ostbahnwoche_Orpheum_kl100.jpg
115 ms
PR_TRAB_1(c)FelicitasMatern100.jpg
310 ms
balken.jpg
104 ms
bg_face.jpg
109 ms
__utm.gif
22 ms
orpheum.at accessibility score
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
Image elements do not have [alt] attributes
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
List items (<li>) are not contained within <ul> or <ol> parent elements.
orpheum.at best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
orpheum.at SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
Document uses legible font sizes
DE
N/A
N/A
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Orpheum.at can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Orpheum.at main page’s claimed encoding is . 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.
orpheum.at
Open Graph description is not detected on the main page of Orpheum. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: