2.7 sec in total
746 ms
1.5 sec
447 ms
Click here to check amazing Edgewell content for United States. Otherwise, check out these important facts you probably never knew about edgewell.com
Meet Edgewell, a global company with more than 25 market-leading brands in shave, grooming, sun, skin and feminine care.
Visit edgewell.comWe analyzed Edgewell.com page load time and found that the first response time was 746 ms and then it took 1.9 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
edgewell.com performance score
name
value
score
weighting
Value10.1 s
0/100
10%
Value23.8 s
0/100
25%
Value11.2 s
5/100
10%
Value290 ms
79/100
30%
Value0.333
34/100
15%
Value22.4 s
1/100
10%
746 ms
149 ms
75 ms
77 ms
54 ms
Our browser made a total of 57 requests to load all elements on the main page. We found that 84% of them (48 requests) were addressed to the original Edgewell.com, 7% (4 requests) were made to Google.com and 4% (2 requests) were made to Cse.google.com. The less responsive or slowest element that took the longest time to load (746 ms) belongs to the original domain Edgewell.com.
Page size can be reduced by 1.2 MB (25%)
4.7 MB
3.5 MB
In fact, the total size of Edgewell.com main page is 4.7 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. 80% 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. Images take 3.3 MB which makes up the majority of the site volume.
Potential reduce by 58.2 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 58.2 kB or 82% of the original size.
Potential reduce by 86.2 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. Edgewell images are well optimized though.
Potential reduce by 838.3 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 838.3 kB or 80% of the original size.
Potential reduce by 174.8 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. Edgewell.com needs all CSS files to be minified and compressed as it can save up to 174.8 kB or 87% of the original size.
Number of requests can be reduced by 23 (42%)
55
32
The browser has sent 55 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Edgewell. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
edgewell.com
746 ms
main.css
149 ms
modernizr-2.8.3-respond-1.4.2.min.js
75 ms
detectizr.js
77 ms
language-selector.css
54 ms
style.css
84 ms
royalslider.css
81 ms
rs-epc.css
99 ms
jquery-2.1.3.js
227 ms
jqueryUI.js
346 ms
vimeo.ga.min.js
112 ms
require.js
121 ms
gradientText.js
30 ms
wp-embed.min.js
28 ms
sitepress.js
39 ms
jquery.royalslider.min.js
99 ms
2e45f9
140 ms
wp-emoji-release.min.js
69 ms
language-icon.png
98 ms
magnifying-lens.png
96 ms
logo.png
98 ms
hummingbird-slider.jpg
99 ms
homepage-slide-2-with-gradient-new1.jpg
260 ms
homepage-slide-4-with-gradient.jpg
255 ms
homepage-slide-3-with-gradient-new.jpg
272 ms
homepage-slide-mobile-1.jpg
254 ms
homepage-slide-mobile-2.jpg
265 ms
mobile-our-history-hero-image2.jpg
255 ms
homepage-slide-mobile-3.jpg
259 ms
gretchen-homepage-retina.jpg
255 ms
gretchen-homepage-344x210.jpg
256 ms
homepage-image2-retina.jpg
263 ms
homepage-image2-344x210.jpg
256 ms
homepage-image3-retina.jpg
265 ms
homepage-image3-344x210.jpg
263 ms
brands-desktop1.png
267 ms
brands-desktop-hover-en1.png
263 ms
brands-tablet.png
265 ms
brands-tablet-hover-en.png
310 ms
brands-mobile.png
266 ms
app.build.js
227 ms
cse.js
200 ms
analytics.js
45 ms
preloader-white.gif
179 ms
next-prev.png
179 ms
2E45F9_B_0.woff
207 ms
2E45F9_7_0.woff
209 ms
2E45F9_A_0.woff
209 ms
2E45F9_6_0.woff
209 ms
collect
58 ms
jsapi
107 ms
selectbox-arrow.png
46 ms
default+en.css
3 ms
default.css
38 ms
default+en.I.js
7 ms
default.css
25 ms
print.css
35 ms
edgewell.com 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-*] attributes do not match their roles
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
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.
edgewell.com 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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
edgewell.com 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 Edgewell.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 Edgewell.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.
edgewell.com
Open Graph data is detected on the main page of Edgewell. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: