11.9 sec in total
1.2 sec
10.5 sec
163 ms
Click here to check amazing Sparkle White content. Otherwise, check out these important facts you probably never knew about sparklewhite.co.nz
Here at Sparklewhite, we give all your teeth extra sparkle! Our procedure is very safe, completely painless as gums are protected with gum barrier . . .
Visit sparklewhite.co.nzWe analyzed Sparklewhite.co.nz page load time and found that the first response time was 1.2 sec and then it took 10.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
sparklewhite.co.nz performance score
name
value
score
weighting
Value3.5 s
35/100
10%
Value33.4 s
0/100
25%
Value19.7 s
0/100
10%
Value2,150 ms
6/100
30%
Value0.02
100/100
15%
Value21.5 s
1/100
10%
1237 ms
422 ms
441 ms
599 ms
415 ms
Our browser made a total of 84 requests to load all elements on the main page. We found that 81% of them (68 requests) were addressed to the original Sparklewhite.co.nz, 8% (7 requests) were made to Fonts.gstatic.com and 4% (3 requests) were made to S.ytimg.com. The less responsive or slowest element that took the longest time to load (5.4 sec) belongs to the original domain Sparklewhite.co.nz.
Page size can be reduced by 1.9 MB (39%)
4.7 MB
2.9 MB
In fact, the total size of Sparklewhite.co.nz 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 2.7 MB which makes up the majority of the site volume.
Potential reduce by 50.4 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. This page needs HTML code to be minified as it can gain 6.0 kB, which is 11% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 50.4 kB or 91% of the original size.
Potential reduce by 194.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. Sparkle White images are well optimized though.
Potential reduce by 911.7 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 911.7 kB or 78% of the original size.
Potential reduce by 715.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. Sparklewhite.co.nz needs all CSS files to be minified and compressed as it can save up to 715.5 kB or 85% of the original size.
Number of requests can be reduced by 34 (51%)
67
33
The browser has sent 67 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Sparkle 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 17 to 1 for JavaScripts and from 19 to 1 for CSS and as a result speed up the page load time.
sparklewhite.co.nz
1237 ms
bootstrap.css
422 ms
responsive.css
441 ms
style.css
599 ms
MyMedia.css
415 ms
animate.css
437 ms
bootstrap-tabs.css
435 ms
bxslider.css
585 ms
revolution-slider.css
588 ms
jackbox.css
636 ms
jackbox_hovers.css
635 ms
css
42 ms
jquery-ui.css
629 ms
SIHftHl2i4M&feature=youtu.be
113 ms
pinit.js
1195 ms
addthis_widget.js
2303 ms
jquery.js
975 ms
jquery-ui-1.9.2.custom.js
1589 ms
jquery.bxslider.js
848 ms
appear.js
848 ms
styleswitcher.js
1040 ms
colorpicker.js
1041 ms
retina.js
1167 ms
bootstrap.js
1235 ms
script.js
1238 ms
jquery.themepunch.plugins.min.js
1366 ms
jquery.themepunch.revolution.min.js
1578 ms
jquery.cycle2.js
1431 ms
jquery-ui.js
29 ms
logo21.png
1621 ms
untitled1.png
1555 ms
nztc1.png
2003 ms
ban1.jpg
2508 ms
bannermain.jpg
2909 ms
banner3.jpg
2351 ms
service.png
2581 ms
smile.png
2768 ms
service2.jpg
2678 ms
Before-60min-Sparklewhite-treatment.jpg
2543 ms
P1220171.jpg
3080 ms
LsKyems4m_c
92 ms
www-embed-player-vflfNyN_r.css
22 ms
www-embed-player.js
44 ms
base.js
74 ms
fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js
27 ms
ad_status.js
96 ms
CrYjSnGjrRCn0pd9VQsnFOvvDin1pK8aKteLpeZ5c0A.woff
81 ms
RxZJdnzeo3R5zSexge8UUbO3LdcAZYWl9Si6vvxL-qU.woff
82 ms
P2030208.jpg
2514 ms
P4210403.jpg
2551 ms
P8131179.jpg
3020 ms
Sia-17Dec14-Before-1hr-Tx-v2-.jpg
2726 ms
unnamed.gif
2673 ms
After-60min-Sparklewhite-treatment.jpg
2552 ms
P1220176.jpg
2775 ms
font-awesome.css
2678 ms
styleswitcher.css
2672 ms
colorpicker.css
2693 ms
colors-style.css
2722 ms
owl.carousel.css
2630 ms
jquery.fancybox-1.3.4.css
2644 ms
P2030213.jpg
2736 ms
P4210405.jpg
2695 ms
P8131180.jpg
2701 ms
Sia-17Dec14-After-1hr-Tx-v2..jpg
2666 ms
unnamed-1.gif
2476 ms
img-pay.png
2454 ms
DXI1ORHCpsQm3Vp6mXoaTaRDOzjiPcYnFooOUGCOsRk.woff
37 ms
cJZKeOuBrn4kERxqtaUH3bO3LdcAZYWl9Si6vvxL-qU.woff
37 ms
MTP_ySUJH_bn48VBG8sNSqRDOzjiPcYnFooOUGCOsRk.woff
38 ms
k3k702ZOKiLJc3WVjuplzKRDOzjiPcYnFooOUGCOsRk.woff
36 ms
EInbV5DfGHOiMmvb1Xr-hqRDOzjiPcYnFooOUGCOsRk.woff
37 ms
fontawesome-webfontba72.woff
334 ms
superfish.js
910 ms
jquery.mobilemenu.js
4205 ms
jquery.easing.1.3.js
5231 ms
jquery.cookie.js
5301 ms
jquery.tipsy.js
5329 ms
jquery.tweet.js
5446 ms
loader2.gif
194 ms
timer.png
199 ms
pag.png
196 ms
layer-prev.png
196 ms
layer-next.png
197 ms
sparklewhite.co.nz 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.
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.
sparklewhite.co.nz 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
sparklewhite.co.nz 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
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 Sparklewhite.co.nz 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 Sparklewhite.co.nz 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.
sparklewhite.co.nz
Open Graph description is not detected on the main page of Sparkle White. 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: