Tools & Wizards About Us
paj.gr.jp screenshot

Report Summary

  • 53

    Performance

    Renders faster than
    71% of other websites

  • 68

    Accessibility

    Visual factors better than
    that of 33% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 91

    SEO

    Google-friendlier than
    71% of websites

paj.gr.jp

石油連盟

Page Load Speed

7.4 sec in total

First Response

621 ms

Resources Loaded

6.5 sec

Page Rendered

328 ms

paj.gr.jp screenshot

About Website

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

石油連盟は、わが国の石油精製・元売会社、すなわち原油の輸入、精製、石油製品の全国的な販売を行っている企業の団体として創立された基幹的産業団体です。

Visit paj.gr.jp

Key Findings

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

Performance Metrics

paj.gr.jp performance score

53

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

39/100

10%

LCP (Largest Contentful Paint)

Value6.1 s

12/100

25%

SI (Speed Index)

Value6.0 s

47/100

10%

TBT (Total Blocking Time)

Value180 ms

92/100

30%

CLS (Cumulative Layout Shift)

Value0.169

70/100

15%

TTI (Time to Interactive)

Value8.6 s

37/100

10%

Network Requests Diagram

paj.gr.jp

621 ms

jquery.min.js

483 ms

jquery.easing-1.3.js

324 ms

common.js

331 ms

common_fix_3.css

355 ms

Our browser made a total of 86 requests to load all elements on the main page. We found that 98% of them (84 requests) were addressed to the original Paj.gr.jp, 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.9 sec) belongs to the original domain Paj.gr.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 217.8 kB (23%)

Content Size

927.3 kB

After Optimization

709.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Paj.gr.jp main page is 927.3 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 647.4 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 28.0 kB

  • Original 33.5 kB
  • After minification 22.9 kB
  • After compression 5.4 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 10.5 kB, which is 32% 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 28.0 kB or 84% of the original size.

Image Optimization

-2%

Potential reduce by 13.5 kB

  • Original 647.4 kB
  • After minification 633.9 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. Paj images are well optimized though.

JavaScript Optimization

-67%

Potential reduce by 121.5 kB

  • Original 182.4 kB
  • After minification 147.8 kB
  • After compression 60.9 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 121.5 kB or 67% of the original size.

CSS Optimization

-85%

Potential reduce by 54.8 kB

  • Original 64.2 kB
  • After minification 52.4 kB
  • After compression 9.4 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. Paj.gr.jp needs all CSS files to be minified and compressed as it can save up to 54.8 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 23 (27%)

Requests Now

85

After Optimization

62

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

paj.gr.jp

paj.gr.jp

621 ms

jquery.min.js

jquery.min.js

483 ms

jquery.easing-1.3.js

jquery.easing-1.3.js

324 ms

common.js

common.js

331 ms

common_fix_3.css

common_fix_3.css

355 ms

rwd.css

rwd.css

354 ms

rwd.js

rwd.js

363 ms

jquery.bxslider.js

jquery.bxslider.js

837 ms

jquery.bxslider.css

jquery.bxslider.css

659 ms

mustache.js

mustache.js

681 ms

flexibleSearch.js

flexibleSearch.js

692 ms

flexibleSearch-config.js

flexibleSearch-config.js

715 ms

ga.js

ga.js

31 ms

bg_site_header.gif

bg_site_header.gif

356 ms

__utm.gif

__utm.gif

12 ms

bg_site_body.gif

bg_site_body.gif

323 ms

bg_site_header_2.gif

bg_site_header_2.gif

351 ms

btn_gnav.png

btn_gnav.png

353 ms

logo.gif

logo.gif

365 ms

banner_fuel.gif

banner_fuel.gif

385 ms

slider_img01.jpg

slider_img01.jpg

1141 ms

slider_img02.jpg

slider_img02.jpg

1199 ms

slider_img03.jpg

slider_img03.jpg

988 ms

slider_img04.jpg

slider_img04.jpg

1343 ms

slider_img01_thumb.jpg

slider_img01_thumb.jpg

701 ms

slider_img02_thumb.jpg

slider_img02_thumb.jpg

746 ms

slider_img03_thumb.jpg

slider_img03_thumb.jpg

1063 ms

slider_img04_thumb.jpg

slider_img04_thumb.jpg

1079 ms

slider_img01.jpg

slider_img01.jpg

1527 ms

slider_img02.jpg

slider_img02.jpg

1736 ms

slider_img03.jpg

slider_img03.jpg

1612 ms

slider_img04.jpg

slider_img04.jpg

1865 ms

hd_index_latest.gif

hd_index_latest.gif

1541 ms

hd_index_latest_rss.gif

hd_index_latest_rss.gif

1682 ms

title_news_on.png

title_news_on.png

1856 ms

icon_index_pressconferences.gif

icon_index_pressconferences.gif

1873 ms

icon_index_topics.gif

icon_index_topics.gif

1964 ms

hd_index_statis.gif

hd_index_statis.gif

2066 ms

title_statis_off.png

title_statis_off.png

2056 ms

hd_index_old.gif

hd_index_old.gif

2207 ms

hd_index_contents.gif

hd_index_contents.gif

2216 ms

hd_index_contents_about.gif

hd_index_contents_about.gif

2231 ms

hd_index_contents_petro.gif

hd_index_contents_petro.gif

2340 ms

hd_index_contents_data.gif

hd_index_contents_data.gif

2405 ms

hd_index_site.gif

hd_index_site.gif

2426 ms

title_links_off.png

title_links_off.png

2535 ms

pagetop.png

pagetop.png

2557 ms

label_search.gif

label_search.gif

2567 ms

btn_search.gif

btn_search.gif

2687 ms

btn_search.png

btn_search.png

2741 ms

menu_global.gif

menu_global.gif

2877 ms

btn_banner_1.gif

btn_banner_1.gif

2571 ms

btn_banner_6.gif

btn_banner_6.gif

2533 ms

btn_banner_2.gif

btn_banner_2.gif

2604 ms

btn_banner_3.gif

btn_banner_3.gif

2726 ms

btn_banner_4.gif

btn_banner_4.gif

2709 ms

btn_banner_5.gif

btn_banner_5.gif

2521 ms

banner_earthquake.gif

banner_earthquake.gif

2490 ms

bg_index_latest.gif

bg_index_latest.gif

2491 ms

arrow2.gif

arrow2.gif

2209 ms

line_dashed.gif

line_dashed.gif

2339 ms

bg_contents_area_1column.gif

bg_contents_area_1column.gif

2292 ms

arrow2_green.gif

arrow2_green.gif

2386 ms

arrow2_orange.gif

arrow2_orange.gif

2244 ms

arrow2_pink.gif

arrow2_pink.gif

2108 ms

banner_16.gif

banner_16.gif

2224 ms

banner_4.gif

banner_4.gif

2182 ms

banner_6.gif

banner_6.gif

2153 ms

banner_5.gif

banner_5.gif

2181 ms

banner_8.gif

banner_8.gif

2088 ms

banner_1.gif

banner_1.gif

2127 ms

banner_18.gif

banner_18.gif

2252 ms

banner_2.gif

banner_2.gif

2164 ms

banner_30.gif

banner_30.gif

2098 ms

banner_25.gif

banner_25.gif

2198 ms

banner_11.gif

banner_11.gif

2092 ms

banner_12.gif

banner_12.gif

2105 ms

banner_7.gif

banner_7.gif

2260 ms

banner_10.gif

banner_10.gif

2144 ms

banner_evss.gif

banner_evss.gif

2067 ms

banner_20.gif

banner_20.gif

2174 ms

banner_27.jpg

banner_27.jpg

2091 ms

banner_28.gif

banner_28.gif

2126 ms

bg_site_footer.gif

bg_site_footer.gif

2242 ms

bx_loader.gif

bx_loader.gif

2110 ms

print.css

print.css

186 ms

Accessibility Review

paj.gr.jp accessibility score

68

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

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

<input type="image"> elements do not have [alt] text

High

Form elements do not have associated labels

High

Links do not have a discernible name

Best Practices

paj.gr.jp best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

paj.gr.jp SEO score

91

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 Paj.gr.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 Paj.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

paj.gr.jp

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