16.3 sec in total
1.1 sec
15 sec
235 ms
Welcome to petio.com homepage info - get ready to check Petio best content for Japan right away, or after learning these important things about petio.com
「ペットと人が幸せに暮らせる社会の創造」を目指す、ペティオのコーポレートサイトです。商品情報やキャンペーンのお知らせなどペティオの最新情報や、犬や猫の飼い方やしつけ、お悩みを解決するコンテンツなど、ペットとの生活を豊かにするコンテンツを揃えています。
Visit petio.comWe analyzed Petio.com page load time and found that the first response time was 1.1 sec and then it took 15.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
petio.com performance score
name
value
score
weighting
Value5.6 s
5/100
10%
Value35.6 s
0/100
25%
Value18.0 s
0/100
10%
Value4,370 ms
1/100
30%
Value0.333
34/100
15%
Value32.4 s
0/100
10%
1063 ms
343 ms
349 ms
1296 ms
371 ms
Our browser made a total of 97 requests to load all elements on the main page. We found that 98% of them (95 requests) were addressed to the original Petio.com, 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (13 sec) belongs to the original domain Petio.com.
Page size can be reduced by 155.7 kB (10%)
1.6 MB
1.4 MB
In fact, the total size of Petio.com main page is 1.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. 25% of websites need less resources to load. Images take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 17.8 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 17.8 kB or 77% of the original size.
Potential reduce by 13.4 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. Petio images are well optimized though.
Potential reduce by 85.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 85.0 kB or 60% of the original size.
Potential reduce by 39.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. Petio.com needs all CSS files to be minified and compressed as it can save up to 39.5 kB or 80% of the original size.
Number of requests can be reduced by 49 (51%)
96
47
The browser has sent 96 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Petio. 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 from 7 to 1 for CSS and as a result speed up the page load time.
petio.com
1063 ms
set.css
343 ms
gallery.css
349 ms
jquery-1.7.1.min.js
1296 ms
jquery.blend-min.js
371 ms
jquery.tools.js
417 ms
utility.js
512 ms
common.js
691 ms
font_resize.js
739 ms
jquery.gallery.js
831 ms
default.css
294 ms
layout.css
683 ms
module.css
506 ms
base.css
870 ms
useful.css
797 ms
ga.js
92 ms
bg_line.gif
214 ms
lgo_petio.gif
187 ms
hnav01.gif
173 ms
hnav02.gif
188 ms
hnav03.gif
209 ms
hnav04.gif
175 ms
hnav05.gif
342 ms
bg_navi_line.gif
346 ms
bg_navi.gif
371 ms
ico_navarw.gif
370 ms
20_1.jpg
5338 ms
23_1.jpg
3326 ms
21_1.jpg
3276 ms
25_1.jpg
3030 ms
22_1.jpg
3063 ms
24_1.jpg
12958 ms
20_2.jpg
3375 ms
23_2.jpg
3432 ms
21_2.jpg
3446 ms
25_2.jpg
3536 ms
22_2.jpg
3720 ms
24_2.jpg
3617 ms
btn_gallery_back.gif
3615 ms
btn_gallery_next.gif
3748 ms
font_size.gif
3785 ms
font_language.gif
3802 ms
bg_picup.gif
3891 ms
tit_pickup.gif
3961 ms
nav_lineup.gif
3957 ms
3_1.jpg
4564 ms
4_1.jpg
4236 ms
2_1.jpg
4297 ms
6_1.jpg
4221 ms
7_1.jpg
4436 ms
5_1.jpg
4580 ms
1_1.jpg
4637 ms
__utm.gif
11 ms
tit_brand.gif
4489 ms
nav_brand_petio.gif
4585 ms
nav_brand_zottone.gif
4578 ms
nav_brand_addmate.gif
4632 ms
tit_news.gif
4666 ms
nav_motlook.gif
4732 ms
ico_rss.gif
4596 ms
ico_newsplaza.gif
4646 ms
ico_petio.gif
4725 ms
ico_event.gif
4739 ms
ico_campaign.gif
2097 ms
bnr_shop_s.jpg
2268 ms
tit_itemsearch.gif
2024 ms
btn_search.gif
1958 ms
tit_plaza.gif
1938 ms
txt_plaza.gif
2023 ms
btn_regist.gif
2065 ms
btn_login.gif
1962 ms
bnr_recruit.jpg
1887 ms
tit_topics.gif
1926 ms
topics_bg.gif
1910 ms
tit_useful_magazine.jpg
1934 ms
topics_bottom.gif
1886 ms
ico_cursor.gif
1920 ms
tit_useful_faq.jpg
1858 ms
tit_useful_petlife.jpg
1844 ms
tit_useful_preciante.jpg
1881 ms
topics_end.gif
1645 ms
bnr_fb.jpg
1697 ms
tit_twitter.gif
1658 ms
nav_petiokouhou.gif
1533 ms
nav_petiomaster.gif
1449 ms
pagetop.gif
1469 ms
bnr_petio.gif
1507 ms
bnr_zuttone.gif
1511 ms
bnr_addmate.gif
1393 ms
ico_cursor2.gif
1427 ms
ico_blank.gif
1424 ms
copy.gif
1452 ms
btn_gallery_on.gif
1429 ms
font_s_size.gif
1435 ms
font_m_size.gif
1372 ms
font_l_size.gif
1333 ms
font_s_size_on.gif
1390 ms
petio.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
petio.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
petio.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
Document uses legible font sizes
Tap targets are not sized appropriately
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Petio.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 Petio.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.
petio.com
Open Graph description is not detected on the main page of Petio. 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: