Tools & Wizards About Us
burningtastebuds.com screenshot

Report Summary

  • 71

    Performance

    Renders faster than
    81% of other websites

  • 70

    Accessibility

    Visual factors better than
    that of 35% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

burningtastebuds.com

Award winning Chilli Salts, Chilli Rubs and Chilli Beef Jerky

Page Load Speed

4.3 sec in total

First Response

474 ms

Resources Loaded

2.4 sec

Page Rendered

1.4 sec

burningtastebuds.com screenshot

About Website

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

We have award winning chilli salts - from mild to hot. A range of Chilli Rubs and Chilli Beef Jerky

Visit burningtastebuds.com

Key Findings

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

Performance Metrics

burningtastebuds.com performance score

71

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

28/100

10%

LCP (Largest Contentful Paint)

Value4.8 s

30/100

25%

SI (Speed Index)

Value3.7 s

85/100

10%

TBT (Total Blocking Time)

Value100 ms

98/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value4.7 s

80/100

10%

Network Requests Diagram

www.burningtastebuds.com

474 ms

css

119 ms

css

116 ms

styles.css

233 ms

styles.css

306 ms

Our browser made a total of 97 requests to load all elements on the main page. We found that 41% of them (40 requests) were addressed to the original Burningtastebuds.com, 23% (22 requests) were made to Cdn9.bigcommerce.com and 14% (14 requests) were made to Cdn2.bigcommerce.com. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Burningtastebuds.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 556.4 kB (37%)

Content Size

1.5 MB

After Optimization

941.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Burningtastebuds.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. 70% of websites need less resources to load. Images take 730.3 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 35.7 kB

  • Original 45.1 kB
  • After minification 41.5 kB
  • After compression 9.5 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 35.7 kB or 79% of the original size.

Image Optimization

-0%

Potential reduce by 174 B

  • Original 730.3 kB
  • After minification 730.2 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. Burningtastebuds images are well optimized though.

JavaScript Optimization

-70%

Potential reduce by 430.2 kB

  • Original 610.3 kB
  • After minification 503.8 kB
  • After compression 180.1 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 430.2 kB or 70% of the original size.

CSS Optimization

-81%

Potential reduce by 90.3 kB

  • Original 111.9 kB
  • After minification 94.4 kB
  • After compression 21.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. Burningtastebuds.com needs all CSS files to be minified and compressed as it can save up to 90.3 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 47 (49%)

Requests Now

95

After Optimization

48

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.burningtastebuds.com

www.burningtastebuds.com

474 ms

css

css

119 ms

css

css

116 ms

styles.css

styles.css

233 ms

styles.css

styles.css

306 ms

iselector.css

iselector.css

347 ms

flexslider.css

flexslider.css

267 ms

slide-show.css

slide-show.css

304 ms

styles-slide-show.css

styles-slide-show.css

252 ms

social.css

social.css

223 ms

white.css

white.css

476 ms

theme.css

theme.css

445 ms

bedazzled.css

bedazzled.css

256 ms

product.attributes.css

product.attributes.css

286 ms

ui.all.css

ui.all.css

253 ms

product.quickview.css

product.quickview.css

297 ms

store.css

store.css

260 ms

imodal.css

imodal.css

266 ms

custom.css

custom.css

67 ms

jquery.bxslider.css

jquery.bxslider.css

202 ms

css

css

148 ms

css

css

141 ms

jquery-1.9.1.min.js

jquery-1.9.1.min.js

280 ms

jquery.min.js

jquery.min.js

175 ms

menudrop.js

menudrop.js

205 ms

common.js

common.js

207 ms

iselector.js

iselector.js

215 ms

jquery.bxslider.js

jquery.bxslider.js

439 ms

jquery.autobox.js

jquery.autobox.js

215 ms

init.js

init.js

216 ms

jquery.uniform.min.js

jquery.uniform.min.js

213 ms

main.js

main.js

268 ms

jquery-ui.min.js

jquery-ui.min.js

265 ms

jquery.validate.js

jquery.validate.js

268 ms

product.functions.js

product.functions.js

268 ms

product.attributes.js

product.attributes.js

261 ms

quickview.js

quickview.js

252 ms

quickview.initialise.js

quickview.initialise.js

252 ms

jquery.form.js

jquery.form.js

255 ms

imodal.js

imodal.js

256 ms

loader.js

loader.js

282 ms

quicksearch.js

quicksearch.js

283 ms

style_parallaxhome.css

style_parallaxhome.css

636 ms

getgeotrustseal

getgeotrustseal

280 ms

si.js

si.js

339 ms

csrf-protection-header-14d7a517a359072d0dc53537c6a3e7070e54b6c0.js

csrf-protection-header-14d7a517a359072d0dc53537c6a3e7070e54b6c0.js

258 ms

css

css

20 ms

ga.js

ga.js

280 ms

pmn-caecilia-webfont.woff

pmn-caecilia-webfont.woff

705 ms

headerbg.png

headerbg.png

582 ms

carticon.jpg

carticon.jpg

237 ms

fbicon.png

fbicon.png

237 ms

twiticon.png

twiticon.png

237 ms

logo.png

logo.png

234 ms

move1.1.png

move1.1.png

452 ms

move1.2.png

move1.2.png

539 ms

move1.3.png

move1.3.png

348 ms

move1.4.png

move1.4.png

349 ms

move1.5.png

move1.5.png

414 ms

move2.1.png

move2.1.png

462 ms

move2.2.png

move2.2.png

458 ms

move2.3.png

move2.3.png

447 ms

move2.4.png

move2.4.png

681 ms

move2.5.png

move2.5.png

574 ms

move2.6.png

move2.6.png

678 ms

move3.1.png

move3.1.png

587 ms

move3.2.png

move3.2.png

588 ms

move3.3.png

move3.3.png

597 ms

move3.4.png

move3.4.png

614 ms

move3.5.png

move3.5.png

761 ms

move3.6.png

move3.6.png

631 ms

moveitem1.png

moveitem1.png

713 ms

moveitem2.png

moveitem2.png

717 ms

moveitem3.png

moveitem3.png

829 ms

moveitem4.png

moveitem4.png

894 ms

bottwiticon.png

bottwiticon.png

861 ms

botfbicon.png

botfbicon.png

780 ms

mastercard.jpg

mastercard.jpg

786 ms

visacard.jpg

visacard.jpg

852 ms

paypal.jpg

paypal.jpg

1030 ms

all.js

all.js

246 ms

cartbg.png

cartbg.png

513 ms

socialbg.png

socialbg.png

395 ms

accuntbg.png

accuntbg.png

387 ms

navbg.png

navbg.png

372 ms

Slide1bg2.jpg

Slide1bg2.jpg

706 ms

Slide2bg2.jpg

Slide2bg2.jpg

645 ms

paraBg3.jpg

paraBg3.jpg

642 ms

Slide3bg2.jpg

Slide3bg2.jpg

670 ms

Slide4bg2.jpg

Slide4bg2.jpg

690 ms

footerbg.png

footerbg.png

852 ms

bullet.png

bullet.png

791 ms

__utm.gif

__utm.gif

84 ms

smarticon

smarticon

210 ms

uparrow.png

uparrow.png

746 ms

downarrow.png

downarrow.png

794 ms

all.js

all.js

5 ms

Accessibility Review

burningtastebuds.com accessibility score

70

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

Buttons do not have an accessible name

High

Links do not have a discernible name

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.

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

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

Page has valid source maps

SEO Factors

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

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 doesn't use 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 Burningtastebuds.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 Burningtastebuds.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

burningtastebuds.com

Open Graph description is not detected on the main page of Burningtastebuds. 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: