6.4 sec in total
1.2 sec
4.6 sec
681 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 1.2 sec and then it took 5.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
smallfish.com.au performance score
name
value
score
weighting
Value5.5 s
6/100
10%
Value15.5 s
0/100
25%
Value14.9 s
1/100
10%
Value5,330 ms
0/100
30%
Value0.041
99/100
15%
Value24.7 s
0/100
10%
1152 ms
930 ms
85 ms
160 ms
72 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.2 sec) belongs to the original domain Smallfish.com.au.
Page size can be reduced by 445.3 kB (35%)
1.3 MB
843.3 kB
In fact, the total size of Smallfish.com.au main page is 1.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. 80% 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 507.5 kB which makes up the majority of the site volume.
Potential reduce by 297.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 297.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 146.0 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 146.0 kB or 36% of the original size.
Potential reduce by 1.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. Smallfish.com.au has all CSS files already compressed.
Number of requests can be reduced by 87 (82%)
106
19
The browser has sent 106 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 53 to 1 for JavaScripts and from 36 to 1 for CSS and as a result speed up the page load time.
smallfish.com.au
1152 ms
smallfish.com.au
930 ms
www.smallfish.com.au
85 ms
widget.js
160 ms
bootstrap.min.css
72 ms
google-review.css
88 ms
prettyPhoto.css
259 ms
wp-video-lightbox.css
104 ms
projects-map.css
260 ms
posts-list.css
262 ms
style.min.css
139 ms
general.css
150 ms
pagination.css
189 ms
post-cards.css
208 ms
gallery.css
186 ms
testimonials-all.css
233 ms
testimonial-block.css
246 ms
location.css
290 ms
category-block.css
283 ms
tags-block.css
295 ms
before-after.css
303 ms
content-block.css
328 ms
for-masonry.css
320 ms
for-album.css
323 ms
cover.css
365 ms
map-popup.css
358 ms
main-filters.css
337 ms
ai-writeups.css
352 ms
all.css
372 ms
magnific-popup.css
400 ms
lightgallery.min.css
401 ms
style.css
408 ms
all.min.css
99 ms
jquery.fancybox.min.css
104 ms
grid-style.css
414 ms
responsive-style.css
415 ms
style.css
401 ms
wpac-time.js
439 ms
jquery.min.js
425 ms
jquery-migrate.min.js
467 ms
jquery.prettyPhoto.js
434 ms
jquery.fancybox.min.js
98 ms
js
129 ms
js
204 ms
js
178 ms
tracking.js
105 ms
opf.js
111 ms
genbootstrap.php
460 ms
184848.js
94 ms
js
125 ms
video-lightbox.js
454 ms
site-app.js
422 ms
custom-script.js
394 ms
wp-polyfill-inert.min.js
380 ms
regenerator-runtime.min.js
500 ms
wp-polyfill.min.js
560 ms
hooks.min.js
460 ms
i18n.min.js
522 ms
for_blocks.js
440 ms
masonry.pkgd.min.js
476 ms
map.js
461 ms
underscore.min.js
452 ms
wp-util.min.js
451 ms
lightgallery-all.min.js
687 ms
jquery.magnific-popup.min.js
664 ms
for-masonry.js
657 ms
backbone.min.js
648 ms
api-request.min.js
642 ms
wp-api.min.js
622 ms
front-ui.js
686 ms
scripts.min.js
684 ms
jquery.fitvids.js
672 ms
common.js
657 ms
smush-lazy-load.min.js
649 ms
rplg.js
643 ms
fbevents.js
204 ms
hotjar-343501.js
502 ms
gtm.js
199 ms
default
436 ms
349 ms
KFOmCnqEu92Fr1Mu7GxM.woff
430 ms
KFOmCnqEu92Fr1Mu7GxP.ttf
744 ms
KFOlCnqEu92Fr1MmEU9fChc-.woff
730 ms
KFOlCnqEu92Fr1MmEU9fChc9.ttf
743 ms
KFOlCnqEu92Fr1MmSU5fChc-.woff
749 ms
KFOlCnqEu92Fr1MmSU5fChc9.ttf
748 ms
KFOkCnqEu92Fr1MmgVxGIzQ.woff
814 ms
KFOkCnqEu92Fr1MmgVxGIzc.ttf
818 ms
KFOlCnqEu92Fr1MmWUlfChc-.woff
817 ms
KFOlCnqEu92Fr1MmWUlfChc9.ttf
817 ms
KFOlCnqEu92Fr1MmYUtfChc-.woff
874 ms
KFOlCnqEu92Fr1MmYUtfChc9.ttf
874 ms
modules.woff
817 ms
analytics.js
606 ms
230 ms
iframe_api
748 ms
genjs-v3.php
592 ms
KFOkCnqEu92Fr1Mu51xGIzQ.woff
747 ms
KFOkCnqEu92Fr1Mu51xGIzc.ttf
808 ms
KFOjCnqEu92Fr1Mu51S7ACc0CsI.woff
808 ms
KFOjCnqEu92Fr1Mu51S7ACc0CsE.ttf
808 ms
KFOjCnqEu92Fr1Mu51TjASc0CsI.woff
811 ms
KFOjCnqEu92Fr1Mu51TjASc0CsE.ttf
812 ms
KFOiCnqEu92Fr1Mu51QrEz4dKQ.woff
823 ms
KFOiCnqEu92Fr1Mu51QrEz4dKg.ttf
828 ms
KFOjCnqEu92Fr1Mu51TzBic0CsI.woff
827 ms
KFOjCnqEu92Fr1Mu51TzBic0CsE.ttf
827 ms
KFOjCnqEu92Fr1Mu51TLBCc0CsI.woff
828 ms
KFOjCnqEu92Fr1Mu51TLBCc0CsE.ttf
828 ms
fa-brands-400.woff
255 ms
fa-brands-400.woff
1231 ms
modules.f7c079ad889f2e18ab73.js
655 ms
analytics.js
650 ms
231 ms
1SFBC-logo-_-Hi-Res-colored-fish-on-white-background.png
945 ms
2019-03-13-Small-Fish-Coaching-Homepage_09.png
853 ms
2019-03-13-Small-Fish-Coaching-Homepage_13.png
854 ms
2019-03-13-Small-Fish-Coaching-Homepage_11.png
726 ms
SF-hp1.jpg
666 ms
KNP_4290-scaled.jpg
726 ms
workshop-1-scaled.jpg
898 ms
583 ms
585 ms
1
484 ms
collect
161 ms
collect
155 ms
245 ms
www-widgetapi.js
82 ms
collect
82 ms
ga-audiences
15 ms
moonrayform.paymentplandisplay.css
19 ms
form.default.min.css
200 ms
gencss.php
275 ms
genjs-v3.php
298 ms
jquery.min.js
20 ms
load.gif
16 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: