3.7 sec in total
292 ms
3.2 sec
194 ms
Click here to check amazing Tue content for Netherlands. Otherwise, check out these important facts you probably never knew about tue.nl
Eindhoven University of Technology (TU/e) is a research university specializing in engineering science & technology.
Visit tue.nlWe analyzed Tue.nl page load time and found that the first response time was 292 ms and then it took 3.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
tue.nl performance score
name
value
score
weighting
Value4.2 s
20/100
10%
Value8.9 s
1/100
25%
Value7.8 s
23/100
10%
Value400 ms
68/100
30%
Value0.009
100/100
15%
Value9.0 s
33/100
10%
292 ms
389 ms
406 ms
100 ms
99 ms
Our browser made a total of 67 requests to load all elements on the main page. We found that 85% of them (57 requests) were addressed to the original Tue.nl, 4% (3 requests) were made to Google.com and 3% (2 requests) were made to Cse.google.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Assets.w3.tue.nl.
Page size can be reduced by 207.5 kB (22%)
934.6 kB
727.1 kB
In fact, the total size of Tue.nl main page is 934.6 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. 55% of websites need less resources to load. Javascripts take 373.3 kB which makes up the majority of the site volume.
Potential reduce by 65.4 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 17.3 kB, which is 23% 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 65.4 kB or 86% of the original size.
Potential reduce by 0 B
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. Tue images are well optimized though.
Potential reduce by 84.8 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 84.8 kB or 23% of the original size.
Potential reduce by 57.2 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. Tue.nl needs all CSS files to be minified and compressed as it can save up to 57.2 kB or 45% of the original size.
Number of requests can be reduced by 54 (90%)
60
6
The browser has sent 60 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Tue. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 47 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
tue.nl
292 ms
tue.nl
389 ms
406 ms
7015c8c4ac5ff815b57530b221005fc6.css
100 ms
CookieNotice.css
99 ms
magnific-popup.css
199 ms
pikaday.min.css
197 ms
Style.min.css
302 ms
TueMenu.min.css
298 ms
TueStyling.min.css
533 ms
cse.js
50 ms
dfc25987ec0b988c9a083b0fbe99c4ee.js
392 ms
CookieNotice.js
392 ms
jquery-1_11_2.js
734 ms
donationForm.js
393 ms
foundation.js
397 ms
pikaday.js
489 ms
parseDate.js
489 ms
dateFormat.js
490 ms
formDatePicker.js
493 ms
modernizr.min.js
632 ms
jquery.main.js
633 ms
magnific-popup.min.js
630 ms
magnific-popup-initializer.js
637 ms
stacktable.min.js
638 ms
CreatePrintImages.js
770 ms
MediaQueryChange.js
768 ms
InitFoundation.js
768 ms
CookieConsent.js
777 ms
Form.min.js
778 ms
svg4everybody.min.js
857 ms
init.js
859 ms
globalNavigation.js
858 ms
sideMainMenu.js
859 ms
stickyQuickLinksBar.js
861 ms
scrollingHeader.js
862 ms
searchBox.js
923 ms
mobileNavigation.js
925 ms
objectfit.min.js
925 ms
foundation.accordion.js
926 ms
init.js
846 ms
sectionMenu.js
846 ms
readMore.js
823 ms
loadMore.js
824 ms
eventFormDatePicker.js
725 ms
filters.js
712 ms
scrollToTop.js
643 ms
smoothScroll.js
644 ms
formfilefieldfix.js
724 ms
focusFields.js
721 ms
contentSlider.js
630 ms
donationTeaser.js
630 ms
cse_element__en.js
28 ms
default+en.css
78 ms
default.css
82 ms
gtm.js
154 ms
csm_Delia%204_8966678ef9.jpg
1104 ms
sprite.svg
580 ms
sprite.svg
582 ms
lato-regular.woff
583 ms
lato-bold.woff
578 ms
Gilroy-ExtraBold.woff
548 ms
Gilroy-Light.woff
609 ms
analytics.js
30 ms
insight.min.js
62 ms
collect
20 ms
async-ads.js
78 ms
tue.nl 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
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
tue.nl 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
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
tue.nl 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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Tue.nl 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 Tue.nl 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.
tue.nl
Open Graph description is not detected on the main page of Tue. 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: