14.3 sec in total
3.4 sec
10.3 sec
514 ms
Welcome to pixelcandy.co.za homepage info - get ready to check Pixel Candy best content right away, or after learning these important things about pixelcandy.co.za
Potchefstroom Website Design & Hosting Company. Prices that simply can\'t be matched. We can design the website of your dreams, and host it at the best
Visit pixelcandy.co.zaWe analyzed Pixelcandy.co.za page load time and found that the first response time was 3.4 sec and then it took 10.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
pixelcandy.co.za performance score
name
value
score
weighting
Value4.4 s
16/100
10%
Value4.4 s
39/100
25%
Value9.8 s
10/100
10%
Value90 ms
99/100
30%
Value0.342
33/100
15%
Value5.0 s
77/100
10%
3416 ms
522 ms
539 ms
21 ms
546 ms
Our browser made a total of 108 requests to load all elements on the main page. We found that 66% of them (71 requests) were addressed to the original Pixelcandy.co.za, 15% (16 requests) were made to Fonts.gstatic.com and 7% (8 requests) were made to Scontent-iad3-1.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (3.4 sec) belongs to the original domain Pixelcandy.co.za.
Page size can be reduced by 3.0 MB (60%)
5.1 MB
2.0 MB
In fact, the total size of Pixelcandy.co.za main page is 5.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. CSS take 2.0 MB which makes up the majority of the site volume.
Potential reduce by 60.8 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 60.8 kB or 84% of the original size.
Potential reduce by 48.9 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. Pixel Candy images are well optimized though.
Potential reduce by 1.2 MB
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 1.2 MB or 73% of the original size.
Potential reduce by 1.8 MB
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. Pixelcandy.co.za needs all CSS files to be minified and compressed as it can save up to 1.8 MB or 89% of the original size.
Number of requests can be reduced by 52 (59%)
88
36
The browser has sent 88 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pixel Candy. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 33 to 1 for JavaScripts and from 21 to 1 for CSS and as a result speed up the page load time.
www.pixelcandy.co.za
3416 ms
wp-emoji-release.min.js
522 ms
layerslider.css
539 ms
css
21 ms
styles.css
546 ms
style.css
542 ms
stylesheet.min.css
1374 ms
print.css
756 ms
blog.min.css
781 ms
style_dynamic.css
1056 ms
font-awesome.min.css
802 ms
style.min.css
846 ms
ionicons.min.css
1017 ms
style.css
1040 ms
simple-line-icons.css
1064 ms
dripicons.css
1105 ms
responsive.min.css
1540 ms
style_dynamic_responsive.css
1300 ms
js_composer.min.css
1834 ms
custom_css.css
1324 ms
webkit_stylesheet.css
1365 ms
css
44 ms
greensock.js
1738 ms
jquery.js
2026 ms
jquery-migrate.min.js
1543 ms
layerslider.kreaturamedia.jquery.js
1550 ms
layerslider.transitions.js
1719 ms
jquery.form.min.js
1700 ms
scripts.js
1701 ms
eltd-like.js
1836 ms
plugins.js
2649 ms
jquery.carouFredSel-6.2.1.js
1867 ms
jquery.fullPage.min.js
2012 ms
lemmon-slider.js
2013 ms
jquery.mousewheel.min.js
2192 ms
jquery.touchSwipe.min.js
2193 ms
isotope.pkgd.min.js
2191 ms
typed.js
2238 ms
js
116 ms
default_dynamic.js
2237 ms
default.min.js
2534 ms
blog.min.js
2136 ms
custom_js.js
2132 ms
TweenLite.min.js
2154 ms
ScrollToPlugin.min.js
1942 ms
smoothPageScroll.js
2269 ms
comment-reply.min.js
2251 ms
ajax.min.js
2207 ms
js_composer_front.min.js
2035 ms
wp-embed.min.js
2128 ms
analytics.js
148 ms
pixel-candy-2015-dark-full.png
1104 ms
pixel-candy-2015-white-full.png
1105 ms
web-dev-bg.jpg
2406 ms
pixel-candy-icon-e1453641711393.png
1104 ms
tabs-parallax.jpg
1412 ms
servers-slide.jpg
1554 ms
crown.png
1349 ms
chubby-chick-1.png
1409 ms
auto-den.png
1666 ms
agreenco-bioenergy.png
1619 ms
eurasian.png
1684 ms
bic-safaris.png
1688 ms
circle.png
1831 ms
crafty-cottage.png
1883 ms
hs-heilbron.png
1926 ms
pk-sedation.png
1962 ms
cts-brokers.png
1982 ms
preload_pattern.png
305 ms
footer-background-image.jpg
421 ms
60-60.png
2031 ms
www.pixelcandy.co.za
3281 ms
Xyjz-jNkfiYuJf8UC3Lizw.woff
166 ms
oOeFwZNlrTefzLYmlVV1UD8E0i7KZn-EPnyo3HZu7kw.woff
166 ms
Pru33qjShpZSmG3z6VYwnT8E0i7KZn-EPnyo3HZu7kw.woff
166 ms
idLYXfFa1c7oAPILDl4z0fesZW2xOQ-xsNqO47m55DA.woff
165 ms
97uahxiqZRoncBaCEI3aWz8E0i7KZn-EPnyo3HZu7kw.woff
165 ms
9_7S_tWeGDh5Pq3u05RVkj8E0i7KZn-EPnyo3HZu7kw.woff
167 ms
ElegantIcons.woff
2639 ms
WmVKXVcOuffP_qmCpFuyzRsxEYwM7FgeyaSgU71cLG0.woff
167 ms
QoPu455RxV2raYSIFXAMBRsxEYwM7FgeyaSgU71cLG0.woff
167 ms
Ji5epXNcpHu3r63lhS0cThsxEYwM7FgeyaSgU71cLG0.woff
166 ms
STBOO2waD2LpX45SXYjQBRsxEYwM7FgeyaSgU71cLG0.woff
166 ms
Li18TEFObx_yGdzKDoI_chsxEYwM7FgeyaSgU71cLG0.woff
166 ms
vQbQAx9WlNOTTgpOnfyPXQ.woff
211 ms
ZKwULyCG95tk6mOqHQfRBBsxEYwM7FgeyaSgU71cLG0.woff
210 ms
cbAbzEjxTdN5KKmS-gA0tRsxEYwM7FgeyaSgU71cLG0.woff
209 ms
rr0ijB5_2nAJsAoZ6vECXT8E0i7KZn-EPnyo3HZu7kw.woff
210 ms
likebox.php
399 ms
O_D1NAZVOFOobLbVtW3bcha1RVmPjeKy21_GQJaLlJI.woff
153 ms
collect
138 ms
Simple-Line-Icons.woff
2276 ms
fontawesome-webfont.woff
2037 ms
YrFakaCOmcf.css
22 ms
BWRIL9-XbYW.js
35 ms
JrFVMrRpAYB.js
71 ms
T-D_V7C7Ph6.js
70 ms
575323_347129082007778_1949359635_n.jpg
52 ms
72922_347129422007744_874213080_n.jpg
42 ms
10616217_10203495477441124_859663613252690841_n.jpg
236 ms
8362_10156804475785711_7185007944403633642_n.jpg
24 ms
14657269_1293940973970982_9003056651449052989_n.jpg
212 ms
20729435_473825739658738_5293180566424929371_n.jpg
23 ms
16003114_1229928813768548_6728618611778055749_n.jpg
235 ms
21106587_347592209012443_8688818676834614373_n.jpg
236 ms
wMkwmq5_RAN.png
16 ms
parallax-layers-1.jpg
1312 ms
logo.png
1481 ms
pixelcandy.co.za 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.
pixelcandy.co.za 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
Browser errors were logged to the console
Issues were logged in the Issues panel in Chrome Devtools
pixelcandy.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 Pixelcandy.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 Pixelcandy.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.
pixelcandy.co.za
Open Graph description is not detected on the main page of Pixel Candy. 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: