Tools & Wizards About Us
e-nenpi.com screenshot

Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 61% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 89

    SEO

    Google-friendlier than
    66% of websites

e-nenpi.com

燃費ランキング・ガソリン価格・車種情報の共有コミュニティ - e燃費

Page Load Speed

5.8 sec in total

First Response

918 ms

Resources Loaded

4.4 sec

Page Rendered

493 ms

e-nenpi.com screenshot

About Website

Welcome to e-nenpi.com homepage info - get ready to check E Nenpi best content for Japan right away, or after learning these important things about e-nenpi.com

実燃費による燃費ランキング、ガソリン価格、車種情報、車レビューを62万人のe燃費会員と共有するコミュニティ・サイトです。車選びの指標を提供し、エコカーライフを支援します。

Visit e-nenpi.com

Key Findings

We analyzed E-nenpi.com page load time and found that the first response time was 918 ms and then it took 4.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

e-nenpi.com performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

25/100

10%

LCP (Largest Contentful Paint)

Value9.8 s

0/100

25%

SI (Speed Index)

Value11.5 s

5/100

10%

TBT (Total Blocking Time)

Value1,190 ms

21/100

30%

CLS (Cumulative Layout Shift)

Value0.195

63/100

15%

TTI (Time to Interactive)

Value19.2 s

2/100

10%

Network Requests Diagram

e-nenpi.com

918 ms

common.css

345 ms

header.css

495 ms

jquery.min.js

25 ms

jquery.easing.1.3.js

517 ms

Our browser made a total of 94 requests to load all elements on the main page. We found that 67% of them (63 requests) were addressed to the original E-nenpi.com, 24% (23 requests) were made to Image.e-nenpi.com and 1% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (1.6 sec) relates to the external source Image.e-nenpi.com.

Page Optimization Overview & Recommendations

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

Content Size

873.1 kB

After Optimization

760.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of E-nenpi.com main page is 873.1 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 40% of websites need less resources to load. Images take 433.2 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 91.8 kB

  • Original 111.3 kB
  • After minification 105.8 kB
  • After compression 19.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. 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 91.8 kB or 82% of the original size.

Image Optimization

-4%

Potential reduce by 16.4 kB

  • Original 433.2 kB
  • After minification 416.8 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. E Nenpi images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 2.2 kB

  • Original 274.4 kB
  • After minification 274.4 kB
  • After compression 272.2 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. This website has mostly compressed JavaScripts.

CSS Optimization

-5%

Potential reduce by 2.6 kB

  • Original 54.2 kB
  • After minification 54.2 kB
  • After compression 51.6 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. E-nenpi.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 24 (26%)

Requests Now

92

After Optimization

68

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

e-nenpi.com

e-nenpi.com

918 ms

common.css

common.css

345 ms

header.css

header.css

495 ms

jquery.min.js

jquery.min.js

25 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

517 ms

fixHeight.js

fixHeight.js

599 ms

common.js

common.js

599 ms

common.js

common.js

612 ms

gpt.js

gpt.js

96 ms

track_banners_init.js

track_banners_init.js

27 ms

style.css

style.css

646 ms

style.css

style.css

659 ms

highcharts.js

highcharts.js

1109 ms

jquery.masonry.min.js

jquery.masonry.min.js

798 ms

jquery.freetile.min.js

jquery.freetile.min.js

798 ms

top_script.js

top_script.js

815 ms

zocial.css

zocial.css

1061 ms

cx.js

cx.js

49 ms

apstag.js

apstag.js

48 ms

gtm.js

gtm.js

137 ms

pubads_impl.js

pubads_impl.js

46 ms

1613.jpg

1613.jpg

946 ms

header_logo.png

header_logo.png

226 ms

menu_bg.png

menu_bg.png

227 ms

234 ms

icon_star_4.gif

icon_star_4.gif

224 ms

badge_no1.png

badge_no1.png

226 ms

badge_no2.png

badge_no2.png

314 ms

badge_no3.png

badge_no3.png

329 ms

gs_brand02.png

gs_brand02.png

343 ms

gs_ico_self.gif

gs_ico_self.gif

409 ms

gs_brand1000.png

gs_brand1000.png

409 ms

gs_ico_24h.gif

gs_ico_24h.gif

430 ms

gs_brand21.png

gs_brand21.png

517 ms

gs_ico_maintenance.gif

gs_ico_maintenance.gif

494 ms

gs_ico_full.png

gs_ico_full.png

512 ms

gs_brand09.png

gs_brand09.png

611 ms

ev_stand_search.png

ev_stand_search.png

607 ms

enenpiaward2023-2024-1.png

enenpiaward2023-2024-1.png

628 ms

sp_app_banner.png

sp_app_banner.png

657 ms

705 ms

hydrogen_station.png

hydrogen_station.png

719 ms

pagetop.gif

pagetop.gif

806 ms

footer_logo.gif

footer_logo.gif

814 ms

2419.jpg

2419.jpg

944 ms

2412.jpg

2412.jpg

949 ms

1619.jpg

1619.jpg

1039 ms

2404.jpg

2404.jpg

1039 ms

2216.jpg

2216.jpg

1057 ms

457.jpg

457.jpg

1113 ms

586.jpg

586.jpg

1114 ms

2022999_s.jpg

2022999_s.jpg

1119 ms

2022991_s.jpg

2022991_s.jpg

1226 ms

2022985_s.jpg

2022985_s.jpg

1232 ms

2022945_s.jpg

2022945_s.jpg

1237 ms

2022776_s.jpg

2022776_s.jpg

1284 ms

2023013_s.jpg

2023013_s.jpg

1283 ms

2021678_s.jpg

2021678_s.jpg

1291 ms

2022918_s.jpg

2022918_s.jpg

1423 ms

002thumb.JPG

002thumb.JPG

1429 ms

001thumb.jpeg

001thumb.jpeg

1634 ms

002thumb.JPG

002thumb.JPG

1622 ms

006thumb.JPG

006thumb.JPG

1625 ms

bg_container.png

bg_container.png

785 ms

bg_gadget_sprite.png

bg_gadget_sprite.png

1432 ms

arrow_02.gif

arrow_02.gif

833 ms

number.png

number.png

880 ms

number_yen.png

number_yen.png

963 ms

2281.jpg

2281.jpg

1420 ms

2291.jpg

2291.jpg

1579 ms

2311.jpg

2311.jpg

1586 ms

e-nenpi.ttf

e-nenpi.ttf

976 ms

e-nenpi.ttf

e-nenpi.ttf

994 ms

app.png

app.png

975 ms

bg_unit680_btm.png

bg_unit680_btm.png

1044 ms

ttl_contents_sprite.png

ttl_contents_sprite.png

1122 ms

bg_unit680.gif

bg_unit680.gif

1140 ms

imagemask_76_50.png

imagemask_76_50.png

1144 ms

btn_sprite.png

btn_sprite.png

1275 ms

bg_unit_login.gif

bg_unit_login.gif

1109 ms

bg_unit_login_btm.png

bg_unit_login_btm.png

1182 ms

bg_unit300_btm.png

bg_unit300_btm.png

1203 ms

bg_unit300.gif

bg_unit300.gif

1202 ms

bg_comment_top.gif

bg_comment_top.gif

1304 ms

mYLJVpiB6UaowawQ5qDWwhmYZ8ICnEXCEixCYQWWgXAOVsKOtPkAmoBkpAAAAAABULvfUwAA

mYLJVpiB6UaowawQ5qDWwhmYZ8ICnEXCEixCYQWWgXAOVsKOtPkAmoBkpAAAAAABULvfUwAA

3 ms

bg_comment_btm.gif

bg_comment_btm.gif

1329 ms

bg_unit300_top.png

bg_unit300_top.png

1293 ms

footer_bg_unit1_btm.png

footer_bg_unit1_btm.png

1298 ms

footer_bg_unit1_top.png

footer_bg_unit1_top.png

1290 ms

footer_bg_unit1.gif

footer_bg_unit1.gif

1234 ms

arrow_01.gif

arrow_01.gif

1332 ms

footer_bg_unit2_top.png

footer_bg_unit2_top.png

1305 ms

footer_bg_unit2_btm.png

footer_bg_unit2_btm.png

1312 ms

footer_bg_unit2.gif

footer_bg_unit2.gif

1312 ms

Accessibility Review

e-nenpi.com accessibility score

86

Accessibility Issues

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

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

Best Practices

e-nenpi.com best practices score

67

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

e-nenpi.com SEO score

89

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

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

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 E-nenpi.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 E-nenpi.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

e-nenpi.com

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