10.1 sec in total
1.7 sec
7.6 sec
891 ms
Click here to check amazing Easychart content. Otherwise, check out these important facts you probably never knew about easychart.co.za
Stick-on whiteboard solutions for presentations, brain-storming sessions and meet-ups on-the-go - movable, reusable and more cost-efficient than paper.
Visit easychart.co.zaWe analyzed Easychart.co.za page load time and found that the first response time was 1.7 sec and then it took 8.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
easychart.co.za performance score
name
value
score
weighting
Value8.5 s
0/100
10%
Value10.0 s
0/100
25%
Value24.0 s
0/100
10%
Value1,530 ms
13/100
30%
Value0.194
63/100
15%
Value20.1 s
2/100
10%
1662 ms
527 ms
552 ms
598 ms
577 ms
Our browser made a total of 116 requests to load all elements on the main page. We found that 66% of them (77 requests) were addressed to the original Easychart.co.za, 11% (13 requests) were made to Maps.googleapis.com and 7% (8 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (3.7 sec) belongs to the original domain Easychart.co.za.
Page size can be reduced by 1.4 MB (47%)
3.0 MB
1.6 MB
In fact, the total size of Easychart.co.za main page is 3.0 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. Javascripts take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 66.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. 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 66.4 kB or 83% of the original size.
Potential reduce by 48.5 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. Easychart images are well optimized though.
Potential reduce by 996.8 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 996.8 kB or 70% of the original size.
Potential reduce by 311.0 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. Easychart.co.za needs all CSS files to be minified and compressed as it can save up to 311.0 kB or 86% of the original size.
Number of requests can be reduced by 70 (65%)
107
37
The browser has sent 107 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Easychart. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 53 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.
easychart.co.za
1662 ms
wp-emoji-release.min.js
527 ms
styles.css
552 ms
settings.css
598 ms
prettyPhoto.css
577 ms
bootstrap.css
603 ms
plugin.css
610 ms
fonts.css
794 ms
style.css
1098 ms
responsive.css
859 ms
animate.css
878 ms
woocommerce.css
872 ms
easychart.co.za
1375 ms
jquery.js
1706 ms
jquery-migrate.min.js
1184 ms
jquery.themepunch.plugins.min.js
1429 ms
jquery.themepunch.revolution.min.js
1435 ms
fastclick.js
1393 ms
postlike.js
1493 ms
jquery.form.min.js
1646 ms
scripts.js
1661 ms
jquery.prettyPhoto.min.js
1799 ms
jquery.prettyPhoto.init.min.js
1814 ms
jquery.blockUI.min.js
1817 ms
woocommerce.min.js
1978 ms
jquery.cookie.min.js
1979 ms
cart-fragments.min.js
1996 ms
comment-reply.min.js
2035 ms
mediaelement-and-player.min.js
2376 ms
wp-mediaelement.js
2068 ms
masonry.min.js
2278 ms
easing.js
2283 ms
superfish.js
2418 ms
mmenu.js
2417 ms
caroufredsel.js
2479 ms
isotope.js
2260 ms
countto.js
2167 ms
flexslider.js
2151 ms
donutchart.js
2145 ms
magnificpopup.js
2125 ms
tweet.js
2272 ms
bootstrap.js
2267 ms
wow.js
2142 ms
waypoints.js
2113 ms
parallax.js
2352 ms
functions.js
2131 ms
affix.js
2268 ms
css
28 ms
wp-embed.min.js
2126 ms
single-product.min.js
2026 ms
css
16 ms
underscore.min.js
1905 ms
wp-util.min.js
1899 ms
add-to-cart-variation.min.js
1991 ms
back.jpg
2600 ms
logo.png
1955 ms
transparent.png
1954 ms
easychart1.png
3196 ms
embed
226 ms
erase.jpg
2326 ms
tape1.jpg
2133 ms
easy.jpg
2543 ms
BVtM30trf7q_jfqYeHfjtA.woff
81 ms
wkfQbvfT_02e2IWO3yYueQ.woff
81 ms
9k-RPmcnxYEPm8CNFsH2gg.woff
108 ms
KT3KS9Aol4WfR6Vas8kNcg.woff
109 ms
fontawesome-webfont.woff
2281 ms
trash1.jpg
2505 ms
single.png
2677 ms
board-150x150.png
2406 ms
js
96 ms
init_embed.js
69 ms
step1.png
2707 ms
step21.png
2678 ms
common.js
89 ms
map.js
90 ms
google4.png
24 ms
overlay.js
21 ms
util.js
150 ms
onion.js
106 ms
search_impl.js
148 ms
StaticMapService.GetMapImage
202 ms
step31.png
2469 ms
step41.png
2468 ms
stats.js
151 ms
openhand_8_8.cur
136 ms
ViewportInfoService.GetViewportInfo
82 ms
ViewportInfoService.GetViewportInfo
76 ms
kh
296 ms
kh
292 ms
step51.png
2526 ms
transparent.png
173 ms
step61.png
2602 ms
magic.png
3660 ms
controls.js
124 ms
css
116 ms
entity11.png
78 ms
vt
85 ms
vt
111 ms
vt
107 ms
vt
109 ms
vt
100 ms
mapcnt6.png
40 ms
tmapctrl.png
33 ms
2UX7WLTfW3W8TclTUvlFyQ.woff
43 ms
RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff
44 ms
Hgo13k-tfSpn0qi1SFdUfT8E0i7KZn-EPnyo3HZu7kw.woff
52 ms
d-6IYplOFocCacKzxwXSOD8E0i7KZn-EPnyo3HZu7kw.woff
51 ms
AuthenticationService.Authenticate
33 ms
loader.gif
1419 ms
small_left.png
1418 ms
small_right.png
1535 ms
ajax-loader.gif
1532 ms
debut_light.png
1602 ms
tweed.png
1643 ms
binding_dark.png
1668 ms
easychart.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
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.
easychart.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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
easychart.co.za SEO score
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Easychart.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 Easychart.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.
easychart.co.za
Open Graph description is not detected on the main page of Easychart. 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: