6.3 sec in total
1.7 sec
4.5 sec
110 ms
Welcome to smallfire.co.nz homepage info - get ready to check Smallfire best content right away, or after learning these important things about smallfire.co.nz
Visit smallfire.co.nzWe analyzed Smallfire.co.nz page load time and found that the first response time was 1.7 sec and then it took 4.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
smallfire.co.nz performance score
name
value
score
weighting
Value6.5 s
2/100
10%
Value6.5 s
9/100
25%
Value11.5 s
5/100
10%
Value290 ms
79/100
30%
Value0.068
96/100
15%
Value13.1 s
12/100
10%
1704 ms
374 ms
412 ms
619 ms
414 ms
Our browser made a total of 41 requests to load all elements on the main page. We found that 51% of them (21 requests) were addressed to the original Smallfire.co.nz, 27% (11 requests) were made to Platform.twitter.com and 7% (3 requests) were made to Static.addtoany.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Smallfire.co.nz.
Page size can be reduced by 307.7 kB (54%)
568.8 kB
261.1 kB
In fact, the total size of Smallfire.co.nz main page is 568.8 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. 30% of websites need less resources to load. Javascripts take 215.5 kB which makes up the majority of the site volume.
Potential reduce by 17.4 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 17.4 kB or 74% of the original size.
Potential reduce by 29.0 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. Obviously, Smallfire needs image optimization as it can save up to 29.0 kB or 17% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 127.2 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 127.2 kB or 59% of the original size.
Potential reduce by 134.1 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. Smallfire.co.nz needs all CSS files to be minified and compressed as it can save up to 134.1 kB or 83% of the original size.
Number of requests can be reduced by 28 (78%)
36
8
The browser has sent 36 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Smallfire. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 22 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
www.smallfire.co.nz
1704 ms
wp-emoji-release.min.js
374 ms
widget.css
412 ms
style.min.css
619 ms
styles.css
414 ms
css
16 ms
athemes-symbols.css
415 ms
bootstrap.min.css
1025 ms
style.css
580 ms
addtoany.min.css
622 ms
jquery.js
1030 ms
jquery-migrate.min.js
623 ms
addtoany.min.js
787 ms
bootstrap.min.js
827 ms
hoverIntent.js
827 ms
superfish.js
832 ms
settings.js
993 ms
page.js
35 ms
widgets.js
95 ms
scripts.js
916 ms
wp-embed.min.js
915 ms
Smallfire1.png
207 ms
Enablingparticipation-640x250.png
412 ms
sm.25.html
29 ms
eso.Ep5bSEmr.js
34 ms
TK3_WkUHHAIjg75cFRf3bXL8LICs1_FvsUZiYA.ttf
30 ms
TK3_WkUHHAIjg75cFRf3bXL8LICs169vsUZiYA.ttf
30 ms
TK3_WkUHHAIjg75cFRf3bXL8LICs1xZosUZiYA.ttf
31 ms
afonts.woff
208 ms
widget_iframe.2f70fb173b9000da126c79afe2098f02.html
58 ms
settings
75 ms
timeline.e108540dddc96e4b707f5cf259a582d7.js
22 ms
pennyhagen
68 ms
polyfills-3b821eda8863adcc4a4b.js
22 ms
runtime-a697c5a1ae32bd7e4d42.js
47 ms
modules.20f98d7498a59035a762.js
72 ms
main-fd9ef5eb169057cda26d.js
92 ms
_app-88bf420a57d49e33be53.js
91 ms
%5BscreenName%5D-c33f0b02841cffc3e9b4.js
90 ms
_buildManifest.js
94 ms
_ssgManifest.js
93 ms
smallfire.co.nz 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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
smallfire.co.nz 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
smallfire.co.nz 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
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 Smallfire.co.nz 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 Smallfire.co.nz 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.
smallfire.co.nz
Open Graph description is not detected on the main page of Smallfire. 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: