Tools & Wizards About Us
sweetfirejelly.com screenshot

Report Summary

  • 81

    Performance

    Renders faster than
    87% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 62% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

sweetfirejelly.com

Page Load Speed

3.4 sec in total

First Response

737 ms

Resources Loaded

2.3 sec

Page Rendered

306 ms

sweetfirejelly.com screenshot

About Website

Click here to check amazing Sweetfirejelly content. Otherwise, check out these important facts you probably never knew about sweetfirejelly.com

The tastiest pepper jellies in Jalapeno and Habanero flavors!

Visit sweetfirejelly.com

Key Findings

We analyzed Sweetfirejelly.com page load time and found that the first response time was 737 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

sweetfirejelly.com performance score

81

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

47/100

10%

LCP (Largest Contentful Paint)

Value3.3 s

69/100

25%

SI (Speed Index)

Value3.1 s

93/100

10%

TBT (Total Blocking Time)

Value170 ms

93/100

30%

CLS (Cumulative Layout Shift)

Value0.104

89/100

15%

TTI (Time to Interactive)

Value3.8 s

89/100

10%

Network Requests Diagram

www.sweetfirejelly.com

737 ms

wp-emoji-release.min.js

90 ms

css

23 ms

style.css

171 ms

woocommerce-layout.css

86 ms

Our browser made a total of 67 requests to load all elements on the main page. We found that 73% of them (49 requests) were addressed to the original Sweetfirejelly.com, 13% (9 requests) were made to Fonts.gstatic.com and 4% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (737 ms) belongs to the original domain Sweetfirejelly.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 525.5 kB (26%)

Content Size

2.0 MB

After Optimization

1.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Sweetfirejelly.com main page is 2.0 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. 70% of websites need less resources to load. Images take 1.4 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 29.4 kB

  • Original 36.4 kB
  • After minification 34.7 kB
  • After compression 7.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 29.4 kB or 81% of the original size.

Image Optimization

-1%

Potential reduce by 15.5 kB

  • Original 1.4 MB
  • After minification 1.4 MB

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. Sweetfirejelly images are well optimized though.

JavaScript Optimization

-67%

Potential reduce by 163.3 kB

  • Original 243.7 kB
  • After minification 226.3 kB
  • After compression 80.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 163.3 kB or 67% of the original size.

CSS Optimization

-86%

Potential reduce by 317.3 kB

  • Original 368.9 kB
  • After minification 334.9 kB
  • After compression 51.6 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. Sweetfirejelly.com needs all CSS files to be minified and compressed as it can save up to 317.3 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 33 (58%)

Requests Now

57

After Optimization

24

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 57 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Sweetfirejelly. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 15 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

www.sweetfirejelly.com

www.sweetfirejelly.com

737 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

90 ms

css

css

23 ms

style.css

style.css

171 ms

woocommerce-layout.css

woocommerce-layout.css

86 ms

woocommerce.css

woocommerce.css

118 ms

css

css

32 ms

css

css

43 ms

style.css

style.css

122 ms

shortcodes.css

shortcodes.css

129 ms

shortcodes_responsive.css

shortcodes_responsive.css

109 ms

jetpack.css

jetpack.css

176 ms

jquery.fancybox-1.3.4.css

jquery.fancybox-1.3.4.css

138 ms

page_templates.css

page_templates.css

144 ms

jquery.js

jquery.js

209 ms

jquery-migrate.min.js

jquery-migrate.min.js

157 ms

idle-timer.min.js

idle-timer.min.js

126 ms

custom.js

custom.js

133 ms

add-to-cart.min.js

add-to-cart.min.js

133 ms

jquery.blockUI.min.js

jquery.blockUI.min.js

144 ms

woocommerce.min.js

woocommerce.min.js

143 ms

jquery.cookie.min.js

jquery.cookie.min.js

144 ms

cart-fragments.min.js

cart-fragments.min.js

152 ms

devicepx-jetpack.js

devicepx-jetpack.js

14 ms

gprofiles.js

gprofiles.js

59 ms

wpgroho.js

wpgroho.js

219 ms

superfish.js

superfish.js

220 ms

custom.js

custom.js

218 ms

jquery.easing-1.3.pack.js

jquery.easing-1.3.pack.js

220 ms

jquery.fancybox-1.3.4.pack.js

jquery.fancybox-1.3.4.pack.js

221 ms

et-ptemplates-frontend.js

et-ptemplates-frontend.js

221 ms

wp-embed.min.js

wp-embed.min.js

220 ms

e-201611.js

e-201611.js

16 ms

fire-bg-4.jpg

fire-bg-4.jpg

247 ms

sfpj-logo-6005.png

sfpj-logo-6005.png

238 ms

et-cart.png

et-cart.png

56 ms

mobile_arrow.png

mobile_arrow.png

56 ms

categories-bg.png

categories-bg.png

56 ms

scorpion-slide.jpg

scorpion-slide.jpg

246 ms

chipotle-slide.jpg

chipotle-slide.jpg

242 ms

slide-4-a.jpg

slide-4-a.jpg

248 ms

slide-3.jpg

slide-3.jpg

238 ms

scorpion-sting-140x135.png

scorpion-sting-140x135.png

237 ms

smokin-chipotle-140x135.png

smokin-chipotle-140x135.png

240 ms

jalapeno-jar-trans-140x135.png

jalapeno-jar-trans-140x135.png

241 ms

citrus-explosion-jar-140x135.png

citrus-explosion-jar-140x135.png

242 ms

fair-first.png

fair-first.png

246 ms

fair-best.png

fair-best.png

244 ms

pd-fw-festival.png

pd-fw-festival.png

285 ms

u-WUoqrET9fUeobQW7jkRaCWcynf_cDxXwCLxiixG1c.ttf

u-WUoqrET9fUeobQW7jkRaCWcynf_cDxXwCLxiixG1c.ttf

21 ms

cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf

cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf

20 ms

DXI1ORHCpsQm3Vp6mXoaTdqQynqKV_9Plp7mupa0S4g.ttf

DXI1ORHCpsQm3Vp6mXoaTdqQynqKV_9Plp7mupa0S4g.ttf

198 ms

k3k702ZOKiLJc3WVjuplzNqQynqKV_9Plp7mupa0S4g.ttf

k3k702ZOKiLJc3WVjuplzNqQynqKV_9Plp7mupa0S4g.ttf

198 ms

k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf

k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf

21 ms

EInbV5DfGHOiMmvb1Xr-htqQynqKV_9Plp7mupa0S4g.ttf

EInbV5DfGHOiMmvb1Xr-htqQynqKV_9Plp7mupa0S4g.ttf

197 ms

PRmiXeptR36kaC0GEAetxvqEJM-AK1nFUafhVdytxUY.ttf

PRmiXeptR36kaC0GEAetxvqEJM-AK1nFUafhVdytxUY.ttf

177 ms

PRmiXeptR36kaC0GEAetxiBnJMIPt0VoltfALX9gDFQ.ttf

PRmiXeptR36kaC0GEAetxiBnJMIPt0VoltfALX9gDFQ.ttf

178 ms

PRmiXeptR36kaC0GEAetxk7Gbs5Oj9RrfpUUQRHsz5w.ttf

PRmiXeptR36kaC0GEAetxk7Gbs5Oj9RrfpUUQRHsz5w.ttf

178 ms

admin-ajax.php

admin-ajax.php

584 ms

hovercard.css

hovercard.css

83 ms

services.css

services.css

85 ms

g.gif

g.gif

27 ms

woocommerce-smallscreen.css

woocommerce-smallscreen.css

33 ms

left-arrow.png

left-arrow.png

35 ms

right-arrow.png

right-arrow.png

37 ms

slide-controller-active.png

slide-controller-active.png

37 ms

slide-controller.png

slide-controller.png

37 ms

Accessibility Review

sweetfirejelly.com accessibility score

86

Accessibility Issues

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

Document doesn't have a <title> element

High

<frame> or <iframe> elements do not have a title

Best Practices

sweetfirejelly.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

sweetfirejelly.com SEO score

75

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Document doesn't have a <title> element

Crawling and Indexing

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

Impact

Issue

High

Page is blocked from indexing

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

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Sweetfirejelly.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Sweetfirejelly.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

sweetfirejelly.com

Open Graph data is detected on the main page of Sweetfirejelly. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: