5.6 sec in total
569 ms
4.9 sec
154 ms
Click here to check amazing Oil Stat content for Japan. Otherwise, check out these important facts you probably never knew about oil-stat.com
日本全国のガソリン(ハイオク・レギュラー)・軽油・灯油の価格の推移を毎週発表される資源エネルギー庁の石油製品価格調査を基にグラフ化しています
Visit oil-stat.comWe analyzed Oil-stat.com page load time and found that the first response time was 569 ms and then it took 5 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
oil-stat.com performance score
name
value
score
weighting
Value3.6 s
32/100
10%
Value5.1 s
24/100
25%
Value11.6 s
5/100
10%
Value4,420 ms
0/100
30%
Value0.096
91/100
15%
Value19.8 s
2/100
10%
569 ms
910 ms
173 ms
22 ms
518 ms
Our browser made a total of 132 requests to load all elements on the main page. We found that 14% of them (19 requests) were addressed to the original Oil-stat.com, 15% (20 requests) were made to Pagead2.googlesyndication.com and 13% (17 requests) were made to Cm.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (910 ms) belongs to the original domain Oil-stat.com.
Page size can be reduced by 212.4 kB (14%)
1.6 MB
1.3 MB
In fact, the total size of Oil-stat.com main page is 1.6 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. Javascripts take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 159.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 159.9 kB or 83% of the original size.
Potential reduce by 5.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. Oil Stat images are well optimized though.
Potential reduce by 44.7 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.
Potential reduce by 2.3 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. Oil-stat.com needs all CSS files to be minified and compressed as it can save up to 2.3 kB or 34% of the original size.
Number of requests can be reduced by 82 (69%)
119
37
The browser has sent 119 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Oil Stat. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 43 to 1 for JavaScripts and as a result speed up the page load time.
oil-stat.com
569 ms
oil-stat.com
910 ms
main_scbt2.css
173 ms
jquery.min.js
22 ms
highcharts.js
518 ms
exporting.js
516 ms
raphael.js
691 ms
morris.min.js
524 ms
sp.css
531 ms
adsbygoogle.js
163 ms
show_ads.js
229 ms
script.js
529 ms
s_retargeting.js
768 ms
ga.js
132 ms
plusone.js
132 ms
bookmark_button_wo_al.js
133 ms
widgets.js
313 ms
all.js
132 ms
noteit.js
138 ms
logo.gif
201 ms
eneos.gif
201 ms
article-clipper-vert.png
200 ms
linebutton_86x20.png
201 ms
button-only.gif
135 ms
show_ads_impl.js
336 ms
rank1.png
178 ms
rank2.png
243 ms
rank3.png
285 ms
arrow02.png
284 ms
__utm.gif
151 ms
cb=gapi.loaded_0
141 ms
cb=gapi.loaded_1
140 ms
fastbutton
136 ms
all.js
134 ms
bg02.gif
243 ms
arrow01.gif
220 ms
widget_iframe.2f70fb173b9000da126c79afe2098f02.html
136 ms
134 ms
postmessageRelay
109 ms
developers.google.com
410 ms
ga-audiences
150 ms
zrt_lookup.html
79 ms
ads
876 ms
ads
577 ms
settings
121 ms
ads
828 ms
ads
497 ms
544727282-postmessagerelay.js
36 ms
rpc:shindig_random.js
22 ms
ads
110 ms
ads
246 ms
ads
792 ms
cb=gapi.loaded_0
5 ms
button.856debeac157d9669cf51e73a08fbc93.js
21 ms
embeds
34 ms
tweet_button.2f70fb173b9000da126c79afe2098f02.ja.html
31 ms
gen_204
69 ms
pixel
70 ms
5103905836670088573
53 ms
abg_lite.js
40 ms
omrhp.js
40 ms
Q12zgMmT.js
45 ms
window_focus.js
52 ms
qs_click_protection.js
60 ms
ufs_web_display.js
45 ms
icon.png
20 ms
62bHydCX.html
111 ms
pixel
272 ms
pixel
349 ms
wJiNEMIFAPB28UFvxM_UYtYFK_ILnv1_rxRzUTsn-Pg.js
200 ms
pixel
277 ms
6094436044053429679
195 ms
gen_204
208 ms
reactive_library.js
185 ms
ca-pub-4716628793208246
116 ms
activeview
118 ms
rum
79 ms
bounce
20 ms
pixel
64 ms
pixel
64 ms
rum
34 ms
ads
376 ms
activeview
158 ms
932194293485195630
97 ms
load_preloaded_resource.js
96 ms
abg_lite.js
94 ms
60efddb729a951d3495fe79f6eb41a86.js
172 ms
fullscreen_api_adapter.js
73 ms
interstitial_ad_frame.js
78 ms
feedback_grey600_24dp.png
164 ms
settings_grey600_24dp.png
165 ms
gen_204
126 ms
pixel
125 ms
16172018192069873159
123 ms
pixel
44 ms
css
68 ms
pixel
60 ms
activeview
156 ms
rum
65 ms
setuid
43 ms
pixel
44 ms
pixel
44 ms
pixel
156 ms
dv3.js
158 ms
ufs_web_display.js
39 ms
gen_204
157 ms
font
161 ms
font
162 ms
rum
116 ms
um
82 ms
ad
79 ms
um
20 ms
pixel
19 ms
sd
59 ms
pixel
20 ms
skeleton.js
121 ms
5413302062234100902
26 ms
cookie_push_onload.html
94 ms
activeview
84 ms
382696.gif
96 ms
main.19.8.511.js
64 ms
pixel
25 ms
pixel
25 ms
pixel
29 ms
pixel
23 ms
sodar
81 ms
pixel
18 ms
pixel
29 ms
sodar2.js
5 ms
runner.html
6 ms
aframe
29 ms
pixel
19 ms
oil-stat.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[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
<frame> or <iframe> elements do not have a title
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
oil-stat.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
Issues were logged in the Issues panel in Chrome Devtools
oil-stat.com SEO score
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
Document uses legible font sizes
Tap targets are not sized appropriately
![]()
JA
![]()
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Oil-stat.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 Oil-stat.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.
oil-stat.com
Open Graph data is detected on the main page of Oil Stat. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: