Tools & Wizards About Us
inpex.co.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

inpex.co.jp

INPEX

Page Load Speed

7.5 sec in total

First Response

353 ms

Resources Loaded

6 sec

Page Rendered

1.1 sec

inpex.co.jp screenshot

About Website

Click here to check amazing INPEX content for Japan. Otherwise, check out these important facts you probably never knew about inpex.co.jp

INPEXのオフィシャルWebサイトです。私たちは、世界のエネルギー需要に応え、多様なエネルギーをよりクリーンな形で安定的かつ効率的に供給することにより、SDGsの目指すエネルギー、環境、経済発展、社会開発等に貢献してまいります。

Visit inpex.co.jp

Key Findings

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

Performance Metrics

inpex.co.jp performance score

0

Network Requests Diagram

inpex.co.jp

353 ms

inpex.co.jp

696 ms

www.inpex.co.jp

346 ms

base.css

205 ms

slick.css

236 ms

Our browser made a total of 89 requests to load all elements on the main page. We found that 84% of them (75 requests) were addressed to the original Inpex.co.jp, 4% (4 requests) were made to Googletagmanager.com and 3% (3 requests) were made to Rsv.dga.jp. The less responsive or slowest element that took the longest time to load (3 sec) belongs to the original domain Inpex.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 307.0 kB (4%)

Content Size

7.2 MB

After Optimization

6.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Inpex.co.jp main page is 7.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. 70% of websites need less resources to load. Images take 6.8 MB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 70.7 kB

  • Original 80.9 kB
  • After minification 62.4 kB
  • After compression 10.2 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 18.5 kB, which is 23% 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 70.7 kB or 87% of the original size.

Image Optimization

-2%

Potential reduce by 122.6 kB

  • Original 6.8 MB
  • After minification 6.7 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. INPEX images are well optimized though.

JavaScript Optimization

-39%

Potential reduce by 91.5 kB

  • Original 234.1 kB
  • After minification 232.9 kB
  • After compression 142.5 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 91.5 kB or 39% of the original size.

CSS Optimization

-37%

Potential reduce by 22.2 kB

  • Original 59.3 kB
  • After minification 58.9 kB
  • After compression 37.2 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. Inpex.co.jp needs all CSS files to be minified and compressed as it can save up to 22.2 kB or 37% of the original size.

Requests Breakdown

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

Requests Now

85

After Optimization

61

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

inpex.co.jp

inpex.co.jp

353 ms

inpex.co.jp

inpex.co.jp

696 ms

www.inpex.co.jp

www.inpex.co.jp

346 ms

base.css

base.css

205 ms

slick.css

slick.css

236 ms

colorbox.css

colorbox.css

237 ms

slick-theme.css

slick-theme.css

214 ms

layout_pc.css

layout_pc.css

243 ms

layout_sp.css

layout_sp.css

237 ms

parts_pc.css

parts_pc.css

406 ms

parts_sp.css

parts_sp.css

421 ms

top.css

top.css

431 ms

jquery.js

jquery.js

447 ms

vue.min.js

vue.min.js

464 ms

slick.js

slick.js

447 ms

jquery.colorbox.js

jquery.colorbox.js

603 ms

js.cookie.min.js

js.cookie.min.js

614 ms

common.js

common.js

638 ms

top.js

top.js

642 ms

fbevents.js

fbevents.js

197 ms

gtm.js

gtm.js

242 ms

hdr_logo01.png

hdr_logo01.png

789 ms

hdr_font_ic01_on.png

hdr_font_ic01_on.png

793 ms

hdr_font_ic02_off.png

hdr_font_ic02_off.png

793 ms

index_im01.jpg

index_im01.jpg

314 ms

hdr_nav_company_im02.jpg

hdr_nav_company_im02.jpg

792 ms

hdr_nav_company_im03.png

hdr_nav_company_im03.png

461 ms

hdr_nav_business_im01.jpg

hdr_nav_business_im01.jpg

878 ms

hdr_nav_business_im02.jpg

hdr_nav_business_im02.jpg

793 ms

hdr_nav_business_im03.jpg

hdr_nav_business_im03.jpg

1196 ms

hdr_nav_ir_im03.jpg

hdr_nav_ir_im03.jpg

1009 ms

hdr_nav_ir_im02.jpg

hdr_nav_ir_im02.jpg

1368 ms

hdr_nav_ir_im01.jpg

hdr_nav_ir_im01.jpg

1188 ms

hdr_nav_csr_im01.jpg

hdr_nav_csr_im01.jpg

1197 ms

hdr_search_ic01.png

hdr_search_ic01.png

1079 ms

hdr_contact_ic01.png

hdr_contact_ic01.png

1205 ms

hdr_global_ic01.png

hdr_global_ic01.png

1460 ms

index_im18_01.jpg

index_im18_01.jpg

1792 ms

index_im18_05.jpg

index_im18_05.jpg

1603 ms

index_bt01.png

index_bt01.png

1763 ms

index_im18_06.jpg

index_im18_06.jpg

1639 ms

index_bt02.png

index_bt02.png

1913 ms

index_im18_02.jpg

index_im18_02.jpg

2043 ms

index_im18_03.jpg

index_im18_03.jpg

2210 ms

index_im18_04.jpg

index_im18_04.jpg

2162 ms

index_ic04.png

index_ic04.png

2137 ms

index_im02.png

index_im02.png

2198 ms

index_im21.jpg

index_im21.jpg

2109 ms

index_im22.jpg

index_im22.jpg

2435 ms

index_im23.jpg

index_im23.jpg

2656 ms

index_im24.jpg

index_im24.jpg

2522 ms

index_im25.jpg

index_im25.jpg

2364 ms

index_im03_01-r2x.jpg

index_im03_01-r2x.jpg

2584 ms

index_im03_02-r2x.jpg

index_im03_02-r2x.jpg

2774 ms

index_im03.jpg

index_im03.jpg

2967 ms

index_im26.jpg

index_im26.jpg

2820 ms

uwt.js

uwt.js

131 ms

search_tool_n1.js

search_tool_n1.js

1045 ms

index_im27.jpg

index_im27.jpg

2664 ms

js

js

40 ms

js

js

168 ms

js

js

165 ms

analytics.js

analytics.js

155 ms

news_parts.json

news_parts.json

2476 ms

adsct

adsct

570 ms

adsct

adsct

489 ms

news.json

news.json

2567 ms

collect

collect

316 ms

slick.woff

slick.woff

2512 ms

index_im07.jpg

index_im07.jpg

2204 ms

index_im08.png

index_im08.png

2559 ms

index_im09.png

index_im09.png

2402 ms

index_im10.png

index_im10.png

2379 ms

collect

collect

16 ms

index_im11.png

index_im11.png

2511 ms

index_im04.jpg

index_im04.jpg

2237 ms

cmn_link_blank_ic01.png

cmn_link_blank_ic01.png

2292 ms

i_search_assist_n1.js

i_search_assist_n1.js

1338 ms

ac.css

ac.css

500 ms

index_im28.jpg

index_im28.jpg

2469 ms

index_im19.jpg

index_im19.jpg

2255 ms

index_im20.jpg

index_im20.jpg

2515 ms

index_im13.jpg

index_im13.jpg

2532 ms

index_im16.jpg

index_im16.jpg

2217 ms

cmn_sns_ic01.svg

cmn_sns_ic01.svg

2300 ms

cmn_sns_ic02.png

cmn_sns_ic02.png

2289 ms

ajax-loader.gif

ajax-loader.gif

2142 ms

index_ic01.png

index_ic01.png

2092 ms

cmn_link_pdf_ic01.png

cmn_link_pdf_ic01.png

883 ms

SEO Factors

inpex.co.jp SEO score

0

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 Inpex.co.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 Inpex.co.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

inpex.co.jp

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