3.1 sec in total
105 ms
2.5 sec
476 ms
Welcome to split-fire.com homepage info - get ready to check Split Fire best content right away, or after learning these important things about split-fire.com
35 Years of Manufacturing The Best North American Built 2-Way Log Splitters, Wood Chippers & 3 Point Hitch Buckets.
Visit split-fire.comWe analyzed Split-fire.com page load time and found that the first response time was 105 ms and then it took 3 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
split-fire.com performance score
name
value
score
weighting
Value4.1 s
22/100
10%
Value11.2 s
0/100
25%
Value9.0 s
14/100
10%
Value600 ms
50/100
30%
Value0.167
71/100
15%
Value12.6 s
14/100
10%
105 ms
17 ms
79 ms
89 ms
87 ms
Our browser made a total of 138 requests to load all elements on the main page. We found that 85% of them (117 requests) were addressed to the original Split-fire.com, 4% (5 requests) were made to Googletagmanager.com and 2% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Split-fire.com.
Page size can be reduced by 293.3 kB (20%)
1.4 MB
1.2 MB
In fact, the total size of Split-fire.com main page is 1.4 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 459.9 kB which makes up the majority of the site volume.
Potential reduce by 276.1 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 276.1 kB or 87% of the original size.
Potential reduce by 6.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. Split Fire images are well optimized though.
Potential reduce by 8.5 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. This website has mostly compressed JavaScripts.
Potential reduce by 2.8 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. Split-fire.com has all CSS files already compressed.
Number of requests can be reduced by 101 (79%)
128
27
The browser has sent 128 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Split Fire. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 65 to 1 for JavaScripts and from 38 to 1 for CSS and as a result speed up the page load time.
split-fire.com
105 ms
wp-emoji-release.min.js
17 ms
premium-addons.min.css
79 ms
style.min.css
89 ms
wc-blocks-vendors-style.css
87 ms
wc-blocks-style.css
31 ms
frontend.css
27 ms
badges.css
41 ms
classic-themes.min.css
92 ms
advanced-flat-rate-shipping-for-woocommerce-public.css
48 ms
font-awesome.min.css
110 ms
frontend.css
55 ms
svgs-attachment.css
65 ms
woocommerce-layout.css
74 ms
woocommerce.css
92 ms
rplg.css
139 ms
swiper.min.css
138 ms
dashicons.min.css
144 ms
all.min.css
143 ms
style.css
98 ms
photoswipe.min.css
105 ms
default-skin.min.css
173 ms
sv-wc-payment-gateway-payment-form.min.css
114 ms
pum-site-styles.css
121 ms
frontend-lite.min.css
135 ms
post-57338.css
294 ms
nucleus.css
140 ms
orion_home.css
203 ms
wordpress.css
201 ms
orion-wordpress_home.css
149 ms
smartslider.min.css
156 ms
jquery.min.js
165 ms
jquery-migrate.min.js
174 ms
advanced-flat-rate-shipping-for-woocommerce-public.js
229 ms
Checkout.js
151 ms
js
35 ms
js
58 ms
wp-polyfill-inert.min.js
176 ms
elementor-icons.min.css
175 ms
swiper.min.css
182 ms
post-22321.css
231 ms
frontend-lite.min.css
224 ms
animations.min.css
191 ms
regenerator-runtime.min.js
169 ms
wp-polyfill.min.js
167 ms
hooks.min.js
166 ms
frontend.js
246 ms
wpac-time.js
212 ms
blazy.min.js
158 ms
swiper.min.js
162 ms
rplg.js
169 ms
script.js
177 ms
jquery.payment.min.js
235 ms
sv-wc-payment-gateway-payment-form.js
191 ms
wc-elavon-payment-form.min.js
169 ms
smush-lazy-load.min.js
167 ms
css
31 ms
n2.min.js
168 ms
smartslider-frontend.min.js
197 ms
ss-carousel.min.js
303 ms
w-arrow-image.min.js
305 ms
email-decode.min.js
191 ms
frontend.js
300 ms
colcade.js
296 ms
jquery.blockUI.min.js
179 ms
js.cookie.min.js
173 ms
woocommerce.min.js
164 ms
cart-fragments.min.js
263 ms
script2.js
270 ms
custom-validation2.js
252 ms
photoswipe.min.js
240 ms
photoswipe-ui-default.min.js
236 ms
core.min.js
236 ms
css
12 ms
css
22 ms
pum-site-scripts.js
227 ms
frontend-min.js
230 ms
hoverIntent.min.js
272 ms
maxmegamenu.js
266 ms
public.js
259 ms
main.js
214 ms
webpack-pro.runtime.min.js
258 ms
webpack.runtime.min.js
205 ms
frontend-modules.min.js
198 ms
i18n.min.js
236 ms
frontend.min.js
185 ms
waypoints.min.js
184 ms
swiper.min.js
184 ms
share-link.min.js
215 ms
dialog.min.js
208 ms
frontend.min.js
200 ms
preloaded-elements-handlers.min.js
215 ms
preloaded-modules.min.js
198 ms
jquery.sticky.min.js
337 ms
underscore.min.js
331 ms
wp-util.min.js
330 ms
frontend.min.js
178 ms
gtm.js
94 ms
gr
293 ms
call-split-fire.jpg
280 ms
email-split-fire.jpg
276 ms
Allan-Strickland-Minden-La.jpg
318 ms
Frank-Montani-Cape-Cod-MA.jpg
340 ms
Brent-McCloskey-Jamestown-PA.jpg
339 ms
logan-craig-review.jpg
339 ms
Mark-Brault-Vermont-1.jpg
338 ms
review-2265.jpg
337 ms
Mark-Brault-Vermont-2.jpg
338 ms
Ray-Forbes-Winnipeg-MB.jpg
375 ms
Steven-Webster-Truro-NS.jpg
396 ms
Dave-Norrie.jpg
394 ms
js
103 ms
js
197 ms
analytics.js
192 ms
P5sfzZCDf9_T_3cV7NCUECyoxNk37cxcABrE.ttf
232 ms
TK3_WkUHHAIjg75cFRf3bXL8LICs1_FvsUZiYA.ttf
345 ms
TK3_WkUHHAIjg75cFRf3bXL8LICs13FvsUZiYA.ttf
231 ms
TK3_WkUHHAIjg75cFRf3bXL8LICs1xZosUZiYA.ttf
345 ms
wARDj0u
22 ms
us.png
259 ms
183 ms
ca.png
178 ms
Split-Fire-log-splitters-sm.jpg
157 ms
Get-Splitting-Banner-V2.jpg
220 ms
smush-lazyloader-1.gif
219 ms
collect
63 ms
split-fire.com
1458 ms
TK3_WkUHHAIjg75cFRf3bXL8LICs18NvsUZiYA.ttf
51 ms
TK3_WkUHHAIjg75cFRf3bXL8LICs169vsUZiYA.ttf
66 ms
TK3_WkUHHAIjg75cFRf3bXL8LICs13FvsUZiYA.ttf
50 ms
TK3_WkUHHAIjg75cFRf3bXL8LICs1y9osUZiYA.ttf
41 ms
collect
41 ms
52 ms
ga-audiences
16 ms
log-splitter-split-fire-fpm.jpg
65 ms
wood-chipper-fpm.jpg
66 ms
3-point-carry-all-fpm.jpg
69 ms
woocommerce-smallscreen.css
62 ms
split-fire.com 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
Image elements do not have [alt] attributes
split-fire.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
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
split-fire.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 Split-fire.com 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 Split-fire.com 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.
split-fire.com
Open Graph data is detected on the main page of Split Fire. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: