Tools & Wizards About Us

Report Summary

  • 4

    Performance

    Renders faster than
    20% of other websites

  • 76

    Accessibility

    Visual factors better than
    that of 42% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

peppynet.com

ペット用品の通販サイト ペピイ（PEPPY）

Page Load Speed

8.2 sec in total

First Response

10 ms

Resources Loaded

7.6 sec

Page Rendered

536 ms

About Website

Click here to check amazing PEPPY Net content for Japan. Otherwise, check out these important facts you probably never knew about peppynet.com

ペット用品の通販サイト ペピイ（PEPPY）公式HP【スマホ対応】。ドッグフード・キャットフードをはじめとしたペット用品通販やペットのお役立ち情報、ペットの施設検索など、ペットの総合情報サイトです。

Visit peppynet.com

Key Findings

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

Performance Metrics

peppynet.com performance score

4

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

36/100

10%

LCP (Largest Contentful Paint)

Value25.5 s

0/100

25%

SI (Speed Index)

Value22.3 s

0/100

10%

TBT (Total Blocking Time)

Value7,650 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.805

5/100

15%

TTI (Time to Interactive)

Value35.0 s

0/100

10%

Network Requests Diagram

peppynet.com

10 ms

peppynet.com

691 ms

www.peppynet.com

42 ms

gtm.js

129 ms

index.css

686 ms

Our browser made a total of 205 requests to load all elements on the main page. We found that 16% of them (33 requests) were addressed to the original Peppynet.com, 33% (68 requests) were made to Image.peppynet.com and 12% (24 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (4.1 sec) relates to the external source Image.peppynet.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 761.3 kB (12%)

Content Size

6.2 MB

After Optimization

5.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Peppynet.com main page is 6.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. Only a small number of websites need less resources to load. Images take 5.4 MB which makes up the majority of the site volume.

HTML Optimization

-90%

Potential reduce by 350.1 kB

  • Original 389.6 kB
  • After minification 286.6 kB
  • After compression 39.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. This page needs HTML code to be minified as it can gain 103.0 kB, which is 26% 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 350.1 kB or 90% of the original size.

Image Optimization

-6%

Potential reduce by 334.7 kB

  • Original 5.4 MB
  • After minification 5.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. PEPPY Net images are well optimized though.

JavaScript Optimization

-19%

Potential reduce by 75.9 kB

  • Original 407.6 kB
  • After minification 407.6 kB
  • After compression 331.7 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 75.9 kB or 19% of the original size.

CSS Optimization

-2%

Potential reduce by 475 B

  • Original 25.2 kB
  • After minification 25.2 kB
  • After compression 24.7 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. Peppynet.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 90 (46%)

Requests Now

197

After Optimization

107

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

peppynet.com accessibility score

76

Accessibility Issues

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

peppynet.com best practices score

58

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

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

peppynet.com SEO score

85

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

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

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    UTF-8

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

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