3.8 sec in total
519 ms
3 sec
257 ms
Click here to check amazing HEPHY content for Austria. Otherwise, check out these important facts you probably never knew about hephy.at
Visit hephy.atWe analyzed Hephy.at page load time and found that the first response time was 519 ms and then it took 3.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
hephy.at performance score
name
value
score
weighting
Value5.1 s
8/100
10%
Value8.2 s
2/100
25%
Value10.4 s
8/100
10%
Value1,060 ms
25/100
30%
Value0.813
4/100
15%
Value18.3 s
3/100
10%
519 ms
443 ms
206 ms
411 ms
17 ms
Our browser made a total of 31 requests to load all elements on the main page. We found that 90% of them (28 requests) were addressed to the original Hephy.at, 6% (2 requests) were made to Cdn.mathjax.org and 3% (1 request) were made to Piwik.hephy.at. The less responsive or slowest element that took the longest time to load (934 ms) belongs to the original domain Hephy.at.
Page size can be reduced by 844.7 kB (30%)
2.8 MB
2.0 MB
In fact, the total size of Hephy.at main page is 2.8 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. 55% of websites need less resources to load. Images take 1.9 MB which makes up the majority of the site volume.
Potential reduce by 56.2 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 14.6 kB, which is 22% 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 56.2 kB or 86% of the original size.
Potential reduce by 151.1 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. HEPHY images are well optimized though.
Potential reduce by 470.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 470.3 kB or 72% of the original size.
Potential reduce by 167.1 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. Hephy.at needs all CSS files to be minified and compressed as it can save up to 167.1 kB or 85% of the original size.
Number of requests can be reduced by 8 (33%)
24
16
The browser has sent 24 CSS, Javascripts, AJAX and image requests in order to completely render the main page of HEPHY. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and as a result speed up the page load time.
hephy.at
519 ms
www.hephy.at
443 ms
merged-bdd3a53233d02077221c4070c8b16718-80d4560363ee42aa85313d60016d277f.css
206 ms
merged-256c1eadc1f6753959eecef59de47c9f-f29d66d679a8b7729b3ebe7c139d1c4e.js
411 ms
MathJax.js
17 ms
slightbox.css
222 ms
prototype.1.7.0.yui.js
307 ms
scriptaculous.js
221 ms
lightbox.2.0.5.yui.js
222 ms
TeX-AMS-MML_HTMLorMML.js
18 ms
effects.js
103 ms
builder.js
102 ms
logo.png
702 ms
csm_bild1_slider_013452af95.jpg
406 ms
csm_tunnel_cb16fc55a7.jpg
607 ms
csm_wafer_banner_bc69b237f7.jpg
303 ms
csm_sadasss6_65c8d7296a.png
934 ms
csm_collage_9ce8cef741.jpg
518 ms
news_bgr.jpg
507 ms
csm_SuperKEKB_eca9c3407e.jpg
507 ms
csm_Masterclasses_2016_51f7ea0944.jpg
611 ms
csm_ChristophSchwanda_CR_MarkusTordik_A17061weiss_53289b1df2.jpg
610 ms
OEAW_logo.png
622 ms
piwik.js
687 ms
square.png
622 ms
sub_gradient.png
622 ms
.woff
640 ms
glyphicons-halflings-regular.woff
713 ms
piwik.js
782 ms
OpenSans-Regular.ttf
105 ms
Roboto-Regular.ttf
203 ms
hephy.at accessibility score
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
[aria-*] attributes do not match their roles
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
Links do not have a discernible name
hephy.at best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
hephy.at SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
Tap targets are not sized appropriately
DE
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hephy.at can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and it matches the claimed language. Our system also found out that Hephy.at main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.
hephy.at
Open Graph description is not detected on the main page of HEPHY. 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: