Tools & Wizards About Us
amazonpepper.com screenshot

Report Summary

  • 56

    Performance

    Renders faster than
    73% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 89% of websites

  • 50

    Best Practices

    More advanced features
    available than in
    18% of websites

  • 62

    SEO

    Google-friendlier than
    22% of websites

amazonpepper.com

Amazon Pepper

Page Load Speed

1.4 sec in total

First Response

132 ms

Resources Loaded

1 sec

Page Rendered

204 ms

amazonpepper.com screenshot

About Website

Visit amazonpepper.com now to see the best up-to-date Amazon Pepper content and also check out these interesting facts you probably never knew about amazonpepper.com

Amazon Pepper te trae un amplio portafolio de productos picantes especiales para realzar el sabor de tus comidas. Descúbrelos aquí.

Visit amazonpepper.com

Key Findings

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

Performance Metrics

amazonpepper.com performance score

56

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.3 s

74/100

10%

LCP (Largest Contentful Paint)

Value8.3 s

2/100

25%

SI (Speed Index)

Value3.5 s

88/100

10%

TBT (Total Blocking Time)

Value460 ms

62/100

30%

CLS (Cumulative Layout Shift)

Value0.057

98/100

15%

TTI (Time to Interactive)

Value6.3 s

60/100

10%

Network Requests Diagram

amazonpepper.com

132 ms

313 ms

gtm.js

103 ms

css

32 ms

dashicons.min.css

73 ms

Our browser made a total of 29 requests to load all elements on the main page. We found that 59% of them (17 requests) were addressed to the original Amazonpepper.com, 7% (2 requests) were made to Google-analytics.com and 7% (2 requests) were made to Connect.facebook.net. The less responsive or slowest element that took the longest time to load (313 ms) belongs to the original domain Amazonpepper.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 449.6 kB (17%)

Content Size

2.6 MB

After Optimization

2.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-83%

Potential reduce by 102.8 kB

  • Original 123.4 kB
  • After minification 122.1 kB
  • After compression 20.7 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 102.8 kB or 83% of the original size.

Image Optimization

-4%

Potential reduce by 77.4 kB

  • Original 2.1 MB
  • After minification 2.0 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. Amazon Pepper images are well optimized though.

JavaScript Optimization

-67%

Potential reduce by 240.4 kB

  • Original 356.8 kB
  • After minification 349.4 kB
  • After compression 116.5 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 240.4 kB or 67% of the original size.

CSS Optimization

-48%

Potential reduce by 29.1 kB

  • Original 60.6 kB
  • After minification 56.2 kB
  • After compression 31.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. Amazonpepper.com needs all CSS files to be minified and compressed as it can save up to 29.1 kB or 48% of the original size.

Requests Breakdown

Number of requests can be reduced by 7 (32%)

Requests Now

22

After Optimization

15

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 22 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Amazon 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 8 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

amazonpepper.com

amazonpepper.com

132 ms

313 ms

gtm.js

gtm.js

103 ms

css

css

32 ms

dashicons.min.css

dashicons.min.css

73 ms

jquery.rwdImageMaps.min.js

jquery.rwdImageMaps.min.js

73 ms

jquery.js

jquery.js

106 ms

autoptimize_76548d5529f227f7608874f58a2a3f7f.js

autoptimize_76548d5529f227f7608874f58a2a3f7f.js

137 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

73 ms

analytics.js

analytics.js

4 ms

collect

collect

35 ms

fbevents.js

fbevents.js

75 ms

header.jpg

header.jpg

107 ms

logo.png

logo.png

57 ms

sello.png

sello.png

57 ms

content.jpg

content.jpg

151 ms

slide7-3.jpg

slide7-3.jpg

96 ms

amazon-legend-en-1.jpg

amazon-legend-en-1.jpg

126 ms

1-2.jpg

1-2.jpg

95 ms

banner-recipe-us.jpg

banner-recipe-us.jpg

193 ms

footer2.jpg

footer2.jpg

132 ms

collect

collect

95 ms

baron-neue.black-webfont.woff

baron-neue.black-webfont.woff

81 ms

AAABVuGyrgAA

AAABVuGyrgAA

3 ms

WJ6D195CfbTRlIs49IbkFw.woff

WJ6D195CfbTRlIs49IbkFw.woff

29 ms

0Aa8aBJcGN1n1zDNhqNrnQ.woff

0Aa8aBJcGN1n1zDNhqNrnQ.woff

30 ms

1874611486093259

1874611486093259

17 ms

21 ms

ga-audiences

ga-audiences

41 ms

Accessibility Review

amazonpepper.com accessibility score

96

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

Links do not have a discernible name

Best Practices

amazonpepper.com best practices score

50

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

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

amazonpepper.com SEO score

62

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

Links do not have descriptive text

Language and Encoding

  • Language Detected

    ES

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Amazonpepper.com can be misinterpreted by Google and other search engines. Our service has detected that Spanish is used on the page, and it does not match the claimed English language. Our system also found out that Amazonpepper.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

amazonpepper.com

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