11.7 sec in total
3 sec
8.5 sec
183 ms
Welcome to floorstep.co.za homepage info - get ready to check Floor Step best content right away, or after learning these important things about floorstep.co.za
Visit floorstep.co.zaWe analyzed Floorstep.co.za page load time and found that the first response time was 3 sec and then it took 8.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
floorstep.co.za performance score
name
value
score
weighting
Value6.4 s
2/100
10%
Value12.8 s
0/100
25%
Value15.7 s
0/100
10%
Value800 ms
36/100
30%
Value1.081
2/100
15%
Value11.7 s
17/100
10%
2969 ms
733 ms
1102 ms
1106 ms
1108 ms
Our browser made a total of 79 requests to load all elements on the main page. We found that 33% of them (26 requests) were addressed to the original Floorstep.co.za, 61% (48 requests) were made to Fonts.gstatic.com and 3% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (3 sec) belongs to the original domain Floorstep.co.za.
Page size can be reduced by 194.7 kB (44%)
439.0 kB
244.3 kB
In fact, the total size of Floorstep.co.za main page is 439.0 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. 85% 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. HTML takes 226.8 kB which makes up the majority of the site volume.
Potential reduce by 192.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 192.5 kB or 85% of the original size.
Potential reduce by 0 B
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. Floor Step images are well optimized though.
Potential reduce by 631 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.
Potential reduce by 1.6 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. Floorstep.co.za needs all CSS files to be minified and compressed as it can save up to 1.6 kB or 13% of the original size.
Number of requests can be reduced by 23 (77%)
30
7
The browser has sent 30 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Floor Step. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
floorstep.co.za
2969 ms
wp_head.css
733 ms
styles.css
1102 ms
custom.css
1106 ms
divi-stop-stacking.css
1108 ms
front.min.css
795 ms
pbe-li.css
796 ms
style.css
1107 ms
js
61 ms
style.min.css
1190 ms
style.min.css
1190 ms
jquery.min.js
1576 ms
jquery-migrate.min.js
1219 ms
scripts.min.js
1956 ms
general.js
1475 ms
call.js
1498 ms
divi-stop-stacking.min.js
1507 ms
smoothscroll.js
1596 ms
jquery.fitvids.js
1843 ms
front.min.js
1868 ms
common.js
1880 ms
wp_footer.js
1999 ms
pbe-li.min.js
1997 ms
fbevents.js
111 ms
Floor-Step-Logo-400x77.png
1098 ms
Floor-Step-Logo-250x48.png
1124 ms
js
69 ms
analytics.js
64 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Ew9.woff
118 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Ew-.ttf
129 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Ew9.woff
145 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Ew-.ttf
153 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Ew9.woff
170 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Ew-.ttf
171 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Ew9.woff
169 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Ew-.ttf
171 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Uw9.woff
152 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Uw-.ttf
178 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu170w9.woff
173 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu170w-.ttf
177 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM70w9.woff
174 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM70w-.ttf
177 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr70w9.woff
176 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr70w-.ttf
177 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC70w9.woff
178 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC70w-.ttf
179 ms
modules.woff
1405 ms
collect
58 ms
Floor-Step-Header-2.jpg
399 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0C4k.woff
20 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0C4n.ttf
16 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0C4k.woff
20 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0C4n.ttf
19 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0C4k.woff
18 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0C4n.ttf
18 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1y4k.woff
26 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1y4n.ttf
26 ms
font
25 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1y4n.ttf
22 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1y4k.woff
25 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1y4n.ttf
25 ms
pxiByp8kv8JHgFVrLGT9V1g.woff
51 ms
pxiByp8kv8JHgFVrLGT9V1s.ttf
52 ms
pxiEyp8kv8JHgFVrFJM.woff
50 ms
pxiEyp8kv8JHgFVrFJA.ttf
52 ms
pxiByp8kv8JHgFVrLDz8V1g.woff
52 ms
pxiByp8kv8JHgFVrLDz8V1s.ttf
49 ms
pxiByp8kv8JHgFVrLFj_V1g.woff
55 ms
pxiByp8kv8JHgFVrLFj_V1s.ttf
54 ms
pxiGyp8kv8JHgFVrLPTedA.woff
52 ms
pxiGyp8kv8JHgFVrLPTedw.ttf
55 ms
pxiByp8kv8JHgFVrLEj6V1g.woff
51 ms
pxiByp8kv8JHgFVrLEj6V1s.ttf
54 ms
pxiByp8kv8JHgFVrLCz7V1g.woff
54 ms
pxiByp8kv8JHgFVrLCz7V1s.ttf
80 ms
pxiByp8kv8JHgFVrLDD4V1g.woff
83 ms
pxiByp8kv8JHgFVrLDD4V1s.ttf
81 ms
pxiByp8kv8JHgFVrLBT5V1g.woff
81 ms
pxiByp8kv8JHgFVrLBT5V1s.ttf
81 ms
floorstep.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.
floorstep.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
floorstep.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 Floorstep.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 Floorstep.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.
floorstep.co.za
Open Graph description is not detected on the main page of Floor Step. 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: