28.6 sec in total
5.7 sec
22.2 sec
760 ms
Visit imperialsoap.com now to see the best up-to-date Imperial Soap content and also check out these interesting facts you probably never knew about imperialsoap.com
Visit imperialsoap.comWe analyzed Imperialsoap.com page load time and found that the first response time was 5.7 sec and then it took 23 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster.
imperialsoap.com performance score
name
value
score
weighting
Value7.5 s
1/100
10%
Value23.7 s
0/100
25%
Value24.6 s
0/100
10%
Value2,570 ms
4/100
30%
Value0.152
75/100
15%
Value22.5 s
1/100
10%
5650 ms
9674 ms
234 ms
209 ms
232 ms
Our browser made a total of 93 requests to load all elements on the main page. We found that 51% of them (47 requests) were addressed to the original Imperialsoap.com, 12% (11 requests) were made to Fonts.gstatic.com and 10% (9 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (9.7 sec) belongs to the original domain Imperialsoap.com.
Page size can be reduced by 2.6 MB (21%)
12.4 MB
9.8 MB
In fact, the total size of Imperialsoap.com main page is 12.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. 85% 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 11.6 MB which makes up the majority of the site volume.
Potential reduce by 240.5 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 240.5 kB or 85% of the original size.
Potential reduce by 2.3 MB
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, Imperial Soap needs image optimization as it can save up to 2.3 MB or 20% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 56.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 56.2 kB or 14% of the original size.
Potential reduce by 26.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. Imperialsoap.com needs all CSS files to be minified and compressed as it can save up to 26.5 kB or 16% of the original size.
Number of requests can be reduced by 48 (66%)
73
25
The browser has sent 73 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Imperial Soap. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 31 to 1 for JavaScripts and from 19 to 1 for CSS and as a result speed up the page load time.
imperialsoap.com
5650 ms
imperialsoap.com
9674 ms
style.css
234 ms
widget-options.css
209 ms
woocommerce-layout.css
232 ms
woocommerce.css
218 ms
frontend.css
209 ms
style.min.css
236 ms
css
29 ms
all.css
163 ms
v4-shims.css
203 ms
style.css
371 ms
all.css
248 ms
js
48 ms
email-decode.min.js
171 ms
mediaelementplayer-legacy.min.css
432 ms
wp-mediaelement.min.css
412 ms
jquery.min.js
401 ms
jquery-migrate.min.js
390 ms
printomat.js
387 ms
print_elements.js
569 ms
jquery.blockUI.min.js
592 ms
add-to-cart.min.js
591 ms
js.cookie.min.js
599 ms
woocommerce.min.js
629 ms
gtm4wp-form-move-tracker.js
631 ms
frontend.min.js
766 ms
scripts.min.js
805 ms
jquery.fitvids.js
787 ms
jquery.visible.min.js
848 ms
common.js
836 ms
single-product.min.js
836 ms
mediaelement-and-player.min.js
968 ms
mediaelement-migrate.min.js
1001 ms
wp-mediaelement.min.js
1024 ms
footer-scripts.js
1025 ms
style.css
698 ms
gtm.js
152 ms
SV1XXeKVOeU
281 ms
logo.png
279 ms
since1963.png
277 ms
Victory-backpack-and-handheld-1.jpg
365 ms
victory.png
569 ms
Covid-19-Banner.png
903 ms
kaivac_group_photo.png
5122 ms
Riding-Floor-Cleaner.jpg
737 ms
BBB-Logo.png
736 ms
ISSA.png
569 ms
js
41 ms
analytics.js
85 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Ew-.ttf
86 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Ew-.ttf
120 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Ew-.ttf
131 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Ew-.ttf
136 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Uw-.ttf
178 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu170w-.ttf
170 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM70w-.ttf
169 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr70w-.ttf
169 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC70w-.ttf
169 ms
modules.woff
591 ms
fa-solid-900.woff
133 ms
fa-solid-900.woff
177 ms
fa-regular-400.woff
210 ms
fa-regular-400.woff
179 ms
et-divi-dynamic-11-late.css
1560 ms
collect
100 ms
collect
97 ms
www-player.css
17 ms
www-embed-player.js
54 ms
base.js
93 ms
collect
428 ms
collect
434 ms
js
207 ms
ad_status.js
221 ms
jz7nBWcXoC6PzFPxSGBK-EbGk4-kUqTnoXZXIXcr3eQ.js
159 ms
embed.js
52 ms
id
48 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
43 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
47 ms
Create
103 ms
GenerateIT
14 ms
Main-Banner-Imperial-Soap.jpg
461 ms
qoe
10 ms
log_event
0 ms
SV1XXeKVOeU
148 ms
ad_status.js
65 ms
Create
107 ms
id
54 ms
GenerateIT
16 ms
log_event
17 ms
woocommerce-smallscreen.css
337 ms
style.min.css
269 ms
style.min.css
21 ms
imperialsoap.com accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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.
imperialsoap.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
imperialsoap.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 Imperialsoap.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 Imperialsoap.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.
imperialsoap.com
Open Graph description is not detected on the main page of Imperial Soap. 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: