Tools & Wizards About Us
iburn.com screenshot

Report Summary

  • 14

    Performance

    Renders faster than
    26% of other websites

  • 75

    Accessibility

    Visual factors better than
    that of 41% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 78

    SEO

    Google-friendlier than
    39% of websites

iburn.com

Hot Sauce Boss

Page Load Speed

3.2 sec in total

First Response

348 ms

Resources Loaded

2.5 sec

Page Rendered

265 ms

iburn.com screenshot

About Website

Click here to check amazing Iburn content for United States. Otherwise, check out these important facts you probably never knew about iburn.com

Hot Sauce Boss is a spice-centric marketplace offering hot sauces, salsas, rubs & other goods curated by the Spicy Challenge OG; Hot Sauce Boss himself.

Visit iburn.com

Key Findings

We analyzed Iburn.com page load time and found that the first response time was 348 ms and then it took 2.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

iburn.com performance score

14

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value8.8 s

0/100

10%

LCP (Largest Contentful Paint)

Value11.0 s

0/100

25%

SI (Speed Index)

Value9.8 s

10/100

10%

TBT (Total Blocking Time)

Value1,790 ms

10/100

30%

CLS (Cumulative Layout Shift)

Value0.192

64/100

15%

TTI (Time to Interactive)

Value14.7 s

8/100

10%

Network Requests Diagram

Default.asp

348 ms

platform.js

85 ms

jquery-ui.css

80 ms

default.css

123 ms

Artisan20240122103452.css

102 ms

Our browser made a total of 67 requests to load all elements on the main page. We found that 43% of them (29 requests) were addressed to the original Iburn.com, 18% (12 requests) were made to Cdn4.volusion.store and 13% (9 requests) were made to D21ivvgspl06jm.cloudfront.net. The less responsive or slowest element that took the longest time to load (546 ms) relates to the external source Cdn4.volusion.store.

Page Optimization Overview & Recommendations

Page size can be reduced by 417.9 kB (35%)

Content Size

1.2 MB

After Optimization

779.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Iburn.com main page is 1.2 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. 55% of websites need less resources to load. Images take 405.4 kB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 89.4 kB

  • Original 125.0 kB
  • After minification 124.2 kB
  • After compression 35.6 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 89.4 kB or 72% of the original size.

Image Optimization

-0%

Potential reduce by 81 B

  • Original 405.4 kB
  • After minification 405.4 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. Iburn images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 1.8 kB

  • Original 262.6 kB
  • After minification 262.6 kB
  • After compression 260.8 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

-81%

Potential reduce by 326.7 kB

  • Original 404.3 kB
  • After minification 403.6 kB
  • After compression 77.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. Iburn.com needs all CSS files to be minified and compressed as it can save up to 326.7 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 40 (63%)

Requests Now

64

After Optimization

24

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Default.asp

Default.asp

348 ms

platform.js

platform.js

85 ms

jquery-ui.css

jquery-ui.css

80 ms

default.css

default.css

123 ms

Artisan20240122103452.css

Artisan20240122103452.css

102 ms

jquery-3.7.1.min.js

jquery-3.7.1.min.js

84 ms

jquery-migrate-merged.js

jquery-migrate-merged.js

128 ms

jquery-ui.min.js

jquery-ui.min.js

98 ms

volusion.js

volusion.js

185 ms

content.css

content.css

186 ms

paypal-rest-default-buttons.js

paypal-rest-default-buttons.js

155 ms

soft_add.js

soft_add.js

155 ms

soft_add_mult.js

soft_add_mult.js

187 ms

soft_add.css

soft_add.css

231 ms

javascripts.js

javascripts.js

246 ms

js

js

121 ms

optimize.js

optimize.js

121 ms

f2c8c7e93216e073_complete.js

f2c8c7e93216e073_complete.js

93 ms

js

js

119 ms

template.css

template.css

239 ms

snippets.css

snippets.css

257 ms

theme-icons-base.css

theme-icons-base.css

87 ms

design-toolkit.min.js

design-toolkit.min.js

276 ms

vnav.css

vnav.css

270 ms

vnav.js

vnav.js

337 ms

email-decode.min.js

email-decode.min.js

241 ms

template.min.js

template.min.js

348 ms

class-name-watcher.js

class-name-watcher.js

338 ms

paypal-push-cart.js

paypal-push-cart.js

341 ms

push-cart.js

push-cart.js

346 ms

vcd15cbe7772f49c399c6a5babf22c1241717689176015

vcd15cbe7772f49c399c6a5babf22c1241717689176015

125 ms

css

css

39 ms

css

css

57 ms

fontello.css

fontello.css

190 ms

ionicons.min.css

ionicons.min.css

265 ms

3bde211df716b1567ace28e0c.js

3bde211df716b1567ace28e0c.js

331 ms

Michael-Madsen-Spicy-Mustard-1.jpg

Michael-Madsen-Spicy-Mustard-1.jpg

310 ms

Melinda-Ghost-Sauce-1.jpg

Melinda-Ghost-Sauce-1.jpg

467 ms

Mango-Habanero-Preserves-1.jpg

Mango-Habanero-Preserves-1.jpg

466 ms

Perky-Peppers-Chipotle-Sauce-1.jpg

Perky-Peppers-Chipotle-Sauce-1.jpg

466 ms

Blueberry-Reaper-Hot-Sauce-1.jpg

Blueberry-Reaper-Hot-Sauce-1.jpg

469 ms

gummy-hot-wing-challenge-1.jpg

gummy-hot-wing-challenge-1.jpg

466 ms

Caribbean-Curry-Hot-Sauce-1.jpg

Caribbean-Curry-Hot-Sauce-1.jpg

336 ms

Candied-Jalapenos-1.jpg

Candied-Jalapenos-1.jpg

458 ms

Ghost-Pepper-Salsa-1.jpg

Ghost-Pepper-Salsa-1.jpg

546 ms

Mango-Habanero-Salsa-1.jpg

Mango-Habanero-Salsa-1.jpg

545 ms

Char-Man-Caribbean-Hot-Sauce-1.jpg

Char-Man-Caribbean-Hot-Sauce-1.jpg

543 ms

Agave-Sweet-Spicy-Hot-Sauce-1.jpg

Agave-Sweet-Spicy-Hot-Sauce-1.jpg

541 ms

header_bg.jpg

header_bg.jpg

65 ms

clear1x1.gif

clear1x1.gif

305 ms

Icon_FreeShipping_Small.gif

Icon_FreeShipping_Small.gif

137 ms

iBurn-Street-Art-Mural-Banner.jpg

iBurn-Street-Art-Mural-Banner.jpg

318 ms

1cXxaUPXBpj2rGoU7C9WiHGA.ttf

1cXxaUPXBpj2rGoU7C9WiHGA.ttf

272 ms

va9b4kzIxd1KFppkaRKvDRPJVDf_vB_ekGrW.ttf

va9b4kzIxd1KFppkaRKvDRPJVDf_vB_ekGrW.ttf

330 ms

facebook-dark.svg

facebook-dark.svg

183 ms

twitter-dark.svg

twitter-dark.svg

178 ms

instagram-dark.svg

instagram-dark.svg

180 ms

paypal-dark.svg

paypal-dark.svg

187 ms

visa-dark.svg

visa-dark.svg

182 ms

discover-dark.svg

discover-dark.svg

190 ms

mastercard-dark.svg

mastercard-dark.svg

185 ms

amex-dark.svg

amex-dark.svg

183 ms

ConfigurationSettingProvider.ashx

ConfigurationSettingProvider.ashx

196 ms

ui-bg_flat_75_ffffff_40x100.png

ui-bg_flat_75_ffffff_40x100.png

47 ms

svgdefs.svg

svgdefs.svg

164 ms

embed.js

embed.js

156 ms

main.js

main.js

75 ms

Accessibility Review

iburn.com accessibility score

75

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

ARIA input fields do not have accessible names

High

[aria-*] attributes do not have valid values

High

ARIA IDs are not unique

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

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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

iburn.com best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

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

SEO Factors

iburn.com SEO score

78

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

High

robots.txt is not valid

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

iburn.com

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