8.5 sec in total
426 ms
7.8 sec
289 ms
Click here to check amazing Sparkle content for South Africa. Otherwise, check out these important facts you probably never knew about sparkle.co.za
Sparkle Products is focused on providing high quality products at affordable, competitive prices.
Visit sparkle.co.zaWe analyzed Sparkle.co.za page load time and found that the first response time was 426 ms and then it took 8.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.
sparkle.co.za performance score
name
value
score
weighting
Value15.7 s
0/100
10%
Value27.2 s
0/100
25%
Value24.4 s
0/100
10%
Value480 ms
60/100
30%
Value0.008
100/100
15%
Value25.9 s
0/100
10%
426 ms
1834 ms
607 ms
35 ms
865 ms
Our browser made a total of 83 requests to load all elements on the main page. We found that 73% of them (61 requests) were addressed to the original Sparkle.co.za, 20% (17 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2.5 sec) belongs to the original domain Sparkle.co.za.
Page size can be reduced by 752.2 kB (56%)
1.3 MB
586.0 kB
In fact, the total size of Sparkle.co.za main page is 1.3 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. CSS take 594.8 kB which makes up the majority of the site volume.
Potential reduce by 51.3 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 51.3 kB or 77% of the original size.
Potential reduce by 904 B
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 images are well optimized though.
Potential reduce by 167.3 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 167.3 kB or 60% of the original size.
Potential reduce by 532.7 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. Sparkle.co.za needs all CSS files to be minified and compressed as it can save up to 532.7 kB or 90% of the original size.
Number of requests can be reduced by 43 (68%)
63
20
The browser has sent 63 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Sparkle. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 25 to 1 for JavaScripts and from 20 to 1 for CSS and as a result speed up the page load time.
sparkle.co.za
426 ms
www.sparkle.co.za
1834 ms
wp-emoji-release.min.js
607 ms
css
35 ms
style.min.css
865 ms
style.css
1036 ms
styles.css
624 ms
settings.css
838 ms
woocommerce-layout.css
828 ms
woocommerce.css
844 ms
frontend.css
834 ms
grid.css
1039 ms
icons.css
1455 ms
woocommerce.css
1050 ms
js_composer.min.css
2509 ms
style.css
1496 ms
animations.css
1245 ms
grid_responsive.css
1248 ms
css
29 ms
jquery.js
1471 ms
jquery-migrate.min.js
1456 ms
jquery.themepunch.tools.min.js
1870 ms
jquery.themepunch.revolution.min.js
1871 ms
jquery.blockUI.min.js
1666 ms
add-to-cart.min.js
1683 ms
woocommerce-add-to-cart.js
1706 ms
libs.min.js
2299 ms
common.js
1896 ms
js
63 ms
background-style.css
1713 ms
animate.css
2090 ms
style.css
1881 ms
scripts.js
1908 ms
js.cookie.min.js
1926 ms
woocommerce.min.js
2092 ms
cart-fragments.min.js
2126 ms
jquery.prettyPhoto.min.js
2140 ms
frontend.min.js
2387 ms
wp-embed.min.js
2389 ms
js_composer_front.min.js
2388 ms
ultimate_bg.js
2389 ms
jparallax.js
2175 ms
jquery.vhparallax.js
2137 ms
jquery.appear.js
1932 ms
custom.js
1930 ms
logo.jpg
281 ms
slider-img.jpg
283 ms
slider-content.png
280 ms
toilet-frash-combo-1-300x300.jpg
341 ms
odorex-spray-300x300.jpg
343 ms
dishwashing-combo-300x300.jpg
379 ms
wearhouse-pic2.jpg
517 ms
logo-transparent.png
494 ms
212047514.png
492 ms
embed
226 ms
footer-bg.jpg
474 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0C4n.ttf
121 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0C4n.ttf
130 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1y4n.ttf
131 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1y4n.ttf
132 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1y4n.ttf
129 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX8.ttf
127 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf
130 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf
132 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf
150 ms
icomoon.svg
818 ms
icomoon.woff
653 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkaVc.ttf
152 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk5hkaVc.ttf
151 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkxhjaVc.ttf
151 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkyFjaVc.ttf
153 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk0ZjaVc.ttf
153 ms
S6u9w4BMUTPHh7USSwiPHA.ttf
150 ms
S6uyw4BMUTPHjx4wWw.ttf
153 ms
S6u9w4BMUTPHh6UVSwiPHA.ttf
153 ms
www.sparkle.co.za
1113 ms
revolution.extension.slideanims.min.js
437 ms
revolution.extension.layeranimation.min.js
443 ms
revolution.extension.parallax.min.js
458 ms
icon_plus.png
644 ms
ajax-loader.gif
650 ms
js
60 ms
woocommerce-smallscreen.css
214 ms
sparkle.co.za 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
<frame> or <iframe> elements do not have a title
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.
sparkle.co.za 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
sparkle.co.za 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 Sparkle.co.za 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 Sparkle.co.za 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.
sparkle.co.za
Open Graph data is detected on the main page of Sparkle. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: