16.7 sec in total
2.6 sec
13.5 sec
586 ms
Visit screentime.co.za now to see the best up-to-date Screentime content and also check out these interesting facts you probably never knew about screentime.co.za
Just another WordPress site
Visit screentime.co.zaWe analyzed Screentime.co.za page load time and found that the first response time was 2.6 sec and then it took 14 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
screentime.co.za performance score
name
value
score
weighting
Value6.9 s
1/100
10%
Value8.3 s
2/100
25%
Value34.4 s
0/100
10%
Value4,420 ms
0/100
30%
Value0.649
9/100
15%
Value32.6 s
0/100
10%
2623 ms
27 ms
1961 ms
1144 ms
1615 ms
Our browser made a total of 111 requests to load all elements on the main page. We found that 68% of them (76 requests) were addressed to the original Screentime.co.za, 8% (9 requests) were made to Youtube.com and 8% (9 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (6.8 sec) belongs to the original domain Screentime.co.za.
Page size can be reduced by 255.3 kB (8%)
3.4 MB
3.1 MB
In fact, the total size of Screentime.co.za main page is 3.4 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.3 MB which makes up the majority of the site volume.
Potential reduce by 137.5 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 137.5 kB or 82% of the original size.
Potential reduce by 102.0 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. Screentime images are well optimized though.
Potential reduce by 4.5 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. This website has mostly compressed JavaScripts.
Potential reduce by 11.3 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. Screentime.co.za has all CSS files already compressed.
Number of requests can be reduced by 57 (59%)
97
40
The browser has sent 97 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Screentime. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 40 to 1 for JavaScripts and from 19 to 1 for CSS and as a result speed up the page load time.
www.screentime.co.za
2623 ms
styles.css
27 ms
be.css
1961 ms
animations.min.css
1144 ms
fontawesome.css
1615 ms
jplayer.blue.monday.css
1183 ms
responsive.css
1556 ms
css
99 ms
js_composer.min.css
40 ms
animate.min.css
96 ms
pum-site-styles.css
104 ms
basic.min.css
124 ms
theme-ie11.min.css
132 ms
theme.min.css
142 ms
jquery.min.js
146 ms
jquery-migrate.min.js
153 ms
jquery.json.min.js
162 ms
gravityforms.min.js
174 ms
iframe_api
114 ms
email-decode.min.js
173 ms
css
83 ms
vc_carousel.min.css
181 ms
trustindex-facebook-widget.css
190 ms
rs6.css
202 ms
index.js
211 ms
index.js
221 ms
page-scroll-to-id.min.js
232 ms
rbtools.min.js
238 ms
rs6.min.js
255 ms
core.min.js
264 ms
tabs.min.js
272 ms
plugins.js
290 ms
menu.js
299 ms
animations.min.js
306 ms
jplayer.min.js
317 ms
translate3d.js
338 ms
scripts.js
349 ms
js_composer_front.min.js
360 ms
vc-waypoints.min.js
370 ms
iframe_api
135 ms
loader.js
82 ms
pum-site-scripts.js
379 ms
wp-polyfill-inert.min.js
385 ms
regenerator-runtime.min.js
351 ms
wp-polyfill.min.js
328 ms
css
20 ms
dom-ready.min.js
329 ms
hooks.min.js
315 ms
i18n.min.js
321 ms
a11y.min.js
318 ms
placeholders.jquery.min.js
318 ms
transition.min.js
319 ms
vc_carousel.min.js
319 ms
sound-on.svg
213 ms
sound-off.svg
1401 ms
logo.svg
1403 ms
screentime-logo.png
1399 ms
dummy.png
1403 ms
brand-strategy.svg
1404 ms
e-commerce.svg
217 ms
digital-marketing.svg
267 ms
web-app.svg
473 ms
amc-fabrications.png
927 ms
gogo-dineo-ndlanzi-institute.png
980 ms
mmpm.png
982 ms
bms-capital.png
2460 ms
42-lifestyle.png
2302 ms
afrika-ikalafe.png
2677 ms
tseba-tanks.png
2612 ms
the-accounting-village.png
2686 ms
tiger-wheel-tyre.png
2666 ms
sello-maake-kancube-foundation.png
3823 ms
v-insighters.png
3985 ms
cookies.png
3777 ms
picture
980 ms
picture
473 ms
picture
472 ms
pxiByp8kv8JHgFVrLEj6Z1xlEw.woff
457 ms
pxiByp8kv8JHgFVrLCz7Z1xlEw.woff
905 ms
pxiByp8kv8JHgFVrLGT9Z1xlEw.woff
963 ms
pxiEyp8kv8JHgFVrJJfedA.woff
962 ms
pxiByp8kv8JHgFVrLDz8Z1xlEw.woff
961 ms
www-widgetapi.js
195 ms
gogo-dineo.jpg
4655 ms
aurum-innova.png
4929 ms
tseba-tanks.png
5830 ms
afrika-ikalafe.png
6300 ms
the-accounting-village.png
6827 ms
umthombocs.png
3956 ms
lets-chat.svg
3965 ms
icons.woff
5757 ms
f.svg
310 ms
icon.svg
713 ms
recommendation-positive.svg
709 ms
QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K67QBi8JoA.woff
762 ms
KFOmCnqEu92Fr1Mu4mxM.woff
761 ms
305566400_468865945260384_681953888545703890_n.png
716 ms
3mKWngKizT4
266 ms
www-player.css
34 ms
www-embed-player.js
81 ms
base.js
154 ms
ad_status.js
233 ms
QIgJXlTW_ocH5BKR4VvT459F7KnrK51w4wqraUAmDYI.js
118 ms
embed.js
38 ms
AIdro_miwMro4-C5pF69Arqu5pxE_piZnOT59gqF9JJO=s68-c-k-c0x00ffffff-no-rj
398 ms
id
33 ms
KFOmCnqEu92Fr1Mu4mxM.woff
32 ms
KFOlCnqEu92Fr1MmEU9fBBc-.woff
33 ms
Create
129 ms
GenerateIT
13 ms
log_event
18 ms
screentime.co.za accessibility score
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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Links do not have a discernible name
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
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.
screentime.co.za best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
screentime.co.za 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
Image elements do not have [alt] attributes
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 Screentime.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 Screentime.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.
screentime.co.za
Open Graph description is not detected on the main page of Screentime. 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: