10.6 sec in total
466 ms
9.7 sec
441 ms
Click here to check amazing Lnnme EPFL content for Switzerland. Otherwise, check out these important facts you probably never knew about lnnme.epfl.ch
Visit lnnme.epfl.chWe analyzed Lnnme.epfl.ch page load time and found that the first response time was 466 ms and then it took 10.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
lnnme.epfl.ch performance score
name
value
score
weighting
Value6.0 s
4/100
10%
Value10.5 s
0/100
25%
Value10.3 s
8/100
10%
Value1,280 ms
18/100
30%
Value0
100/100
15%
Value10.1 s
26/100
10%
466 ms
386 ms
1102 ms
186 ms
279 ms
Our browser made a total of 50 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Lnnme.epfl.ch, 42% (21 requests) were made to Lpmc.epfl.ch and 30% (15 requests) were made to Epfl.ch. The less responsive or slowest element that took the longest time to load (7.7 sec) relates to the external source Lpmc.epfl.ch.
Page size can be reduced by 338.6 kB (60%)
560.4 kB
221.8 kB
In fact, the total size of Lnnme.epfl.ch main page is 560.4 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. 25% of websites need less resources to load. Javascripts take 398.3 kB which makes up the majority of the site volume.
Potential reduce by 63.1 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. 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 63.1 kB or 73% 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. Lnnme EPFL images are well optimized though.
Potential reduce by 223.7 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 223.7 kB or 56% of the original size.
Potential reduce by 51.8 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. Lnnme.epfl.ch needs all CSS files to be minified and compressed as it can save up to 51.8 kB or 83% of the original size.
Number of requests can be reduced by 22 (46%)
48
26
The browser has sent 48 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lnnme EPFL. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 7 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
lnnme.epfl.ch
466 ms
lpmc.epfl.ch
386 ms
epfl.css
1102 ms
homePortal.css
186 ms
jahia.css
279 ms
sb.css
1193 ms
jquery.min.js
5 ms
jquery.plugins.js
381 ms
epfl.js
277 ms
socialshare.js
186 ms
addthis_widget.js
9 ms
wsi.ashx
265 ms
my-server.png
145 ms
324x182.jpg
394 ms
grey-facebook-round.png
276 ms
grey-twitter-round.png
277 ms
grey-linkedin-round.png
277 ms
grey-googleplus-round.png
277 ms
grey-mail-round.png
368 ms
Mozaik%20of%20crystals2.jpg
831 ms
Laszlo%20Forro2015.jpg
866 ms
LOGO-ERC.jpg
1048 ms
Davor.jpg
867 ms
Daniele%20Mari.jpg
1488 ms
evelyn_Laszlo.jpg
935 ms
DBK2016.png
7706 ms
160x90.jpg
584 ms
160x90.jpg
587 ms
160x90.jpg
601 ms
underline.gif
135 ms
epfl_small.png
194 ms
sprites-arrow.png
192 ms
sprites.png
192 ms
magnifier.png
192 ms
separator.png
194 ms
icon_home_white.png
1038 ms
dot.png
161 ms
underline-white.gif
242 ms
news-categories-en-bw.png
244 ms
arrow-more.gif
244 ms
icon_video.png
245 ms
arrow-login.png
246 ms
300lo.json
39 ms
ga.js
35 ms
header_en.jsp
1009 ms
sh.953eb77977227bfd253ee158.html
47 ms
__utm.gif
32 ms
__utm.gif
23 ms
__utm.gif
24 ms
print.css
93 ms
lnnme.epfl.ch accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
lnnme.epfl.ch 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
lnnme.epfl.ch SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lnnme.epfl.ch 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 Lnnme.epfl.ch 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.
lnnme.epfl.ch
Open Graph description is not detected on the main page of Lnnme EPFL. 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: