Tools & Wizards About Us
wildpepper.com screenshot

Report Summary

  • 65

    Performance

    Renders faster than
    78% 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

  • 75

    SEO

    Google-friendlier than
    32% of websites

wildpepper.com

Buy Hot Sauces, BBQ Sauce & Chile Seasonings - Mild to Wild® Pepper & Herb Co.

Page Load Speed

2 sec in total

First Response

190 ms

Resources Loaded

1.7 sec

Page Rendered

197 ms

wildpepper.com screenshot

About Website

Welcome to wildpepper.com homepage info - get ready to check Wild Pepper best content right away, or after learning these important things about wildpepper.com

Buy sauces and seasonings to enjoy a night of fine cuisine. Create a new sauce from combinations of our sauces and seasonings.

Visit wildpepper.com

Key Findings

We analyzed Wildpepper.com page load time and found that the first response time was 190 ms and then it took 1.9 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

wildpepper.com performance score

65

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

37/100

10%

LCP (Largest Contentful Paint)

Value4.9 s

28/100

25%

SI (Speed Index)

Value3.6 s

86/100

10%

TBT (Total Blocking Time)

Value320 ms

76/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value5.1 s

76/100

10%

Network Requests Diagram

wildpepper.com

190 ms

www.wildpepper.com

636 ms

styles.css

97 ms

styles.css

209 ms

iselector.css

100 ms

Our browser made a total of 64 requests to load all elements on the main page. We found that 22% of them (14 requests) were addressed to the original Wildpepper.com, 28% (18 requests) were made to Cdn1.bigcommerce.com and 27% (17 requests) were made to Cdn9.bigcommerce.com. The less responsive or slowest element that took the longest time to load (636 ms) belongs to the original domain Wildpepper.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 196.3 kB (19%)

Content Size

1.0 MB

After Optimization

836.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-80%

Potential reduce by 35.8 kB

  • Original 44.7 kB
  • After minification 39.0 kB
  • After compression 9.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. This page needs HTML code to be minified as it can gain 5.7 kB, which is 13% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 35.8 kB or 80% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 532.2 kB
  • After minification 532.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. Wild Pepper images are well optimized though.

JavaScript Optimization

-36%

Potential reduce by 156.4 kB

  • Original 439.3 kB
  • After minification 434.8 kB
  • After compression 282.9 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 156.4 kB or 36% of the original size.

CSS Optimization

-26%

Potential reduce by 4.2 kB

  • Original 16.2 kB
  • After minification 16.2 kB
  • After compression 12.0 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. Wildpepper.com needs all CSS files to be minified and compressed as it can save up to 4.2 kB or 26% of the original size.

Requests Breakdown

Number of requests can be reduced by 39 (64%)

Requests Now

61

After Optimization

22

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

wildpepper.com

wildpepper.com

190 ms

www.wildpepper.com

www.wildpepper.com

636 ms

styles.css

styles.css

97 ms

styles.css

styles.css

209 ms

iselector.css

iselector.css

100 ms

orange.css

orange.css

239 ms

product.attributes.css

product.attributes.css

104 ms

ui.all.css

ui.all.css

100 ms

product.quickview.css

product.quickview.css

95 ms

store.css

store.css

105 ms

imodal.css

imodal.css

111 ms

signup.css

signup.css

247 ms

jquery.min.js

jquery.min.js

117 ms

menudrop.js

menudrop.js

101 ms

common.js

common.js

74 ms

iselector.js

iselector.js

120 ms

cufon-yui.js

cufon-yui.js

163 ms

rodeo.font.js

rodeo.font.js

172 ms

jquery-ui.min.js

jquery-ui.min.js

116 ms

quickview.js

quickview.js

130 ms

jquery.form.js

jquery.form.js

127 ms

imodal.js

imodal.js

118 ms

loader.js

loader.js

65 ms

quicksearch.js

quicksearch.js

123 ms

jquery.cycle.all.min.js

jquery.cycle.all.min.js

194 ms

plusone.js

plusone.js

72 ms

classic-081711.css

classic-081711.css

37 ms

mc-validate.js

mc-validate.js

73 ms

jquery.bgiframe.min.js

jquery.bgiframe.min.js

127 ms

superfish.js

superfish.js

131 ms

visitor.js

visitor.js

134 ms

csrf-protection-header-5eeddd5de78d98d146ef4fd71b2aedce4161903e.js

csrf-protection-header-5eeddd5de78d98d146ef4fd71b2aedce4161903e.js

133 ms

ga.js

ga.js

102 ms

fbevents.js

fbevents.js

154 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

49 ms

flames.jpg

flames.jpg

269 ms

ajax-loader.gif

ajax-loader.gif

353 ms

M2W_LOGO600Trademarked_.jpg

M2W_LOGO600Trademarked_.jpg

241 ms

searchBG.png

searchBG.png

413 ms

phone.gif

phone.gif

186 ms

facebook.gif

facebook.gif

202 ms

search.png

search.png

231 ms

bg_lefth2.gif

bg_lefth2.gif

159 ms

bg_sidelia.gif

bg_sidelia.gif

163 ms

RSS.gif

RSS.gif

355 ms

IcoRating5.gif

IcoRating5.gif

339 ms

IcoRating0.gif

IcoRating0.gif

359 ms

m2w-banner-ghost13b.jpg

m2w-banner-ghost13b.jpg

328 ms

m2w-banner-scorpion13b.jpg

m2w-banner-scorpion13b.jpg

340 ms

m2w-banner-hotsaucesb.jpg

m2w-banner-hotsaucesb.jpg

377 ms

m2w-banner-bbq.jpg

m2w-banner-bbq.jpg

281 ms

m2w-banner-unbearables2.jpg

m2w-banner-unbearables2.jpg

354 ms

m2w-banner-redsavina.jpg

m2w-banner-redsavina.jpg

479 ms

M2WBBQ_newlabels_swchipotle__64949.1365177130.120.120.jpg

M2WBBQ_newlabels_swchipotle__64949.1365177130.120.120.jpg

303 ms

M2Wredsav-ralph__53853.1332532435.120.120.jpg

M2Wredsav-ralph__53853.1332532435.120.120.jpg

325 ms

stupid_hot__48228.1299099009.120.120.jpg

stupid_hot__48228.1299099009.120.120.jpg

362 ms

M2Wredsav__52537.1332534428.120.120.jpg

M2Wredsav__52537.1332534428.120.120.jpg

342 ms

rookie__33751.1299098897.120.120.jpg

rookie__33751.1299098897.120.120.jpg

360 ms

M2WRalphs__20618.1332532712.120.120.jpg

M2WRalphs__20618.1332532712.120.120.jpg

355 ms

__utm.gif

__utm.gif

106 ms

b_addtocart.gif

b_addtocart.gif

408 ms

984002228324120

984002228324120

82 ms

index.php

index.php

177 ms

nobot

nobot

37 ms

Accessibility Review

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

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

wildpepper.com SEO score

75

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

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

wildpepper.com

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