Tools & Wizards About Us
split-fire.com screenshot

Report Summary

  • 29

    Performance

    Renders faster than
    49% of other websites

  • 91

    Accessibility

    Visual factors better than
    that of 76% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

split-fire.com

Log Splitters & Wood Chippers | North American Built

Page Load Speed

2.7 sec in total

First Response

56 ms

Resources Loaded

2.2 sec

Page Rendered

466 ms

split-fire.com screenshot

About Website

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.com

Key Findings

We analyzed Split-fire.com page load time and found that the first response time was 56 ms and then it took 2.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

split-fire.com performance score

29

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

26/100

10%

LCP (Largest Contentful Paint)

Value15.7 s

0/100

25%

SI (Speed Index)

Value9.2 s

13/100

10%

TBT (Total Blocking Time)

Value690 ms

43/100

30%

CLS (Cumulative Layout Shift)

Value0.143

78/100

15%

TTI (Time to Interactive)

Value14.6 s

8/100

10%

Network Requests Diagram

split-fire.com

56 ms

split-fire.com

79 ms

wp-emoji-release.min.js

30 ms

premium-addons.min.css

73 ms

style.min.css

32 ms

Our browser made a total of 133 requests to load all elements on the main page. We found that 89% of them (118 requests) were addressed to the original Split-fire.com, 3% (4 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.4 sec) belongs to the original domain Split-fire.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 292.3 kB (20%)

Content Size

1.5 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Split-fire.com main page is 1.5 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. 75% 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. Javascripts take 488.4 kB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 278.2 kB

  • Original 320.2 kB
  • After minification 320.2 kB
  • After compression 42.0 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 278.2 kB or 87% of the original size.

Image Optimization

-1%

Potential reduce by 3.0 kB

  • Original 453.0 kB
  • After minification 450.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.

JavaScript Optimization

-2%

Potential reduce by 8.4 kB

  • Original 488.4 kB
  • After minification 486.3 kB
  • After compression 480.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. This website has mostly compressed JavaScripts.

CSS Optimization

-1%

Potential reduce by 2.8 kB

  • Original 226.2 kB
  • After minification 224.2 kB
  • After compression 223.5 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.

Requests Breakdown

Number of requests can be reduced by 99 (83%)

Requests Now

120

After Optimization

21

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 120 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 63 to 1 for JavaScripts and from 38 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

split-fire.com

split-fire.com

56 ms

split-fire.com

split-fire.com

79 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

30 ms

premium-addons.min.css

premium-addons.min.css

73 ms

style.min.css

style.min.css

32 ms

wc-blocks-vendors-style.css

wc-blocks-vendors-style.css

84 ms

wc-blocks-style.css

wc-blocks-style.css

84 ms

frontend.css

frontend.css

80 ms

badges.css

badges.css

94 ms

classic-themes.min.css

classic-themes.min.css

43 ms

advanced-flat-rate-shipping-for-woocommerce-public.css

advanced-flat-rate-shipping-for-woocommerce-public.css

101 ms

font-awesome.min.css

font-awesome.min.css

91 ms

frontend.css

frontend.css

126 ms

svgs-attachment.css

svgs-attachment.css

94 ms

woocommerce-layout.css

woocommerce-layout.css

134 ms

woocommerce.css

woocommerce.css

95 ms

rplg.css

rplg.css

99 ms

swiper.min.css

swiper.min.css

98 ms

dashicons.min.css

dashicons.min.css

112 ms

all.min.css

all.min.css

108 ms

style.css

style.css

112 ms

photoswipe.min.css

photoswipe.min.css

167 ms

default-skin.min.css

default-skin.min.css

119 ms

sv-wc-payment-gateway-payment-form.min.css

sv-wc-payment-gateway-payment-form.min.css

118 ms

elementor-icons.min.css

elementor-icons.min.css

169 ms

frontend-lite.min.css

frontend-lite.min.css

172 ms

swiper.min.css

swiper.min.css

188 ms

post-22321.css

post-22321.css

184 ms

frontend-lite.min.css

frontend-lite.min.css

187 ms

pum-site-styles.css

pum-site-styles.css

176 ms

post-57338.css

post-57338.css

181 ms

nucleus.css

nucleus.css

181 ms

orion_home.css

orion_home.css

188 ms

wordpress.css

wordpress.css

239 ms

orion-wordpress_home.css

orion-wordpress_home.css

196 ms

Checkout.js

Checkout.js

43 ms

js

js

89 ms

js

js

109 ms

adsbygoogle.js

adsbygoogle.js

59 ms

js

js

124 ms

smartslider.min.css

smartslider.min.css

190 ms

animations.min.css

animations.min.css

224 ms

jquery.min.js

jquery.min.js

222 ms

jquery-migrate.min.js

jquery-migrate.min.js

211 ms

advanced-flat-rate-shipping-for-woocommerce-public.js

advanced-flat-rate-shipping-for-woocommerce-public.js

189 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

184 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

176 ms

wp-polyfill.min.js

wp-polyfill.min.js

176 ms

hooks.min.js

hooks.min.js

218 ms

frontend.js

frontend.js

173 ms

wpac-time.js

wpac-time.js

182 ms

blazy.min.js

blazy.min.js

217 ms

swiper.min.js

swiper.min.js

221 ms

rplg.js

rplg.js

175 ms

script.js

script.js

175 ms

jquery.payment.min.js

jquery.payment.min.js

174 ms

sv-wc-payment-gateway-payment-form.js

sv-wc-payment-gateway-payment-form.js

175 ms

wc-elavon-payment-form.min.js

wc-elavon-payment-form.min.js

175 ms

smush-lazy-load.min.js

smush-lazy-load.min.js

258 ms

n2.min.js

n2.min.js

284 ms

smartslider-frontend.min.js

smartslider-frontend.min.js

283 ms

ss-carousel.min.js

ss-carousel.min.js

282 ms

w-arrow-image.min.js

w-arrow-image.min.js

274 ms

email-decode.min.js

email-decode.min.js

202 ms

frontend.js

frontend.js

200 ms

colcade.js

colcade.js

320 ms

css

css

32 ms

jquery.blockUI.min.js

jquery.blockUI.min.js

320 ms

js.cookie.min.js

js.cookie.min.js

314 ms

woocommerce.min.js

woocommerce.min.js

219 ms

cart-fragments.min.js

cart-fragments.min.js

219 ms

script2.js

script2.js

305 ms

custom-validation2.js

custom-validation2.js

305 ms

css

css

27 ms

css

css

27 ms

photoswipe.min.js

photoswipe.min.js

336 ms

photoswipe-ui-default.min.js

photoswipe-ui-default.min.js

295 ms

core.min.js

core.min.js

333 ms

pum-site-scripts.js

pum-site-scripts.js

295 ms

frontend-min.js

frontend-min.js

294 ms

hoverIntent.min.js

hoverIntent.min.js

281 ms

maxmegamenu.js

maxmegamenu.js

248 ms

public.js

public.js

272 ms

main.js

main.js

270 ms

webpack-pro.runtime.min.js

webpack-pro.runtime.min.js

303 ms

webpack.runtime.min.js

webpack.runtime.min.js

298 ms

frontend-modules.min.js

frontend-modules.min.js

298 ms

i18n.min.js

i18n.min.js

290 ms

frontend.min.js

frontend.min.js

279 ms

waypoints.min.js

waypoints.min.js

279 ms

swiper.min.js

swiper.min.js

297 ms

share-link.min.js

share-link.min.js

278 ms

dialog.min.js

dialog.min.js

323 ms

frontend.min.js

frontend.min.js

324 ms

preloaded-elements-handlers.min.js

preloaded-elements-handlers.min.js

260 ms

preloaded-modules.min.js

preloaded-modules.min.js

305 ms

jquery.sticky.min.js

jquery.sticky.min.js

250 ms

underscore.min.js

underscore.min.js

261 ms

gtm.js

gtm.js

126 ms

gr

gr

172 ms

wp-util.min.js

wp-util.min.js

184 ms

frontend.min.js

frontend.min.js

194 ms

call-split-fire.jpg

call-split-fire.jpg

1432 ms

email-split-fire.jpg

email-split-fire.jpg

1433 ms

Allan-Strickland-Minden-La.jpg

Allan-Strickland-Minden-La.jpg

298 ms

Frank-Montani-Cape-Cod-MA.jpg

Frank-Montani-Cape-Cod-MA.jpg

298 ms

Brent-McCloskey-Jamestown-PA.jpg

Brent-McCloskey-Jamestown-PA.jpg

310 ms

logan-craig-review.jpg

logan-craig-review.jpg

234 ms

Mark-Brault-Vermont-1.jpg

Mark-Brault-Vermont-1.jpg

262 ms

review-2265.jpg

review-2265.jpg

266 ms

Mark-Brault-Vermont-2.jpg

Mark-Brault-Vermont-2.jpg

292 ms

Ray-Forbes-Winnipeg-MB.jpg

Ray-Forbes-Winnipeg-MB.jpg

308 ms

Steven-Webster-Truro-NS.jpg

Steven-Webster-Truro-NS.jpg

333 ms

Dave-Norrie.jpg

Dave-Norrie.jpg

336 ms

font

font

180 ms

TK3_WkUHHAIjg75cFRf3bXL8LICs1_FvsUZiYA.ttf

TK3_WkUHHAIjg75cFRf3bXL8LICs1_FvsUZiYA.ttf

306 ms

TK3_WkUHHAIjg75cFRf3bXL8LICs18NvsUZiYA.ttf

TK3_WkUHHAIjg75cFRf3bXL8LICs18NvsUZiYA.ttf

344 ms

font

font

234 ms

wARDj0u

wARDj0u

47 ms

TK3_WkUHHAIjg75cFRf3bXL8LICs169vsUZiYA.ttf

TK3_WkUHHAIjg75cFRf3bXL8LICs169vsUZiYA.ttf

324 ms

TK3_WkUHHAIjg75cFRf3bXL8LICs13FvsUZiYA.ttf

TK3_WkUHHAIjg75cFRf3bXL8LICs13FvsUZiYA.ttf

340 ms

TK3_WkUHHAIjg75cFRf3bXL8LICs1y9osUZiYA.ttf

TK3_WkUHHAIjg75cFRf3bXL8LICs1y9osUZiYA.ttf

340 ms

TK3_WkUHHAIjg75cFRf3bXL8LICs1xZosUZiYA.ttf

TK3_WkUHHAIjg75cFRf3bXL8LICs1xZosUZiYA.ttf

344 ms

us.png

us.png

24 ms

Split-Fire-log-splitters-sm.jpg

Split-Fire-log-splitters-sm.jpg

295 ms

Get-Splitting-Banner-V2.jpg

Get-Splitting-Banner-V2.jpg

325 ms

smush-lazyloader-1.gif

smush-lazyloader-1.gif

365 ms

ca.png

ca.png

29 ms

split-fire.com

split-fire.com

1300 ms

log-splitter-split-fire-fpm.jpg

log-splitter-split-fire-fpm.jpg

21 ms

wood-chipper-fpm.jpg

wood-chipper-fpm.jpg

11 ms

3-point-carry-all-fpm.jpg

3-point-carry-all-fpm.jpg

11 ms

woocommerce-smallscreen.css

woocommerce-smallscreen.css

12 ms

Accessibility Review

split-fire.com accessibility score

91

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

High

Image elements do not have [alt] attributes

Best Practices

split-fire.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

split-fire.com SEO score

83

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    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.

Social Sharing Optimization

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: