17 sec in total
545 ms
15.5 sec
892 ms
Click here to check amazing E Pale content for Japan. Otherwise, check out these important facts you probably never knew about e-pale.jp
通販専門ショッピング検索サイト。楽しく賢く買うなら日本最大級の商品検索サイト「イーパレ」で!お取り寄せ、ギフト、送料無料の商品など、たくさんの商品の中からお買い物ができます。
Visit e-pale.jpWe analyzed E-pale.jp page load time and found that the first response time was 545 ms and then it took 16.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
e-pale.jp performance score
name
value
score
weighting
Value5.5 s
6/100
10%
Value6.4 s
10/100
25%
Value20.8 s
0/100
10%
Value200 ms
90/100
30%
Value0.699
7/100
15%
Value24.0 s
1/100
10%
545 ms
1271 ms
751 ms
958 ms
803 ms
Our browser made a total of 167 requests to load all elements on the main page. We found that 99% of them (165 requests) were addressed to the original E-pale.jp, 1% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (4.8 sec) belongs to the original domain E-pale.jp.
Page size can be reduced by 219.9 kB (54%)
409.6 kB
189.7 kB
In fact, the total size of E-pale.jp main page is 409.6 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. 50% of websites need less resources to load. HTML takes 127.8 kB which makes up the majority of the site volume.
Potential reduce by 114.5 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 40.8 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 114.5 kB or 90% of the original size.
Potential reduce by 4.2 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. E Pale images are well optimized though.
Potential reduce by 61.3 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 61.3 kB or 59% of the original size.
Potential reduce by 39.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. E-pale.jp needs all CSS files to be minified and compressed as it can save up to 39.9 kB or 80% of the original size.
Number of requests can be reduced by 20 (12%)
164
144
The browser has sent 164 CSS, Javascripts, AJAX and image requests in order to completely render the main page of E Pale. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 7 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
e-pale.jp
545 ms
www.e-pale.jp
1271 ms
import.css
751 ms
jquery.js
958 ms
thickbox.js
803 ms
jquery.linkwrapper-1.0.3.js
832 ms
yuga.js
834 ms
heightLine.js
707 ms
horinaja.css
876 ms
top.css
907 ms
jquery.mousewheel.js
961 ms
class.horinaja.jquery.js
997 ms
reset.css
254 ms
contents.css
295 ms
common.css
313 ms
module.css
365 ms
thickbox.css
371 ms
ga.js
90 ms
logo.gif
170 ms
search.gif
161 ms
btnSearrch.jpg
171 ms
intrgratedTitle.gif
161 ms
index.php
686 ms
index.php
1039 ms
index.php
1158 ms
index.php
682 ms
index.php
878 ms
index.php
883 ms
index.php
1364 ms
newItem.gif
843 ms
index.php
1361 ms
index.php
1252 ms
index.php
1594 ms
index.php
1577 ms
index.php
1525 ms
index.php
1795 ms
trendKeywordTitle.gif
1518 ms
popsjopTitle.gif
1523 ms
popshopBottom.gif
1675 ms
cateRankTitle.gif
1682 ms
cateTitle1.gif
1684 ms
btnList.gif
1746 ms
index.php
2136 ms
index.php
2509 ms
index.php
2522 ms
index.php
2205 ms
cateTitle2.gif
1911 ms
index.php
2674 ms
index.php
2451 ms
index.php
2683 ms
index.php
2889 ms
cateTitle3.gif
2619 ms
index.php
3338 ms
index.php
3283 ms
__utm.gif
13 ms
index.php
3166 ms
index.php
3230 ms
cateTitle4.gif
2689 ms
index.php
3060 ms
index.php
2734 ms
index.php
3095 ms
index.php
3020 ms
cateTitle5.gif
2622 ms
index.php
4643 ms
index.php
2894 ms
index.php
2942 ms
index.php
2921 ms
cateTitle6.gif
2590 ms
index.php
3203 ms
index.php
2788 ms
index.php
3139 ms
index.php
2939 ms
cateTitle7.gif
2753 ms
index.php
3251 ms
index.php
3015 ms
index.php
3143 ms
index.php
3917 ms
cateTitle8.gif
3086 ms
index.php
3860 ms
index.php
3753 ms
index.php
3238 ms
index.php
3179 ms
cateTitle9.gif
3094 ms
index.php
3468 ms
index.php
3841 ms
index.php
3635 ms
index.php
3468 ms
cateTitle10.gif
3128 ms
index.php
3842 ms
index.php
3749 ms
index.php
3288 ms
index.php
3356 ms
cateTitle11.gif
3086 ms
index.php
3866 ms
index.php
3751 ms
index.php
4010 ms
index.php
3660 ms
cateTitle12.gif
3071 ms
index.php
3357 ms
index.php
3881 ms
index.php
3739 ms
index.php
3584 ms
cateTitle13.gif
3207 ms
index.php
3793 ms
index.php
3908 ms
index.php
3506 ms
index.php
3433 ms
cateTitle14.gif
3199 ms
index.php
3660 ms
index.php
3407 ms
index.php
3852 ms
index.php
3829 ms
cateTitle15.gif
2885 ms
index.php
3477 ms
index.php
3076 ms
index.php
3235 ms
index.php
3283 ms
cateTitle16.gif
3109 ms
index.php
3527 ms
index.php
3415 ms
index.php
3484 ms
index.php
2960 ms
cateTitle17.gif
2779 ms
index.php
3390 ms
index.php
3494 ms
index.php
2951 ms
index.php
3075 ms
cateTitle18.gif
2714 ms
index.php
3741 ms
index.php
3610 ms
index.php
2851 ms
index.php
3388 ms
cateTitle19.gif
2705 ms
index.php
3234 ms
index.php
3084 ms
index.php
3090 ms
index.php
3466 ms
cateTitle20.gif
2932 ms
index.php
3705 ms
index.php
3643 ms
index.php
3384 ms
index.php
3068 ms
cateTitle21.gif
2679 ms
index.php
2926 ms
index.php
4845 ms
index.php
3606 ms
index.php
3486 ms
pagetop.gif
2912 ms
bgRank01.jpg
3161 ms
bgRank02.jpg
2991 ms
bgRank03.jpg
2925 ms
bgRank04.jpg
3054 ms
bgRank05.jpg
2994 ms
bgRank06.jpg
3108 ms
bgRank07.jpg
2971 ms
bgKeyword.jpg
3049 ms
icoList.gif
2835 ms
bgPopshopRank.gif
2810 ms
icoShopRank01.gif
2758 ms
icoShopRank02.gif
2709 ms
icoShopRank03.gif
2727 ms
icoCateRank01.gif
2486 ms
icoCateRank02.gif
2556 ms
icoCateRank03.gif
2392 ms
icoCateRank04.gif
2413 ms
icon_arrow.gif
2375 ms
loadingAnimation.gif
1933 ms
e-pale.jp 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
Heading elements are not in a sequentially-descending order
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
Form elements do not have associated labels
Links do not have a discernible name
e-pale.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
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
e-pale.jp SEO score
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise E-pale.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 E-pale.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.
e-pale.jp
Open Graph description is not detected on the main page of E Pale. 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: