7.5 sec in total
1.9 sec
5.5 sec
127 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 5.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% 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%
1880 ms
290 ms
407 ms
406 ms
407 ms
Our browser made a total of 93 requests to load all elements on the main page. We found that 67% of them (62 requests) were addressed to the original 80edays.com, 11% (10 requests) were made to Fonts.gstatic.com and 4% (4 requests) were made to Googletagmanager.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 331.6 kB (23%)
1.5 MB
1.1 MB
In fact, the total size of 80edays.com main page is 1.5 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 643.7 kB which makes up the majority of the site volume.
Potential reduce by 187.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 187.1 kB or 84% 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. 80e Days images are well optimized though.
Potential reduce by 130.2 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 130.2 kB or 20% of the original size.
Potential reduce by 14.4 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 66 (84%)
79
13
The browser has sent 79 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 46 to 1 for JavaScripts and from 22 to 1 for CSS and as a result speed up the page load time.
80edays.com
1880 ms
dashicons.min.css
290 ms
extra.min.css
407 ms
styles.css
406 ms
style.css
407 ms
dittyDisplays.css
405 ms
all.css
531 ms
modules-style.css
429 ms
magnific-popup.min.css
574 ms
frontend.css
575 ms
index.min.css
577 ms
style.css
582 ms
css
44 ms
css
35 ms
tablepress-combined.min.css
459 ms
ow_votes_display.css
539 ms
ow_votes_color.css
580 ms
ow_vote_prettyPhoto.css
585 ms
font-awesome.min.css
58 ms
ow_vote_fancybox.css
587 ms
owvideo-js.min.css
588 ms
js
101 ms
api:client.js
52 ms
ow_vote_buyvotes.js
602 ms
checkout.js
61 ms
sdk.js
50 ms
js
143 ms
1.js
49 ms
swiped-events.min.js
733 ms
jquery.min.js
826 ms
jquery-migrate.min.js
733 ms
imagesloaded.min.js
733 ms
effect.min.js
735 ms
ditty-news-ticker.js
735 ms
magnific-popup.js
826 ms
slick.min.js
835 ms
counter-up.min.js
838 ms
frontend.js
849 ms
popup.min.js
848 ms
idle-timer.min.js
950 ms
custom.js
953 ms
scripts.min.js
1196 ms
jquery.fitvids.js
970 ms
common.js
976 ms
ow_vote_block_div.js
974 ms
ow_vote_prettyPhoto.js
1106 ms
ow_vote_fancybox.js
947 ms
ow_vote_validate.js
829 ms
ow_votes_fbscript.js
822 ms
ow_count_down.js
821 ms
ow_vote_shortcode_jquery.js
992 ms
ow_audio.js
966 ms
jquery.ui.widget.js
855 ms
jquery.fileupload.js
826 ms
jquery.fileupload-process.js
817 ms
jquery.fileupload-validate.js
865 ms
ow_datetimepicker.js
964 ms
owvideo.min.js
1200 ms
OWYoutubeVimeo.min.js
883 ms
jquery.lazyloadxt.extra.min.js
843 ms
cb=gapi.loaded_0
62 ms
pptm.js
212 ms
80edlogo-2.svg
771 ms
tracker-2.svg
799 ms
support-2.svg
899 ms
route-teams-2.svg
891 ms
sdk.js
27 ms
about-2.svg
820 ms
info-2.svg
822 ms
bg-home3.jpg
1216 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw3aX8.ttf
25 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw3aX8.ttf
29 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw3aX8.ttf
36 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw3aX8.ttf
40 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw3aX8.ttf
40 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w3aX8.ttf
41 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w3aX8.ttf
40 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w3aX8.ttf
41 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w3aX8.ttf
41 ms
zOL64pLDlL1D99S8g8PtiKchq-lmiA.ttf
44 ms
modules.woff
1212 ms
et-divi-dynamic-6965-late.css
937 ms
ts
72 ms
client.json
322 ms
client.json
326 ms
js
55 ms
js
126 ms
analytics.js
121 ms
style.min.css
125 ms
collect
30 ms
modules.woff
125 ms
visit
257 ms
visit
65 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: