7.9 sec in total
746 ms
6.3 sec
906 ms
Click here to check amazing Frogfoot content for South Africa. Otherwise, check out these important facts you probably never knew about frogfoot.net
Frogfoot Networks is a leading open access Fibre infrastructure provider, enabling businesses and homes in South Africa to live, work & connect with ease.
Visit frogfoot.netWe analyzed Frogfoot.net page load time and found that the first response time was 746 ms and then it took 7.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
frogfoot.net performance score
name
value
score
weighting
Value2.9 s
52/100
10%
Value3.6 s
60/100
25%
Value10.0 s
9/100
10%
Value360 ms
72/100
30%
Value0.274
44/100
15%
Value16.4 s
5/100
10%
746 ms
2087 ms
335 ms
494 ms
494 ms
Our browser made a total of 57 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Frogfoot.net, 65% (37 requests) were made to Frogfoot.co.za and 7% (4 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (2.1 sec) relates to the external source Frogfoot.co.za.
Page size can be reduced by 54.6 kB (12%)
444.7 kB
390.1 kB
In fact, the total size of Frogfoot.net main page is 444.7 kB. 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. Images take 353.9 kB which makes up the majority of the site volume.
Potential reduce by 37.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 37.5 kB or 78% of the original size.
Potential reduce by 16.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. Frogfoot images are well optimized though.
Potential reduce by 149 B
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.
Number of requests can be reduced by 22 (45%)
49
27
The browser has sent 49 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Frogfoot. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 23 to 1 for JavaScripts and as a result speed up the page load time.
frogfoot.net
746 ms
www.frogfoot.co.za
2087 ms
js
335 ms
9028.js
494 ms
gtm.js
494 ms
wp-emoji-release.min.js
363 ms
jquery.min.js
929 ms
jquery-migrate.min.js
1176 ms
solid-wordpress.js
1132 ms
navigation.js
1132 ms
jquery-1.12.4.js
1404 ms
bootstrap.js
1206 ms
bootstrap-select.js
1135 ms
skip-link-focus-fix.js
1303 ms
selectize.min.js
298 ms
cavalry.js
1296 ms
lazyload.min.js
1295 ms
login-icon.png
1310 ms
550da9460d9e5083141bc14f8c918749.css
1816 ms
lato-regular-webfont.woff
1705 ms
Roboto-Regular.woff
1987 ms
js
60 ms
analytics.js
449 ms
www.frogfoot.co.za.json
543 ms
conversion_async.js
467 ms
fbevents.js
341 ms
js
212 ms
collect
318 ms
collect
259 ms
a18bb0e21d11a839b7adb013c92ee611.js
259 ms
218131352248156
117 ms
collect
214 ms
117 ms
www.frogfoot.co.za.json
63 ms
share-icon-white.png
334 ms
Frogfoot-logo_Blue.png
343 ms
MicrosoftTeams-image-104.png
691 ms
4521.png
896 ms
MicrosoftTeams-image-29.png
2015 ms
scroll-icon.png
691 ms
home-page-block.jpg
965 ms
air-logo.jpg
755 ms
frog-smart.png
853 ms
logo-white.png
854 ms
Facebook-Icon.png
971 ms
Twitter-Icon.png
1079 ms
youtube.png
1077 ms
Instagram.png
1113 ms
footer-frog.png
1183 ms
footer-frog-mobile.png
1193 ms
223 ms
ga-audiences
194 ms
frog-eyes.png
615 ms
lato-black-webfont.woff
763 ms
Roboto-Black.woff
800 ms
lato-light-webfont.woff
652 ms
Roboto-Light.woff
897 ms
frogfoot.net accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
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.
frogfoot.net 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
Browser errors were logged to the console
Page has valid source maps
frogfoot.net SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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 Frogfoot.net 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 Frogfoot.net 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.
frogfoot.net
Open Graph data is detected on the main page of Frogfoot. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: