Access petgo.jp. ペットゴー（petgo）＜公式＞｜犬猫の療法食、医薬品、サプリメントなどのペットヘルスケア通販

petgo.jp screenshot

12

Performance

Renders faster than
25% of other websites
68

Accessibility

Visual factors better than
that of 33% of websites
75

Best Practices

More advanced features
available than in
35% of websites
83

SEO

Google-friendlier than
46% of websites

First Response

338 ms

Resources Loaded

6.5 sec

Page Rendered

563 ms

petgo.jp screenshot

About Website

Welcome to petgo.jp homepage info - get ready to check Petgo best content for Japan right away, or after learning these important things about petgo.jp

ペットゴーは食事療法食、総合栄養食、動物用医薬品、サプリメントなどを取り扱うペットヘルスケア通販サイトです。ハッピーペットライフ・ハッピーワールドのスローガンのもと、ペットのQOL向上に貢献していきます。

Visit petgo.jp

Key Findings

We analyzed Petgo.jp page load time and found that the first response time was 338 ms and then it took 7 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

name

value

score

weighting

FCP (First Contentful Paint)

Value4.3 s

18/100

10%

LCP (Largest Contentful Paint)

Value19.8 s

0/100

25%

SI (Speed Index)

Value13.0 s

2/100

10%

TBT (Total Blocking Time)

Value1,230 ms

20/100

30%

CLS (Cumulative Layout Shift)

Value0.376

28/100

15%

TTI (Time to Interactive)

Value26.3 s

0/100

10%

petgo.jp

338 ms

www.petgo.jp

867 ms

style.css

342 ms

slick.css

495 ms

slick-theme.css

498 ms

Our browser made a total of 203 requests to load all elements on the main page. We found that 33% of them (67 requests) were addressed to the original Petgo.jp, 22% (45 requests) were made to Pos.petgo.jp and 18% (37 requests) were made to Petgo-pos.s3-ap-northeast-1.amazonaws.com. The less responsive or slowest element that took the longest time to load (2 sec) relates to the external source Pos.petgo.jp.

Content Size

8.5 MB

After Optimization

6.0 MB

In fact, the total size of Petgo.jp main page is 8.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 8.0 MB which makes up the majority of the site volume.

HTML Optimization

-92%

Potential reduce by 198.9 kB

Original 216.6 kB
After minification 187.0 kB
After compression 17.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. This page needs HTML code to be minified as it can gain 29.6 kB, which is 14% 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 198.9 kB or 92% of the original size.

Image Optimization

-28%

Potential reduce by 2.3 MB

Original 8.0 MB
After minification 5.7 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. Obviously, Petgo needs image optimization as it can save up to 2.3 MB or 28% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-12%

Potential reduce by 25.9 kB

Original 214.6 kB
After minification 212.9 kB
After compression 188.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 25.9 kB or 12% of the original size.

CSS Optimization

-11%

Potential reduce by 8.5 kB

Original 78.8 kB
After minification 78.8 kB
After compression 70.3 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. Petgo.jp needs all CSS files to be minified and compressed as it can save up to 8.5 kB or 11% of the original size.

Requests Now

198

After Optimization

112

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

Accessibility Issues

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

High

[aria-*] attributes do not match their roles

High

[aria-hidden="true"] elements contain focusable descendents

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

ARIA toggle fields do not have accessible names

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

High

Serves images with low resolution

Low

Detected JavaScript libraries

Search Engine Optimization Advices

To appear in search results, crawlers need access to your app.

High

Links are not crawlable

Format your HTML in a way that enables crawlers to better understand your app’s content.

High

Image elements do not have [alt] attributes

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

High

Tap targets are not sized appropriately

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 Petgo.jp 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 Petgo.jp 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

petgo.jp

Open Graph data is detected on the main page of Petgo. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: