Tools & Wizards About Us
peve.jp screenshot

Report Summary

  • 26

    Performance

    Renders faster than
    45% of other websites

  • 69

    Accessibility

    Visual factors better than
    that of 34% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

peve.jp

トヨタバッテリー株式会社 | ハイブリッドカー・電気自動車用バッテリー（電池）の開発・製造・販売

Page Load Speed

10.9 sec in total

First Response

472 ms

Resources Loaded

10.1 sec

Page Rendered

273 ms

peve.jp screenshot

About Website

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

トヨタバッテリーの公式サイトです。企業情報、製品・ソリューション、イノベーション、サステナビリティ、ニュースリリース、採用情報などをご紹介します。

Visit peve.jp

Key Findings

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

Performance Metrics

peve.jp performance score

26

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.9 s

1/100

10%

LCP (Largest Contentful Paint)

Value55.4 s

0/100

25%

SI (Speed Index)

Value31.0 s

0/100

10%

TBT (Total Blocking Time)

Value820 ms

35/100

30%

CLS (Cumulative Layout Shift)

Value0.004

100/100

15%

TTI (Time to Interactive)

Value38.3 s

0/100

10%

Network Requests Diagram

peve.jp

472 ms

www.peve.jp

1704 ms

style.css

492 ms

style.min.css

663 ms

styles.css

523 ms

Our browser made a total of 75 requests to load all elements on the main page. We found that 73% of them (55 requests) were addressed to the original Peve.jp, 5% (4 requests) were made to Player.vimeo.com and 5% (4 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (3.4 sec) belongs to the original domain Peve.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 151.7 kB (13%)

Content Size

1.2 MB

After Optimization

1.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Peve.jp main page is 1.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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 880.4 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 51.8 kB

  • Original 65.6 kB
  • After minification 60.7 kB
  • After compression 13.9 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 51.8 kB or 79% of the original size.

Image Optimization

-6%

Potential reduce by 50.9 kB

  • Original 880.4 kB
  • After minification 829.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. Peve images are well optimized though.

JavaScript Optimization

-21%

Potential reduce by 18.5 kB

  • Original 89.5 kB
  • After minification 89.5 kB
  • After compression 71.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 18.5 kB or 21% of the original size.

CSS Optimization

-21%

Potential reduce by 30.5 kB

  • Original 146.5 kB
  • After minification 146.3 kB
  • After compression 115.9 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. Peve.jp needs all CSS files to be minified and compressed as it can save up to 30.5 kB or 21% of the original size.

Requests Breakdown

Number of requests can be reduced by 37 (59%)

Requests Now

63

After Optimization

26

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

peve.jp

peve.jp

472 ms

www.peve.jp

www.peve.jp

1704 ms

style.css

style.css

492 ms

style.min.css

style.min.css

663 ms

styles.css

styles.css

523 ms

dashicons.min.css

dashicons.min.css

872 ms

frontend.css

frontend.css

528 ms

pagenavi-css.css

pagenavi-css.css

678 ms

style.css

style.css

981 ms

import.css

import.css

1045 ms

font-awesome.min.css

font-awesome.min.css

1064 ms

jquery.min.js

jquery.min.js

1332 ms

zipaddr7.js

zipaddr7.js

1129 ms

js

js

73 ms

sdk.js

sdk.js

23 ms

scripts.js

scripts.js

1028 ms

imagesloaded.min.js

imagesloaded.min.js

1218 ms

masonry.min.js

masonry.min.js

1313 ms

jquery.masonry.min.js

jquery.masonry.min.js

1411 ms

rsvp.js

rsvp.js

1411 ms

jquery.vide.js

jquery.vide.js

1539 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

1675 ms

jquery.matchHeight-min.js

jquery.matchHeight-min.js

1710 ms

jquery.inview.min.js

jquery.inview.min.js

1823 ms

lightbox.js

lightbox.js

1906 ms

common.js

common.js

1913 ms

css2

css2

41 ms

css2

css2

60 ms

css2

css2

66 ms

html5reset-1.6.1.css

html5reset-1.6.1.css

1147 ms

fontawesome-all.css

fontawesome-all.css

1300 ms

icofont.min.css

icofont.min.css

1535 ms

lightbox.css

lightbox.css

1478 ms

base.css

base.css

1530 ms

wp.css

wp.css

1548 ms

layout.css

layout.css

1634 ms

content.css

content.css

1811 ms

default.css

default.css

2154 ms

close.png

close.png

382 ms

loading.gif

loading.gif

411 ms

prev.png

prev.png

604 ms

next.png

next.png

603 ms

google-earth-664x374.png

google-earth-664x374.png

901 ms

001.jpg

001.jpg

921 ms

002.jpg

002.jpg

1245 ms

003.jpg

003.jpg

1285 ms

004.jpg

004.jpg

1612 ms

005.jpg

005.jpg

1630 ms

f4205a7fc8c643dc3b86b8c5b1e653d7-320x180.png

f4205a7fc8c643dc3b86b8c5b1e653d7-320x180.png

1397 ms

no-image.jpg

no-image.jpg

1427 ms

54d847f76ce67c9e80b72c577564f1bb-320x180.jpg

54d847f76ce67c9e80b72c577564f1bb-320x180.jpg

1733 ms

1b215b4288a11a87866f09eb93f87874-2-320x180.jpg

1b215b4288a11a87866f09eb93f87874-2-320x180.jpg

2164 ms

b4c11a3c-6b77-4f3f-9412-2167ce3a2d07-320x180.jpg

b4c11a3c-6b77-4f3f-9412-2167ce3a2d07-320x180.jpg

2048 ms

logo.png

logo.png

1907 ms

nav-mail.png

nav-mail.png

2091 ms

sdk.js

sdk.js

88 ms

261451849

261451849

234 ms

261451957

261451957

235 ms

TK3_WkUHHAIjg75cFRf3bXL8LICs1y9ogUE.ttf

TK3_WkUHHAIjg75cFRf3bXL8LICs1y9ogUE.ttf

108 ms

TK3_WkUHHAIjg75cFRf3bXL8LICs1_FvgUE.ttf

TK3_WkUHHAIjg75cFRf3bXL8LICs1_FvgUE.ttf

137 ms

xn71YHs72GKoTvER4Gn3b5eMRtWGkp6o7MjQ2bzvPebA.ttf

xn71YHs72GKoTvER4Gn3b5eMRtWGkp6o7MjQ2bzvPebA.ttf

387 ms

xn71YHs72GKoTvER4Gn3b5eMRtWGkp6o7MjQ2bwxOubA.ttf

xn71YHs72GKoTvER4Gn3b5eMRtWGkp6o7MjQ2bwxOubA.ttf

424 ms

icofont.woff

icofont.woff

3362 ms

bg_news.jpg

bg_news.jpg

3108 ms

nav-xtwitter_w.png

nav-xtwitter_w.png

2311 ms

nav-movie_w.png

nav-movie_w.png

2427 ms

nav-mail_w.png

nav-mail_w.png

2485 ms

222 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

2970 ms

widgets.js

widgets.js

85 ms

261451849

261451849

148 ms

261451957

261451957

153 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

33 ms

settings

settings

115 ms

api.js

api.js

28 ms

Accessibility Review

peve.jp accessibility score

69

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.

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

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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

peve.jp best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

peve.jp SEO score

86

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 Peve.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 Peve.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

peve.jp

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