3.3 sec in total
101 ms
2.9 sec
322 ms
Welcome to chemomouthpiece.com homepage info - get ready to check Chemo Mouthpiece best content right away, or after learning these important things about chemomouthpiece.com
Visit chemomouthpiece.comWe analyzed Chemomouthpiece.com page load time and found that the first response time was 101 ms and then it took 3.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
chemomouthpiece.com performance score
name
value
score
weighting
Value2.1 s
82/100
10%
Value10.7 s
0/100
25%
Value5.3 s
58/100
10%
Value830 ms
35/100
30%
Value0.662
8/100
15%
Value13.5 s
11/100
10%
101 ms
100 ms
124 ms
22 ms
160 ms
Our browser made a total of 101 requests to load all elements on the main page. We found that 42% of them (42 requests) were addressed to the original Chemomouthpiece.com, 20% (20 requests) were made to Fonts.gstatic.com and 13% (13 requests) were made to D.adroll.com. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Chemomouthpiece.com.
Page size can be reduced by 76.0 kB (5%)
1.6 MB
1.5 MB
In fact, the total size of Chemomouthpiece.com main page is 1.6 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. 65% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 70.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 70.0 kB or 76% of the original size.
Potential reduce by 4.4 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. Chemo Mouthpiece images are well optimized though.
Potential reduce by 820 B
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 742 B
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. Chemomouthpiece.com has all CSS files already compressed.
Number of requests can be reduced by 49 (79%)
62
13
The browser has sent 62 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Chemo Mouthpiece. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 30 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
chemomouthpiece.com
101 ms
gtm.js
100 ms
hotjar-1263707.js
124 ms
style.min.css
22 ms
blocks.style.build.css
160 ms
wc-blocks-vendors-style.css
138 ms
wc-blocks-style.css
181 ms
woocommerce-layout.css
169 ms
woocommerce.css
33 ms
et-divi-dynamic-2297-late.css
41 ms
et-divi-dynamic-2297.css
147 ms
style.css
221 ms
landing.css
165 ms
jquery-2.2.4.min.js
294 ms
scripts.js
304 ms
et-divi-customizer-global.min.css
273 ms
3ccdf5bf40d64c8ab339a317f8f33e00.js.ubembed.com
112 ms
email-decode.min.js
167 ms
jquery.blockUI.min.js
350 ms
add-to-cart.min.js
189 ms
js.cookie.min.js
351 ms
woocommerce.min.js
353 ms
cart-fragments.min.js
396 ms
scripts.min.js
460 ms
new-tab.js
432 ms
common.js
443 ms
lazysizes.min.js
395 ms
ls.unveilhooks.min.js
432 ms
ls.native-loading.min.js
503 ms
wp_footer.js
502 ms
roundtrip.js
27 ms
insight.min.js
57 ms
modules.84f80a92c39bbd76564a.js
37 ms
insight.old.min.js
6 ms
DXA35WZSBRBFNISXIJXHAY
17 ms
logo.png
194 ms
intro-chemo-mouthpiece-new.png
230 ms
product-1.png
366 ms
product-4.png
329 ms
product-2.png
430 ms
before-after.png
339 ms
bundle.js
53 ms
PODONLHH7ZGLPA3A6VKHAM.js
275 ms
fbevents.js
44 ms
hinted-OpenSans-Regular.woff
252 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVQ.woff
73 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVc.ttf
76 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVQ.woff
88 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVc.ttf
90 ms
hinted-OpenSans-SemiBold.woff
283 ms
font
88 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVc.ttf
90 ms
hinted-OpenSans-Bold.woff
379 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVQ.woff
89 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVc.ttf
90 ms
hinted-OpenSans-ExtraBold.woff
384 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4uaVQ.woff
96 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4uaVc.ttf
100 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkyFjWV4exg.woff
100 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkyFjWV4exQ.ttf
100 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk0ZjWV4exg.woff
100 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk0ZjWV4exQ.ttf
99 ms
font
103 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkxhjWV4exQ.ttf
106 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkWV4exg.woff
106 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkWV4exQ.ttf
106 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk5hkWV4exg.woff
105 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk5hkWV4exQ.ttf
107 ms
hinted-BrandonText-Bold.woff
357 ms
hinted-BrandonText-Black.woff
379 ms
et-divi-dynamic-2297-late.css
392 ms
out
7 ms
sendrolling.js
6 ms
out
12 ms
out
21 ms
out
19 ms
out
14 ms
out
19 ms
out
18 ms
out
21 ms
out
35 ms
out
35 ms
out
35 ms
pixel
98 ms
Pug
97 ms
tap.php
96 ms
pixel
145 ms
xuid
119 ms
sync
134 ms
tracking.js
94 ms
chemomouthpiece.com
1858 ms
analytics.js
60 ms
in
35 ms
rum
75 ms
sd
71 ms
bounce
58 ms
collect
19 ms
collect
32 ms
js
82 ms
ga-audiences
35 ms
woocommerce-smallscreen.css
11 ms
chemomouthpiece.com accessibility score
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.
chemomouthpiece.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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
chemomouthpiece.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 Chemomouthpiece.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 Chemomouthpiece.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.
chemomouthpiece.com
Open Graph description is not detected on the main page of Chemo Mouthpiece. 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: