8.3 sec in total
1.9 sec
6.2 sec
177 ms
Click here to check amazing 80e Days content. Otherwise, check out these important facts you probably never knew about 80edays.com
80edays the epic around the world electric car trip in 80 days. Racing for future. International exhibitions, sustainable transport, product promotion and presentation platform. 33 countries, 25.000 m...
Visit 80edays.comWe analyzed 80edays.com page load time and found that the first response time was 1.9 sec and then it took 6.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
80edays.com performance score
name
value
score
weighting
Value7.2 s
1/100
10%
Value11.7 s
0/100
25%
Value16.5 s
0/100
10%
Value960 ms
29/100
30%
Value1.451
0/100
15%
Value13.8 s
10/100
10%
1890 ms
269 ms
345 ms
400 ms
406 ms
Our browser made a total of 94 requests to load all elements on the main page. We found that 67% of them (63 requests) were addressed to the original 80edays.com, 11% (10 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain 80edays.com.
Page size can be reduced by 271.5 kB (19%)
1.4 MB
1.1 MB
In fact, the total size of 80edays.com main page is 1.4 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. 65% of websites need less resources to load. Javascripts take 576.0 kB which makes up the majority of the site volume.
Potential reduce by 187.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. 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 187.4 kB or 83% of the original size.
Potential reduce by 21 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. 80e Days images are well optimized though.
Potential reduce by 69.5 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 69.5 kB or 12% of the original size.
Potential reduce by 14.5 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. 80edays.com has all CSS files already compressed.
Number of requests can be reduced by 64 (80%)
80
16
The browser has sent 80 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 80e Days. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 44 to 1 for JavaScripts and from 22 to 1 for CSS and as a result speed up the page load time.
80edays.com
1890 ms
dashicons.min.css
269 ms
extra.min.css
345 ms
index.min.css
400 ms
styles.css
406 ms
style.css
404 ms
dittyDisplays.css
404 ms
all.css
417 ms
magnific-popup.min.css
459 ms
core.min.css
518 ms
style.css
666 ms
css
28 ms
style.min.css
541 ms
css
29 ms
tablepress-combined.min.css
415 ms
ow_votes_display.css
435 ms
ow_votes_color.css
452 ms
ow_vote_prettyPhoto.css
523 ms
font-awesome.min.css
136 ms
ow_vote_fancybox.css
549 ms
owvideo-js.min.css
566 ms
js
101 ms
api:client.js
65 ms
ow_vote_buyvotes.js
616 ms
checkout.js
75 ms
sdk.js
62 ms
js
142 ms
1.js
61 ms
jquery.min.js
784 ms
jquery-migrate.min.js
778 ms
popup.min.js
778 ms
swiped-events.min.js
777 ms
imagesloaded.min.js
778 ms
effect.min.js
777 ms
ditty-news-ticker.js
872 ms
magnific-popup.js
857 ms
main.min.js
866 ms
dtq-default-vb.js
864 ms
idle-timer.min.js
842 ms
custom.js
904 ms
scripts.min.js
1103 ms
jquery.fitvids.js
975 ms
frontend-bundle.min.js
996 ms
common.js
996 ms
ow_vote_block_div.js
1004 ms
ow_vote_prettyPhoto.js
1030 ms
ow_vote_fancybox.js
989 ms
ow_vote_validate.js
922 ms
ow_votes_fbscript.js
867 ms
ow_count_down.js
864 ms
ow_vote_shortcode_jquery.js
883 ms
ow_audio.js
962 ms
jquery.ui.widget.js
952 ms
jquery.fileupload.js
940 ms
jquery.fileupload-process.js
877 ms
jquery.fileupload-validate.js
866 ms
ow_datetimepicker.js
857 ms
owvideo.min.js
1049 ms
OWYoutubeVimeo.min.js
890 ms
jquery.lazyloadxt.extra.min.js
883 ms
cb=gapi.loaded_0
91 ms
pptm.js
202 ms
80edlogo-2.svg
737 ms
tracker-2.svg
738 ms
calendar-2.svg
731 ms
support-2.svg
828 ms
sdk.js
48 ms
route-teams-2.svg
762 ms
about-2.svg
774 ms
info-2.svg
775 ms
bg-home3.jpg
1283 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw3aX8.ttf
37 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw3aX8.ttf
43 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw3aX8.ttf
51 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw3aX8.ttf
51 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw3aX8.ttf
51 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w3aX8.ttf
52 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w3aX8.ttf
47 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w3aX8.ttf
57 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w3aX8.ttf
55 ms
zOL64pLDlL1D99S8g8PtiKchq-lmiA.ttf
54 ms
modules.woff
857 ms
et-divi-dynamic-6965-late.css
864 ms
38 ms
logger
127 ms
ts
97 ms
analytics.js
100 ms
client.json
278 ms
client.json
280 ms
collect
16 ms
style.min.css
135 ms
visit
270 ms
modules.woff
131 ms
visit
68 ms
80edays.com accessibility score
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
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
80edays.com 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
Browser errors were logged to the console
Page has valid source maps
80edays.com SEO score
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 80edays.com 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 80edays.com 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.
80edays.com
Open Graph data is detected on the main page of 80e Days. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: