12.3 sec in total
3.2 sec
8.6 sec
472 ms
Welcome to ohwhite.com homepage info - get ready to check Oh White best content right away, or after learning these important things about ohwhite.com
Tooth whitening cosmetic products to help recover the natural white shade of the tooth enamel. | Teeth Whitening Specialists
Visit ohwhite.comWe analyzed Ohwhite.com page load time and found that the first response time was 3.2 sec and then it took 9.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
ohwhite.com performance score
name
value
score
weighting
Value10.5 s
0/100
10%
Value21.1 s
0/100
25%
Value22.3 s
0/100
10%
Value1,830 ms
9/100
30%
Value0.796
5/100
15%
Value19.8 s
2/100
10%
3217 ms
172 ms
387 ms
193 ms
295 ms
Our browser made a total of 65 requests to load all elements on the main page. We found that 58% of them (38 requests) were addressed to the original Ohwhite.com, 34% (22 requests) were made to Fonts.gstatic.com and 3% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (3.2 sec) belongs to the original domain Ohwhite.com.
Page size can be reduced by 1.9 MB (20%)
9.8 MB
7.9 MB
In fact, the total size of Ohwhite.com main page is 9.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. 65% of websites need less resources to load. Images take 7.9 MB which makes up the majority of the site volume.
Potential reduce by 111.9 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 111.9 kB or 86% of the original size.
Potential reduce by 365.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. Oh White images are well optimized though.
Potential reduce by 589.0 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 589.0 kB or 72% of the original size.
Potential reduce by 858.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. Ohwhite.com needs all CSS files to be minified and compressed as it can save up to 858.5 kB or 86% of the original size.
Number of requests can be reduced by 19 (48%)
40
21
The browser has sent 40 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Oh White. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 10 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
www.ohwhite.com
3217 ms
wp-emoji-release.min.js
172 ms
style.min.css
387 ms
cookie-law-info-public.css
193 ms
cookie-law-info-gdpr.css
295 ms
dashicons.min.css
390 ms
wpmi.css
200 ms
style.css
900 ms
themify-icons.min.css
381 ms
dflip.min.css
400 ms
css
29 ms
jquery.js
587 ms
cookie-law-info-public.js
570 ms
api.js
37 ms
es6-promise.auto.min.js
482 ms
recaptcha.js
485 ms
et-divi-customizer-global-17205129701649.min.css
499 ms
css
18 ms
custom.unified.js
989 ms
dflip.min.js
813 ms
common.js
531 ms
wp-embed.min.js
596 ms
Flag_of_Europe.svg
361 ms
logo1.png
642 ms
Banner-Kit_EN2.jpg
1042 ms
bannercolux2.jpg
1036 ms
bannerfoam2.jpg
1033 ms
whitemintcajatubo.jpg
938 ms
backmintcajatubo.jpg
1041 ms
bannerkitpro.jpg
1116 ms
bannerlampara.jpg
1136 ms
Whitening-Light-kit-Imagen-para-colocar-la-ferula-encendida.jpg
2484 ms
subscribe-loader.gif
346 ms
fondo_footer.jpg
1151 ms
favicon.png
1151 ms
KFOmCnqEu92Fr1Me5g.woff
245 ms
KFOlCnqEu92Fr1MmEU9vAA.woff
246 ms
KFOlCnqEu92Fr1MmSU5vAA.woff
259 ms
KFOkCnqEu92Fr1MmgWxM.woff
258 ms
KFOlCnqEu92Fr1MmWUlvAA.woff
246 ms
KFOlCnqEu92Fr1MmYUtvAA.woff
258 ms
modules.ttf
446 ms
XRXI3I6Li01BKofiOc5wtlZ2di8HDGUmRTA.woff
247 ms
XRXI3I6Li01BKofiOc5wtlZ2di8HDFwmRTA.woff
246 ms
XRXI3I6Li01BKofiOc5wtlZ2di8HDDsmRTA.woff
258 ms
XRXI3I6Li01BKofiOc5wtlZ2di8HDBImRTA.woff
259 ms
XRXI3I6Li01BKofiOc5wtlZ2di8HDLshRTA.woff
253 ms
XRXI3I6Li01BKofiOc5wtlZ2di8HDOUhRTA.woff
254 ms
XRXI3I6Li01BKofiOc5wtlZ2di8HDDshRTA.woff
259 ms
wARDj0u
2 ms
carr1_1_2.jpg
807 ms
carr1-1.jpg
869 ms
chicamovil.jpg
920 ms
carr1-3.jpg
1009 ms
carr2-1.jpg
1020 ms
carr3-1.jpg
1013 ms
XRXI3I6Li01BKofiOc5wtlZ2di8HDIkhRTA.woff
60 ms
XRXK3I6Li01BKofIMPyPbj8d7IEAGXNin3A3iQ.woff
68 ms
XRXK3I6Li01BKofIMPyPbj8d7IEAGXNirXA3iQ.woff
68 ms
XRXK3I6Li01BKofIMPyPbj8d7IEAGXNi83A3iQ.woff
67 ms
XRXK3I6Li01BKofIMPyPbj8d7IEAGXNiLXA3iQ.woff
60 ms
XRXK3I6Li01BKofIMPyPbj8d7IEAGXNic3c3iQ.woff
69 ms
XRXK3I6Li01BKofIMPyPbj8d7IEAGXNiSnc3iQ.woff
113 ms
XRXK3I6Li01BKofIMPyPbj8d7IEAGXNiLXc3iQ.woff
92 ms
XRXK3I6Li01BKofIMPyPbj8d7IEAGXNiBHc3iQ.woff
93 ms
ohwhite.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 IDs are not unique
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.
ohwhite.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
Page has valid source maps
ohwhite.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 Ohwhite.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 Ohwhite.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.
ohwhite.com
Open Graph data is detected on the main page of Oh White. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: