Access peapod.com. Grocery Delivery Service | Online Grocery Ordering

name

value

score

weighting

FCP (First Contentful Paint)

Value2.0 s

84/100

10%

LCP (Largest Contentful Paint)

Value4.4 s

38/100

25%

SI (Speed Index)

Value2.5 s

98/100

10%

TBT (Total Blocking Time)

Value1,590 ms

12/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value10.7 s

22/100

10%

peapod.com

363 ms

cf.challenge.js

649 ms

Our browser made a total of 2 requests to load all elements on the main page. We found that all of those requests were addressed to Peapod.com and no external sources were called. The less responsive or slowest element that took the longest time to load (649 ms) belongs to the original domain Peapod.com.

Content Size

1.1 MB

After Optimization

762.1 kB

In fact, the total size of Peapod.com main page is 1.1 MB. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only a small number of websites need less resources to load. Images take 638.4 kB which makes up the majority of the site volume.

HTML Optimization

-28%

Potential reduce by 9.8 kB

Original 34.9 kB
After minification 34.7 kB
After compression 25.2 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 9.8 kB or 28% of the original size.

Image Optimization

-2%

Potential reduce by 13.9 kB

Original 638.4 kB
After minification 624.5 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. Peapod images are well optimized though.

JavaScript Optimization

-66%

Potential reduce by 195.4 kB

Original 295.4 kB
After minification 274.6 kB
After compression 100.0 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 195.4 kB or 66% of the original size.

CSS Optimization

-85%

Potential reduce by 70.1 kB

Original 82.4 kB
After minification 63.8 kB
After compression 12.4 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. Peapod.com needs all CSS files to be minified and compressed as it can save up to 70.1 kB or 85% of the original size.

Requests Now

After Optimization

The browser has sent 1 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Peapod. According to our analytics all requests are already optimized.

Accessibility Issues

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

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.

High

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

These items highlight common accessibility best practices.

High

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

Areas of Improvement

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

Search Engine Optimization Advices

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/).

High

Document uses legible font sizes

Language and Encoding

Language Detected

N/A
Language Claimed

N/A
Encoding

UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Peapod.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) and no language is claimed in <html> or <meta> tags either. Our system also found out that Peapod.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

peapod.com

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