3.5 sec in total
270 ms
2.9 sec
365 ms
Click here to check amazing EPFL PRESS content. Otherwise, check out these important facts you probably never knew about epflpress.org
Swiss Scientific publisher
Visit epflpress.orgWe analyzed Epflpress.org page load time and found that the first response time was 270 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.
epflpress.org performance score
name
value
score
weighting
Value4.5 s
15/100
10%
Value8.3 s
2/100
25%
Value10.2 s
8/100
10%
Value610 ms
49/100
30%
Value0.037
100/100
15%
Value9.5 s
30/100
10%
270 ms
532 ms
181 ms
410 ms
73 ms
Our browser made a total of 66 requests to load all elements on the main page. We found that 92% of them (61 requests) were addressed to the original Epflpress.org, 5% (3 requests) were made to Google-analytics.com and 2% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Epflpress.org.
Page size can be reduced by 496.1 kB (39%)
1.3 MB
760.0 kB
In fact, the total size of Epflpress.org main page is 1.3 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. 35% of websites need less resources to load. Images take 848.6 kB which makes up the majority of the site volume.
Potential reduce by 38.8 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 6.3 kB, which is 14% 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 38.8 kB or 84% of the original size.
Potential reduce by 186.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, EPFL PRESS needs image optimization as it can save up to 186.5 kB or 22% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 202.1 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 202.1 kB or 73% of the original size.
Potential reduce by 68.7 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. Epflpress.org needs all CSS files to be minified and compressed as it can save up to 68.7 kB or 82% of the original size.
Number of requests can be reduced by 27 (43%)
63
36
The browser has sent 63 CSS, Javascripts, AJAX and image requests in order to completely render the main page of EPFL PRESS. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
epflpress.org
270 ms
www.epflpress.org
532 ms
common_en.css
181 ms
common.js
410 ms
css
73 ms
skin.css
88 ms
skin.js
100 ms
shadowbox-fr.js
172 ms
shadowbox-iframe.js
175 ms
shadowbox-img.js
188 ms
shadowbox-html.js
196 ms
body.png
98 ms
logo.png
123 ms
down-drop-menu.gif
122 ms
book.gif
121 ms
epub.png
97 ms
pdf.png
122 ms
search_bg.png
174 ms
search.png
175 ms
page.png
203 ms
newsletter.png
377 ms
plus-minus.png
191 ms
rss.png
193 ms
button_add2netvibes.gif
246 ms
button_add2myyahoo.gif
247 ms
button_add2windowslive.gif
287 ms
paybox-logo.gif
290 ms
slide_epfl_press_1.png
1008 ms
slide_epfl_press_3.png
593 ms
slide_epfl_press_ok.png
700 ms
slider_03.jpg
787 ms
previous-icon.png
599 ms
next-icon.png
676 ms
978-2-94022-288-9_small.jpg
687 ms
978-2-94022-278-0_small.jpg
709 ms
978-2-94022-290-2_small.jpg
775 ms
orchestration_small.jpg
780 ms
978-2-94022-279-7_small.jpg
800 ms
978-2-94022-272-8_small.jpg
820 ms
978-2-94022-281-0_small.jpg
882 ms
978-2-94022-277-3_small.jpg
864 ms
978-2-94022-276-6_small.jpg
883 ms
978-2-94022-282-7_small.jpg
906 ms
youtube_connect.png
919 ms
facebook_connect.png
949 ms
blog_connect.png
974 ms
twitter_connect.png
939 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
57 ms
analytics.js
29 ms
linkedin_connect.png
916 ms
mediainfo_connect.png
936 ms
bookapp_connect.png
935 ms
google_connect.png
968 ms
best-seller.png
987 ms
linkid.js
5 ms
collect
12 ms
print.css
89 ms
shadow-bg.png
87 ms
shadow-tr.png
99 ms
shadow-bl.png
96 ms
loading.gif
101 ms
close.png
87 ms
next.png
102 ms
play.png
173 ms
pause.png
173 ms
previous.png
188 ms
epflpress.org 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 input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Links do not have a discernible name
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
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
epflpress.org 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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
epflpress.org SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
Tap targets are not sized appropriately
FR
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Epflpress.org can be misinterpreted by Google and other search engines. Our service has detected that French is used on the page, and it does not match the claimed English language. Our system also found out that Epflpress.org 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.
epflpress.org
Open Graph description is not detected on the main page of EPFL PRESS. 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: