5.3 sec in total
179 ms
4.9 sec
227 ms
Click here to check amazing Prevasive content. Otherwise, check out these important facts you probably never knew about prevasive.com
Superior cleaning solutions including EPA-registered product against Cdiff (Kills spores in 2 minutes), Norovirus, TB, Kills 99.999% germs in 30 seconds
Visit prevasive.comWe analyzed Prevasive.com page load time and found that the first response time was 179 ms and then it took 5.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
prevasive.com performance score
name
value
score
weighting
Value3.5 s
34/100
10%
Value10.7 s
0/100
25%
Value12.0 s
4/100
10%
Value1,400 ms
16/100
30%
Value0.389
26/100
15%
Value10.2 s
25/100
10%
179 ms
2536 ms
111 ms
259 ms
266 ms
Our browser made a total of 116 requests to load all elements on the main page. We found that 75% of them (87 requests) were addressed to the original Prevasive.com, 20% (23 requests) were made to Fonts.gstatic.com and 3% (3 requests) were made to Stats.wp.com. The less responsive or slowest element that took the longest time to load (2.5 sec) belongs to the original domain Prevasive.com.
Page size can be reduced by 388.4 kB (13%)
3.1 MB
2.7 MB
In fact, the total size of Prevasive.com main page is 3.1 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. 70% of websites need less resources to load. Images take 2.1 MB which makes up the majority of the site volume.
Potential reduce by 358.0 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 358.0 kB or 87% of the original size.
Potential reduce by 19.1 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. Prevasive images are well optimized though.
Potential reduce by 7.9 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. This website has mostly compressed JavaScripts.
Potential reduce by 3.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. Prevasive.com has all CSS files already compressed.
Number of requests can be reduced by 66 (74%)
89
23
The browser has sent 89 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Prevasive. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 56 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
prevasive.com
179 ms
prevasive.com
2536 ms
mediaelementplayer-legacy.min.css
111 ms
wp-mediaelement.min.css
259 ms
settings.css
266 ms
woocommerce-layout.css
330 ms
woocommerce.css
332 ms
checkout-blocks.css
285 ms
wp-review.css
135 ms
woocommerce.css
205 ms
jquery.min.js
323 ms
jquery-migrate.min.js
281 ms
wp-polyfill-inert.min.js
293 ms
regenerator-runtime.min.js
348 ms
wp-polyfill.min.js
393 ms
hooks.min.js
365 ms
w.js
41 ms
en-wwe-small-checkout.js
366 ms
jquery.blockUI.min.js
360 ms
add-to-cart.min.js
391 ms
js.cookie.min.js
418 ms
woocommerce.min.js
430 ms
s-202403.js
40 ms
ai.min.js
447 ms
css
54 ms
wc-blocks.css
443 ms
jquery.themepunch.tools.min.js
530 ms
jquery.themepunch.revolution.min.js
501 ms
sourcebuster.min.js
501 ms
order-attribution.min.js
502 ms
react.min.js
531 ms
deprecated.min.js
531 ms
dom.min.js
556 ms
react-dom.min.js
691 ms
escape-html.min.js
570 ms
element.min.js
596 ms
is-shallow-equal.min.js
603 ms
i18n.min.js
616 ms
keycodes.min.js
630 ms
priority-queue.min.js
639 ms
e-202403.js
36 ms
compose.min.js
652 ms
private-apis.min.js
621 ms
redux-routine.min.js
551 ms
data.min.js
511 ms
lodash.min.js
527 ms
wc-blocks-registry.js
506 ms
url.min.js
484 ms
api-fetch.min.js
481 ms
wc-settings.js
477 ms
data-controls.min.js
501 ms
html-entities.min.js
505 ms
notices.min.js
475 ms
wc-blocks-middleware.js
482 ms
wc-blocks-data.js
539 ms
dom-ready.min.js
481 ms
a11y.min.js
507 ms
primitives.min.js
477 ms
g.gif
14 ms
warning.min.js
466 ms
blocks-components.js
527 ms
blocks-checkout.js
553 ms
order-attribution-blocks.min.js
492 ms
Screen-Shot-2019-06-07-at-6.49.34-PM.png
753 ms
PREVASIVELOGO-resize.png
327 ms
atom-thyme.png
522 ms
scripts.min.js
565 ms
jquery.fitvids.js
444 ms
underscore.min.js
475 ms
wp-util.min.js
475 ms
main.js
489 ms
common.js
491 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVQ.woff
25 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVc.ttf
28 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVQ.woff
40 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVc.ttf
49 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVQ.woff
49 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVc.ttf
49 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf
48 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVQ.woff
48 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVc.ttf
48 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4uaVQ.woff
61 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4uaVc.ttf
63 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkWV4exg.woff
61 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkWV4exQ.ttf
61 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk5hkWV4exg.woff
62 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk5hkWV4exQ.ttf
62 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkxhjWV4exg.woff
64 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkxhjWV4exQ.ttf
66 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkyFjWV4exg.woff
63 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkyFjWV4exQ.ttf
66 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk0ZjWV4exg.woff
66 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk0ZjWV4exQ.ttf
65 ms
modules.woff
522 ms
dummy.png
504 ms
g.gif
104 ms
revolution.extension.video.min.js
81 ms
revolution.extension.slideanims.min.js
78 ms
revolution.extension.actions.min.js
81 ms
revolution.extension.layeranimation.min.js
87 ms
revolution.extension.kenburn.min.js
82 ms
revolution.extension.navigation.min.js
88 ms
revolution.extension.parallax.min.js
134 ms
KFOlCnqEu92Fr1MmWUlfBBc9.ttf
9 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
8 ms
woocommerce-smallscreen.css
140 ms
Screen-Shot-2019-09-09-at-12.48.23-PM.png
213 ms
healthy-world.png
198 ms
bacteria-prevasive.png
144 ms
Screen-Shot-2019-06-07-at-6.49.34-PM.png
608 ms
revicons.woff
79 ms
MOLD-BUBBLE.png
214 ms
BAC_resize.png
252 ms
marina-prevasive.png
121 ms
Heavy-Duty-Cleaner_1g.png
93 ms
style.min.css
74 ms
prevasive.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
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.
prevasive.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
prevasive.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
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 Prevasive.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 Prevasive.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.
prevasive.com
Open Graph data is detected on the main page of Prevasive. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: