6.7 sec in total
830 ms
5.3 sec
622 ms
Visit smallfish.com.au now to see the best up-to-date Small Fish content and also check out these interesting facts you probably never knew about smallfish.com.au
Business coaching for tradies and builders - learn the structure and systems to grow your business properly and increase your profits. Download our workbook and enrol in our business coaching program.
Visit smallfish.com.auWe analyzed Smallfish.com.au page load time and found that the first response time was 830 ms and then it took 5.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
smallfish.com.au performance score
name
value
score
weighting
Value5.6 s
5/100
10%
Value20.4 s
0/100
25%
Value17.4 s
0/100
10%
Value2,480 ms
4/100
30%
Value0.681
8/100
15%
Value25.2 s
0/100
10%
830 ms
319 ms
1109 ms
97 ms
54 ms
Our browser made a total of 136 requests to load all elements on the main page. We found that 49% of them (66 requests) were addressed to the original Smallfish.com.au, 18% (24 requests) were made to Fonts.gstatic.com and 5% (7 requests) were made to B2158431.smushcdn.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Smallfish.com.au.
Page size can be reduced by 495.0 kB (30%)
1.7 MB
1.2 MB
In fact, the total size of Smallfish.com.au main page is 1.7 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. Only a small number of websites need less resources to load. Javascripts take 695.3 kB which makes up the majority of the site volume.
Potential reduce by 293.7 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 293.7 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. Small Fish images are well optimized though.
Potential reduce by 201.4 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 201.4 kB or 29% of the original size.
Potential reduce by 0 B
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. Smallfish.com.au has all CSS files already compressed.
Number of requests can be reduced by 86 (83%)
103
17
The browser has sent 103 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Small Fish. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 52 to 1 for JavaScripts and from 36 to 1 for CSS and as a result speed up the page load time.
smallfish.com.au
830 ms
smallfish.com.au
319 ms
www.smallfish.com.au
1109 ms
widget.js
97 ms
bootstrap.min.css
54 ms
google-review.css
76 ms
prettyPhoto.css
69 ms
wp-video-lightbox.css
76 ms
projects-map.css
78 ms
posts-list.css
76 ms
style.min.css
103 ms
general.css
110 ms
pagination.css
102 ms
post-cards.css
108 ms
gallery.css
109 ms
testimonials-all.css
118 ms
testimonial-block.css
128 ms
location.css
134 ms
category-block.css
143 ms
tags-block.css
160 ms
before-after.css
142 ms
content-block.css
145 ms
for-masonry.css
150 ms
for-album.css
171 ms
cover.css
173 ms
map-popup.css
172 ms
main-filters.css
178 ms
ai-writeups.css
180 ms
front.min.css
187 ms
all.css
206 ms
magnific-popup.css
202 ms
lightgallery.min.css
216 ms
style.css
210 ms
all.min.css
81 ms
jquery.fancybox.min.css
84 ms
grid-style.css
205 ms
responsive-style.css
216 ms
style.css
231 ms
wpac-time.js
239 ms
jquery.min.js
241 ms
jquery-migrate.min.js
228 ms
jquery.fancybox.min.js
88 ms
js
126 ms
js
186 ms
js
167 ms
tracking.js
85 ms
opf.js
86 ms
genbootstrap.php
199 ms
184848.js
101 ms
js
165 ms
jquery.prettyPhoto.js
249 ms
video-lightbox.js
207 ms
front.min.js
202 ms
site-app.js
205 ms
custom-script.js
200 ms
hooks.min.js
272 ms
i18n.min.js
271 ms
for_blocks.js
247 ms
masonry.pkgd.min.js
296 ms
map.js
293 ms
underscore.min.js
292 ms
wp-util.min.js
292 ms
lightgallery-all.min.js
284 ms
jquery.magnific-popup.min.js
271 ms
for-masonry.js
372 ms
backbone.min.js
363 ms
api-request.min.js
361 ms
wp-api.min.js
360 ms
front-ui.js
355 ms
scripts.min.js
346 ms
jquery.fitvids.js
393 ms
common.js
394 ms
smush-lazy-load.min.js
393 ms
rplg.js
386 ms
fbevents.js
158 ms
hotjar-343501.js
283 ms
gtm.js
155 ms
1SFBC-logo-_-Hi-Res-colored-fish-on-white-background.png
401 ms
KFOmCnqEu92Fr1Mu7GxM.woff
102 ms
KFOmCnqEu92Fr1Mu7GxP.ttf
161 ms
KFOlCnqEu92Fr1MmEU9fChc-.woff
272 ms
KFOlCnqEu92Fr1MmEU9fChc9.ttf
274 ms
KFOlCnqEu92Fr1MmSU5fChc-.woff
274 ms
KFOlCnqEu92Fr1MmSU5fChc9.ttf
274 ms
KFOkCnqEu92Fr1MmgVxGIzQ.woff
275 ms
KFOkCnqEu92Fr1MmgVxGIzc.ttf
274 ms
KFOlCnqEu92Fr1MmWUlfChc-.woff
272 ms
KFOlCnqEu92Fr1MmWUlfChc9.ttf
276 ms
KFOlCnqEu92Fr1MmYUtfChc-.woff
277 ms
KFOlCnqEu92Fr1MmYUtfChc9.ttf
276 ms
modules.woff
270 ms
KFOkCnqEu92Fr1Mu51xGIzQ.woff
244 ms
KFOkCnqEu92Fr1Mu51xGIzc.ttf
243 ms
KFOjCnqEu92Fr1Mu51S7ACc0CsI.woff
243 ms
KFOjCnqEu92Fr1Mu51S7ACc0CsE.ttf
245 ms
KFOjCnqEu92Fr1Mu51TjASc0CsI.woff
245 ms
KFOjCnqEu92Fr1Mu51TjASc0CsE.ttf
245 ms
KFOiCnqEu92Fr1Mu51QrEz4dKQ.woff
246 ms
KFOiCnqEu92Fr1Mu51QrEz4dKg.ttf
246 ms
KFOjCnqEu92Fr1Mu51TzBic0CsI.woff
309 ms
KFOjCnqEu92Fr1Mu51TzBic0CsE.ttf
248 ms
KFOjCnqEu92Fr1Mu51TLBCc0CsI.woff
247 ms
KFOjCnqEu92Fr1Mu51TLBCc0CsE.ttf
247 ms
genjs-v3.php
285 ms
fa-brands-400.woff
177 ms
fa-brands-400.woff
1097 ms
analytics.js
246 ms
212 ms
2019-03-13-Small-Fish-Coaching-Homepage_09.png
155 ms
2019-03-13-Small-Fish-Coaching-Homepage_13.png
215 ms
2019-03-13-Small-Fish-Coaching-Homepage_11.png
213 ms
SF-hp1.jpg
296 ms
workshop-1-scaled.jpg
337 ms
1
327 ms
188 ms
moonrayform.paymentplandisplay.css
13 ms
form.default.min.css
21 ms
gencss.php
103 ms
genjs-v3.php
192 ms
jquery.min.js
17 ms
jquery-ui.min.js
6 ms
20 ms
moonrayform.paymentplandisplay.js
22 ms
KNP_4290-scaled.jpg
224 ms
track.php
109 ms
track.php
213 ms
1SFBC-logo-_-Hi-Res-colored-fish-on-white-background.png
32 ms
a8hixXZyyNE
90 ms
www-player.css
8 ms
www-embed-player.js
25 ms
base.js
51 ms
ad_status.js
159 ms
FoEX-quY0t7i9F3zTEBnQn49aOPZkPAqcwwf5YitGsc.js
108 ms
embed.js
37 ms
id
20 ms
Create
3 ms
smallfish.com.au 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
<frame> or <iframe> elements do not have a title
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.
smallfish.com.au 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
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
smallfish.com.au 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
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 Smallfish.com.au 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 Smallfish.com.au 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.
smallfish.com.au
Open Graph data is detected on the main page of Small Fish. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: