Access ngp.gr.jp. NGP日本自動車リサイクル事業協同組合

name

value

score

weighting

FCP (First Contentful Paint)

Value6.6 s

2/100

10%

LCP (Largest Contentful Paint)

Value7.5 s

4/100

25%

SI (Speed Index)

Value13.2 s

2/100

10%

TBT (Total Blocking Time)

Value5,010 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.179

68/100

15%

TTI (Time to Interactive)

Value28.4 s

0/100

10%

ngp.gr.jp

380 ms

ngp.gr.jp

759 ms

www.ngp.gr.jp

910 ms

reset.css

538 ms

base.css

539 ms

Our browser made a total of 72 requests to load all elements on the main page. We found that 74% of them (53 requests) were addressed to the original Ngp.gr.jp, 8% (6 requests) were made to Youtube.com and 3% (2 requests) were made to Maxcdn.bootstrapcdn.com. The less responsive or slowest element that took the longest time to load (5.7 sec) belongs to the original domain Ngp.gr.jp.

Content Size

8.8 MB

After Optimization

4.6 MB

In fact, the total size of Ngp.gr.jp main page is 8.8 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. 80% 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 8.3 MB which makes up the majority of the site volume.

HTML Optimization

-73%

Potential reduce by 20.3 kB

Original 27.7 kB
After minification 25.1 kB
After compression 7.3 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 20.3 kB or 73% of the original size.

Image Optimization

-48%

Potential reduce by 4.0 MB

Original 8.3 MB
After minification 4.3 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, Ngp needs image optimization as it can save up to 4.0 MB or 48% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-19%

Potential reduce by 48.4 kB

Original 252.2 kB
After minification 228.5 kB
After compression 203.8 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 48.4 kB or 19% of the original size.

CSS Optimization

-59%

Potential reduce by 101.5 kB

Original 172.5 kB
After minification 148.7 kB
After compression 70.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. Ngp.gr.jp needs all CSS files to be minified and compressed as it can save up to 101.5 kB or 59% of the original size.

Requests Now

After Optimization

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

Accessibility Issues

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

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

High

Links do not have a discernible name

These are opportunities to improve keyboard navigation in your application.

High

Heading elements are not in a sequentially-descending order

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

High

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

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

High

Browser errors were logged to the console

High

Page has valid source maps

Search Engine Optimization Advices

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

High

Links do not have descriptive text

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

High

Links are not crawlable

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

N/A
Encoding

UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ngp.gr.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Ngp.gr.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

ngp.gr.jp

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

Report Summary

Performance

Accessibility

Best Practices

SEO

NGP日本自動車リサイクル事業協同組合

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

ngp.gr.jp

ngp.gr.jp

www.ngp.gr.jp

reset.css

base.css

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

ngp.gr.jp

ngp.gr.jp

www.ngp.gr.jp

reset.css

base.css

menu.css

index.css

animate.css

font-awesome.min.css

jquery.bxslider.css

css

js

jquery.min.js

jquery.bxslider.js

jquery-scrollInTurn.js

analytics.js

css

SEntFgX-HT0

logo.png

logoSP.png

sdgs_logo.svg

btn_report.png

btn_report_old.png

new.png

aboutNgpBg.png

iso.png

aboutNgpDatabg.jpg

recycleBg.png

bnr_vr.jpg

recycle02Bg.png

vehicleBg.jpg

sozai99.png

sozai99sp.png

activ01Bg.jpg

activ02Bg.jpg

co2Bg.jpg

bnr_ngp_news.jpg

bnr_ngpMember.jpg

pickup01.jpg

pickup06.jpg

pickup02.jpg

pickup05.jpg

pickup03.jpg