11.3 sec in total
517 ms
10.5 sec
318 ms
Click here to check amazing Itempost content for Japan. Otherwise, check out these important facts you probably never knew about itempost.jp
通販専門ショッピング検索サイト。楽しく賢く買うなら日本最大級の商品検索サイト「アイテムポスト」で!お取り寄せ、ギフト、送料無料の商品など、たくさんの商品の中からお買い物ができます。
Visit itempost.jpWe analyzed Itempost.jp page load time and found that the first response time was 517 ms and then it took 10.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
itempost.jp performance score
name
value
score
weighting
Value6.7 s
2/100
10%
Value7.8 s
3/100
25%
Value12.1 s
3/100
10%
Value660 ms
45/100
30%
Value0.614
10/100
15%
Value17.7 s
4/100
10%
517 ms
1639 ms
318 ms
337 ms
846 ms
Our browser made a total of 87 requests to load all elements on the main page. We found that 70% of them (61 requests) were addressed to the original Itempost.jp, 3% (3 requests) were made to Gigaplus.makeshop.jp and 3% (3 requests) were made to Cache.img.gmo.jp. The less responsive or slowest element that took the longest time to load (6.7 sec) belongs to the original domain Itempost.jp.
Page size can be reduced by 361.0 kB (14%)
2.5 MB
2.2 MB
In fact, the total size of Itempost.jp main page is 2.5 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. 45% of websites need less resources to load. Images take 2.1 MB which makes up the majority of the site volume.
Potential reduce by 59.1 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 59.1 kB or 82% of the original size.
Potential reduce by 64.6 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. Itempost images are well optimized though.
Potential reduce by 180.1 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 180.1 kB or 61% of the original size.
Potential reduce by 57.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. Itempost.jp needs all CSS files to be minified and compressed as it can save up to 57.2 kB or 79% of the original size.
Number of requests can be reduced by 22 (27%)
83
61
The browser has sent 83 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Itempost. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
itempost.jp
517 ms
www.itempost.jp
1639 ms
import.css
318 ms
responsive.css
337 ms
jquery.js
846 ms
thickbox.js
338 ms
jquery.linkwrapper-1.0.3.js
350 ms
yuga.js
466 ms
heightLine.js
473 ms
ld.js
22 ms
top.css
500 ms
class.horinaja.jquery.js
504 ms
jquery.slides.min.js
524 ms
slick.css
621 ms
slick-theme.css
628 ms
slick.min.js
833 ms
reset.css
361 ms
contents.css
1083 ms
common.css
467 ms
module.css
472 ms
thickbox.css
529 ms
015000000283.jpg
923 ms
1_006001000001.jpg
1217 ms
000000000110.jpg
918 ms
000000000216.jpg
1399 ms
001000000011.jpg
865 ms
000000003984.jpg
792 ms
000000000388.jpg
1162 ms
001000000002.jpg
831 ms
037001000100.jpg
672 ms
041000000001.jpg
1436 ms
0000000490512.jpg
1506 ms
gmologo.png
62 ms
logo_2014_winter.png
178 ms
pNav.gif
180 ms
search.gif
180 ms
btnSearch.gif
178 ms
rankingTitle.png
183 ms
attentionTitle.gif
176 ms
itemListBg.gif
325 ms
index.php
695 ms
thisShopBtn.gif
336 ms
index.php
921 ms
index.php
717 ms
index.php
907 ms
index.php
843 ms
index.php
873 ms
index.php
1371 ms
popshopTitle.gif
887 ms
index.php
1997 ms
index.php
1748 ms
index.php
1595 ms
interiorwest.jpg
6708 ms
index.php
1520 ms
index.php
1891 ms
checkTitle.gif
1692 ms
categoryTitle.gif
1766 ms
newitemTitle.gif
1861 ms
index.php
2292 ms
index.php
3646 ms
index.php
2577 ms
index.php
2962 ms
index.php
3039 ms
tagCloudTitle.gif
3043 ms
trendKeywordTitle.gif
2747 ms
btnStart.gif
2917 ms
tokutokuThanksDay.gif
3086 ms
prTitle.png
3118 ms
2_036001000108.jpg
864 ms
1_022001000014.jpg
1050 ms
internet_for_everyone.png
111 ms
000000000387.jpg
1113 ms
event
45 ms
ga.js
66 ms
plusone.js
95 ms
pagetop.gif
3150 ms
event
418 ms
footerstyle.css
74 ms
__utm.gif
13 ms
collect
71 ms
cb=gapi.loaded_0
13 ms
slick.woff
3625 ms
footerBg.gif
3087 ms
icon_arrow.gif
3109 ms
loadingAnimation.gif
3187 ms
ajax-loader.gif
3256 ms
dis.aspx
447 ms
itempost.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
ARIA input fields do not have accessible names
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
Form elements do not have associated labels
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>).
itempost.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
itempost.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
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 Itempost.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 Itempost.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.
itempost.jp
Open Graph data is detected on the main page of Itempost. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: