2.3 sec in total
348 ms
1.7 sec
277 ms
Visit why-fi.co.za now to see the best up-to-date Why Fi content and also check out these interesting facts you probably never knew about why-fi.co.za
Visit why-fi.co.zaWe analyzed Why-fi.co.za page load time and found that the first response time was 348 ms and then it took 2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
why-fi.co.za performance score
348 ms
83 ms
77 ms
50 ms
57 ms
Our browser made a total of 67 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Why-fi.co.za, 49% (33 requests) were made to Static.parastorage.com and 18% (12 requests) were made to Static.wixstatic.com. The less responsive or slowest element that took the longest time to load (456 ms) relates to the external source Static.wixstatic.com.
Page size can be reduced by 2.5 MB (57%)
4.3 MB
1.9 MB
In fact, the total size of Why-fi.co.za main page is 4.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. 75% 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. Javascripts take 2.7 MB which makes up the majority of the site volume.
Potential reduce by 83.1 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 83.1 kB or 84% of the original size.
Potential reduce by 96.4 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. Why Fi images are well optimized though.
Potential reduce by 2.0 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 2.0 MB or 75% of the original size.
Potential reduce by 246.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. Why-fi.co.za needs all CSS files to be minified and compressed as it can save up to 246.7 kB or 83% of the original size.
Number of requests can be reduced by 41 (71%)
58
17
The browser has sent 58 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Why Fi. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 31 to 1 for JavaScripts and as a result speed up the page load time.
why-fi.co.za
348 ms
www.why-fi.com
83 ms
bt
77 ms
require.min.js
50 ms
main-r.min.js
57 ms
viewer.css
72 ms
dynamicmodel
30 ms
a33bb7_03e92805fc74df2f152b961e6795cf0a_143.json.z
453 ms
a33bb7_87943ebfc9c152f50e0cb5c36505dcc0_143.json.z
456 ms
ugc-viewer
77 ms
bt
98 ms
skins.min.js
92 ms
components.min.js
31 ms
utils.min.js
70 ms
core.min.js
76 ms
react-with-addons.min.js
74 ms
lodash.min.js
68 ms
TweenMax.min.js
70 ms
layout.min.js
74 ms
tpa.min.js
73 ms
fonts.min.js
76 ms
animations.min.js
76 ms
swfobject.min.js
75 ms
mousetrap.min.js
74 ms
tweenEngine.min.js
77 ms
DrawSVGPlugin.min.js
79 ms
react-dom.min.js
78 ms
ScrollToPlugin.min.js
78 ms
widgets.min.js
77 ms
experiment.js
76 ms
render.min.js
433 ms
wixappsCore.min.js
80 ms
wixappsBuilder.min.js
79 ms
zepto.min.js
77 ms
color.min.js
76 ms
react-dom-server.min.js
25 ms
bt
170 ms
latin.css
29 ms
dc.js
235 ms
bt
226 ms
a33bb7_f40a5910fa69076d7661fc15fdf0ab8e.png
339 ms
arrows_white_new3.png
86 ms
a33bb7_5c1ef09d5dc8b65c80608ad79ead6b1f.png
314 ms
a33bb7_dfd9b8b95410318b875e8849102b808e.png
361 ms
a33bb7_10d96602b4cd97db366b088162992ab5.jpg
309 ms
a33bb7_3ac43fa204b09afd969d52d13882a35e.jpg
301 ms
8d2c2a4846503b9067e2fd2f590445c2.wix_mp
79 ms
fe7017590fbd384c7502a64601c7b444.png
89 ms
b67d062dc57b4fbce6342c776b8becb0.wix_mp
272 ms
84770f_27ec0b2e3a30c423c76ad738cca20de3.jpg
233 ms
bt
42 ms
bt
41 ms
bt
88 ms
YvQZ1rQTt5s
136 ms
4cefdf47-0136-4169-9933-3225dbbec9d9.woff
31 ms
opensans-bold-webfont.woff
37 ms
opensans-regular-webfont.woff
68 ms
__utm.gif
15 ms
ga-audiences
68 ms
www-embed-player-vflfNyN_r.css
49 ms
www-embed-player.js
66 ms
fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js
9 ms
ad_status.js
55 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
44 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
46 ms
ugc-viewer
35 ms
84770f_27ec0b2e3a30c423c76ad738cca20de3.jpg
7 ms
why-fi.co.za SEO score
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Why-fi.co.za can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Why-fi.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.
why-fi.co.za
Open Graph description is not detected on the main page of Why Fi. 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: