4.2 sec in total
949 ms
3.1 sec
132 ms
Click here to check amazing Lppt EPFL content for Switzerland. Otherwise, check out these important facts you probably never knew about lppt.epfl.ch
Laboratory of Therapeutic Proteins and Peptides - LPPT Prof. Christian Heinis
Visit lppt.epfl.chWe analyzed Lppt.epfl.ch page load time and found that the first response time was 949 ms and then it took 3.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
lppt.epfl.ch performance score
name
value
score
weighting
Value5.2 s
8/100
10%
Value7.9 s
3/100
25%
Value8.1 s
20/100
10%
Value1,170 ms
21/100
30%
Value0
100/100
15%
Value8.9 s
34/100
10%
949 ms
191 ms
187 ms
294 ms
293 ms
Our browser made a total of 32 requests to load all elements on the main page. We found that 47% of them (15 requests) were addressed to the original Lppt.epfl.ch, 31% (10 requests) were made to Epfl.ch and 13% (4 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.6 sec) relates to the external source Epfl.ch.
Page size can be reduced by 203.5 kB (62%)
329.2 kB
125.7 kB
In fact, the total size of Lppt.epfl.ch main page is 329.2 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. Javascripts take 169.8 kB which makes up the majority of the site volume.
Potential reduce by 35.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 8.5 kB, which is 19% 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 35.6 kB or 81% of the original size.
Potential reduce by 15.5 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. Obviously, Lppt EPFL needs image optimization as it can save up to 15.5 kB or 51% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 81.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 81.8 kB or 48% of the original size.
Potential reduce by 70.6 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. Lppt.epfl.ch needs all CSS files to be minified and compressed as it can save up to 70.6 kB or 83% of the original size.
Number of requests can be reduced by 18 (58%)
31
13
The browser has sent 31 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lppt 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 5 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
lppt.epfl.ch
949 ms
epfl.css
191 ms
homePortal.css
187 ms
jahia.css
294 ms
sb.css
293 ms
jquery.min.js
6 ms
jquery.plugins.js
384 ms
epfl.js
291 ms
socialshare.js
195 ms
isic.css
501 ms
print.css
93 ms
ga.js
25 ms
wsi.ashx
253 ms
my-server.png
95 ms
underline.gif
93 ms
grey-facebook-round.png
276 ms
grey-twitter-round.png
278 ms
grey-linkedin-round.png
279 ms
grey-googleplus-round.png
276 ms
grey-mail-round.png
368 ms
keyvisual-lppt.gif
551 ms
epfl_small.png
172 ms
sprites-arrow.png
1016 ms
sprites.png
1144 ms
magnifier.png
1146 ms
separator.png
1609 ms
icon_home_white.png
452 ms
__utm.gif
25 ms
__utm.gif
22 ms
arrow-login.png
1575 ms
header_en.jsp
497 ms
__utm.gif
12 ms
lppt.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
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
lppt.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
lppt.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 Lppt.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 Lppt.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.
lppt.epfl.ch
Open Graph description is not detected on the main page of Lppt 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: