6.8 sec in total
858 ms
5.7 sec
287 ms
Welcome to paperme.jp homepage info - get ready to check PAPER ME best content right away, or after learning these important things about paperme.jp
Visit paperme.jpWe analyzed Paperme.jp page load time and found that the first response time was 858 ms and then it took 6 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
paperme.jp performance score
name
value
score
weighting
Value3.5 s
34/100
10%
Value6.8 s
7/100
25%
Value6.5 s
39/100
10%
Value20 ms
100/100
30%
Value0.009
100/100
15%
Value5.8 s
67/100
10%
858 ms
319 ms
620 ms
24 ms
335 ms
Our browser made a total of 51 requests to load all elements on the main page. We found that 12% of them (6 requests) were addressed to the original Paperme.jp, 59% (30 requests) were made to Img14.shop-pro.jp and 8% (4 requests) were made to Img12.shop-pro.jp. The less responsive or slowest element that took the longest time to load (2 sec) relates to the external source Img14.shop-pro.jp.
Page size can be reduced by 204.5 kB (35%)
582.2 kB
377.7 kB
In fact, the total size of Paperme.jp main page is 582.2 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. 20% of websites need less resources to load. Images take 286.2 kB which makes up the majority of the site volume.
Potential reduce by 11.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 11.1 kB or 70% of the original size.
Potential reduce by 853 B
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. PAPER ME images are well optimized though.
Potential reduce by 175.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 175.8 kB or 68% of the original size.
Potential reduce by 16.7 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. Paperme.jp needs all CSS files to be minified and compressed as it can save up to 16.7 kB or 80% of the original size.
Number of requests can be reduced by 15 (30%)
50
35
The browser has sent 50 CSS, Javascripts, AJAX and image requests in order to completely render the main page of PAPER ME. 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 as a result speed up the page load time.
www.paperme.jp
858 ms
cross-border-cart.css
319 ms
index.css
620 ms
jquery.min.js
24 ms
gmo_header.js.php
335 ms
gmo_header.css.php
332 ms
cart.js
341 ms
product_stock.js
351 ms
li.php
337 ms
li.php
322 ms
shopbell_bannerS.gif
525 ms
lapping88_31.gif
539 ms
body_bg.jpg
452 ms
logo.jpg
434 ms
deliv_free.jpg
394 ms
info_cart.jpg
285 ms
info_login.jpg
340 ms
info_new.jpg
307 ms
gnavi01.jpg
570 ms
gnavi02.jpg
733 ms
gnavi03.jpg
685 ms
gnavi04.jpg
618 ms
gnavi05.jpg
1002 ms
search_btn_off.gif
694 ms
top01.jpg
1288 ms
top02.jpg
1043 ms
top03.jpg
1158 ms
top04.jpg
1135 ms
top05.jpg
1590 ms
tit_bg.jpg
1273 ms
box_bg.jpg
1322 ms
line02.jpg
1367 ms
menu_bg.jpg
1391 ms
tit_type.jpg
1577 ms
arrow02.gif
1596 ms
tit_color.jpg
1594 ms
tit_size.jpg
1744 ms
bana_mobile.jpg
1814 ms
bana_mm.jpg
2009 ms
page_top.jpg
1857 ms
arrow01.jpg
1865 ms
shopbell_bannerS.gif
536 ms
secure.shop-pro.jp
510 ms
jquery-1.6.4.min.js
1083 ms
easyXDM.min.js
474 ms
gmohd_logo2.gif
179 ms
login.gif
179 ms
regist.gif
178 ms
gmohd_bg.gif
5 ms
checkSession.do
976 ms
easyXDM.js
1003 ms
paperme.jp accessibility score
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
Image elements do not have [alt] attributes
<input type="image"> elements do not have [alt] text
Form elements do not have associated labels
Links do not have a discernible name
paperme.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
paperme.jp SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
JA
JA
EUC-JP
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Paperme.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 Paperme.jp main page’s claimed encoding is euc-jp. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
paperme.jp
Open Graph description is not detected on the main page of PAPER ME. 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: