2.2 sec in total
19 ms
2.1 sec
56 ms
Welcome to alexeaves.com homepage info - get ready to check Alexeaves best content right away, or after learning these important things about alexeaves.com
Visit alexeaves.comWe analyzed Alexeaves.com page load time and found that the first response time was 19 ms and then it took 2.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
alexeaves.com performance score
name
value
score
weighting
Value3.2 s
43/100
10%
Value6.0 s
13/100
25%
Value3.2 s
92/100
10%
Value100 ms
98/100
30%
Value0
100/100
15%
Value10.6 s
23/100
10%
19 ms
29 ms
90 ms
38 ms
36 ms
Our browser made a total of 52 requests to load all elements on the main page. We found that 4% of them (2 requests) were addressed to the original Alexeaves.com, 35% (18 requests) were made to Static.wixstatic.com and 31% (16 requests) were made to Static.parastorage.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Polyfill-fastly.io.
Page size can be reduced by 965.1 kB (54%)
1.8 MB
821.8 kB
In fact, the total size of Alexeaves.com main page is 1.8 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. 25% of websites need less resources to load. HTML takes 1.1 MB which makes up the majority of the site volume.
Potential reduce by 894.7 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 894.7 kB or 80% of the original size.
Potential reduce by 22.3 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. Alexeaves images are well optimized though.
Potential reduce by 48.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 48.1 kB or 17% of the original size.
Number of requests can be reduced by 10 (30%)
33
23
The browser has sent 33 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Alexeaves. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and as a result speed up the page load time.
alexeaves.com
19 ms
www.alexeaves.com
29 ms
alex-eaves
90 ms
minified.js
38 ms
focus-within-polyfill.js
36 ms
polyfill.min.js
1151 ms
thunderbolt-commons.5df16dfe.bundle.min.js
43 ms
main.dda15fae.bundle.min.js
49 ms
main.renderer.1d21f023.bundle.min.js
46 ms
lodash.min.js
48 ms
react.production.min.js
46 ms
react-dom.production.min.js
48 ms
siteTags.bundle.min.js
47 ms
Escape%20The%20Waste%20logo%20no%20background.png
202 ms
AlexEavesBioPhoto2024.jpg
362 ms
0e9f49_98ae8ee02f994f91b8a790d952553c44~mv2.jpg
363 ms
0e9f49_3a29469011d44f2881eb8ce3575ed9f0~mv2.jpg
269 ms
0e9f49_4acc14d7c3fc4530a95248c0c8d7bfd7~mv2.jpeg
298 ms
0e9f49_8003ec3942234500a6edac6f090594c8~mv2.jpeg
305 ms
0e9f49_46882464dbb04b6d9b11a894d67d4fb8~mv2.png
418 ms
0e9f49_b7356c6fdc8142989c22d59e94d4604f~mv2.jpeg
488 ms
0e9f49_89150a6447c642d8a8d6717b7fcc4e68~mv2.jpeg
607 ms
0e9f49_b347ddf214504e44bc68aba33b2ea716~mv2.png
481 ms
0e9f49_55491bbeae8445909566585573414c7a~mv2.png
503 ms
0e9f49_98ae8ee02f994f91b8a790d952553c44~mv2.jpg
437 ms
0e9f49_3a29469011d44f2881eb8ce3575ed9f0~mv2.jpg
661 ms
0e9f49_9dc3af67e828494c8100f951d1e9f075~mv2.jpg
725 ms
0e9f49_a0d104afb6d94b44a25a829d8e8d67b2~mv2.jpg
675 ms
0e9f49_8c0662d869194990af022722182b7810~mv2.png
708 ms
0e9f49_ed67aa2ab23d495185c08636618ff181~mv2.jpg
686 ms
0e9f49_17c470f5e9104043b90afdcb3d6c9deb~mv2.jpg
747 ms
bundle.min.js
66 ms
908c4810-64db-4b46-bb8e-823eb41f68c0.woff
6 ms
114 ms
112 ms
108 ms
109 ms
107 ms
108 ms
155 ms
151 ms
150 ms
151 ms
148 ms
146 ms
deprecation-en.v5.html
5 ms
bolt-performance
19 ms
deprecation-style.v5.css
5 ms
right-arrow.svg
15 ms
WixMadeforDisplay_W_Bd.woff
4 ms
WixMadeforText_W_Bd.woff
6 ms
WixMadeforText_W_Rg.woff
6 ms
alexeaves.com 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.
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
alexeaves.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
Page has valid source maps
alexeaves.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
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 Alexeaves.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 Alexeaves.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.
alexeaves.com
Open Graph description is not detected on the main page of Alexeaves. 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: