6.7 sec in total
895 ms
5.4 sec
368 ms
Click here to check amazing Kepco content for Japan. Otherwise, check out these important facts you probably never knew about kepco.jp
関西電力の個人・法人総合トップページ。これからは、電気も。ガスも。関西電力は、あなたの暮らしの頼れる力であるために、選ばれるエネルギー会社を目指します。
Visit kepco.jpWe analyzed Kepco.jp page load time and found that the first response time was 895 ms and then it took 5.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
kepco.jp performance score
name
value
score
weighting
Value6.1 s
3/100
10%
Value18.2 s
0/100
25%
Value11.3 s
5/100
10%
Value450 ms
63/100
30%
Value0.123
83/100
15%
Value14.8 s
8/100
10%
895 ms
335 ms
361 ms
366 ms
384 ms
Our browser made a total of 98 requests to load all elements on the main page. We found that 90% of them (88 requests) were addressed to the original Kepco.jp, 3% (3 requests) were made to Google-analytics.com and 1% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (2.8 sec) belongs to the original domain Kepco.jp.
Page size can be reduced by 409.6 kB (19%)
2.2 MB
1.8 MB
In fact, the total size of Kepco.jp main page is 2.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. 55% of websites need less resources to load. Images take 1.7 MB which makes up the majority of the site volume.
Potential reduce by 37.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. This page needs HTML code to be minified as it can gain 9.1 kB, which is 19% 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 37.3 kB or 80% of the original size.
Potential reduce by 83.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. Kepco images are well optimized though.
Potential reduce by 151.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 151.8 kB or 64% of the original size.
Potential reduce by 137.0 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. Kepco.jp needs all CSS files to be minified and compressed as it can save up to 137.0 kB or 86% of the original size.
Number of requests can be reduced by 36 (38%)
95
59
The browser has sent 95 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Kepco. 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 8 to 1 for CSS and as a result speed up the page load time.
kepco.jp
895 ms
default.css
335 ms
cmn_layout.css
361 ms
cmn_style.css
366 ms
cmn_parts.css
384 ms
cmn_parts_over.css
383 ms
jquery.bxslider.css
411 ms
sc.index.css
500 ms
jquery.js
887 ms
common.js
540 ms
jquery.bxslider.js
568 ms
jquery.matchHeight-min.js
565 ms
sc.common.js
612 ms
index.css
664 ms
analytics.js
15 ms
bg_body02.gif
1420 ms
banner_sample_l.ashx
352 ms
banner_sample_m.ashx
383 ms
btn_campaign_close01.ashx
201 ms
logo.png
200 ms
txt_discription01.png
199 ms
txt_header_links01.png
361 ms
txt_header_links02.png
365 ms
txt_header_links03.png
385 ms
txt_header_links04.png
519 ms
gnavi_txt01.ashx
565 ms
gnavi_txt02.ashx
564 ms
gnavi_txt03.ashx
576 ms
gnavi_txt04.ashx
577 ms
gnavi_txt05.ashx
696 ms
gnavi_txt06.ashx
854 ms
logo_sp01.ashx
872 ms
btn_sp_navi01.ashx
916 ms
hapie_point_1.ashx
1851 ms
move.ashx
1586 ms
esma10.ashx
2125 ms
kaketsuke_service.ashx
1631 ms
kurashi20150118.ashx
1860 ms
liberalization.ashx
2237 ms
eco_project.ashx
2264 ms
hapiemiruden_1.ashx
2382 ms
btn_index01.ashx
2043 ms
btn_index02.ashx
2062 ms
btn_index03.ashx
2235 ms
btn_index04.ashx
2259 ms
btn_index05.ashx
2313 ms
btn_index06.ashx
2428 ms
btn_index07.ashx
2451 ms
btn_index08.ashx
2461 ms
centbnr_left01.ashx
2446 ms
%E3%82%B3%E3%83%94%E3%83%BC%20-%20centbnr_left01.ashx
2502 ms
collect
60 ms
gtm.js
57 ms
s_retargeting.js
562 ms
collect
14 ms
set
313 ms
2829 ms
centbnr_center01.ashx
2375 ms
top_lnavi01.ashx
2426 ms
collect
74 ms
top_lnavi02.ashx
2321 ms
top_lnavi03.ashx
2304 ms
btn_l-navi.ashx
2336 ms
img_index08.ashx
2388 ms
img_index09.ashx
2440 ms
img_index10.ashx
2343 ms
tit_login_mod01.png
2312 ms
tit_login_mod_sp01.png
2317 ms
btn_hapie_login01.png
2371 ms
btn_hapie_login_sp01.png
2433 ms
btn_hapie_regist01.png
2352 ms
conversion.js
26 ms
29 ms
35 ms
btn_hapie_regist_sp01.png
2226 ms
bnr_cm_mirudenhen01.ashx
2387 ms
ico_exlink01.ashx
2225 ms
bnr_cmn08.ashx
1787 ms
btn_pagetop03_no.png
1606 ms
img_twitter01.png
1604 ms
img_facebook01.png
1422 ms
img_youtube01.png
1456 ms
bg_gnavi01.png
1316 ms
ico_index02.png
1328 ms
ico_index05.png
1295 ms
ico_index04.png
1200 ms
bg_cmn_line01.png
1246 ms
ico_login_input01.png
1233 ms
ico_login_input02.png
1261 ms
ico_cmn_arrow01.png
1251 ms
ico_cmn_arrow02.png
1225 ms
ico_info01.png
1186 ms
ico_info02.png
1239 ms
ico_info03.png
1217 ms
ico_info04.png
1229 ms
ico_footer_links01.png
1241 ms
btn_pagetop03_on.png
1223 ms
bg_gnavi_cuurent01.png
1168 ms
kepco.jp accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
button, link, and menuitem elements do not have accessible names.
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
Buttons do not have an accessible name
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
kepco.jp 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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
kepco.jp SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Kepco.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 Kepco.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.
kepco.jp
Open Graph description is not detected on the main page of Kepco. 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: