11.1 sec in total
757 ms
10.2 sec
129 ms
Visit piebooks.com now to see the best up-to-date PIE Books content and also check out these interesting facts you probably never knew about piebooks.com
出版社 パイ インターナショナル(PIE International) 公式サイト。「魅力ある文化・優れたクリエイターと、世界との懸け橋でありたい」自分たちが感動した文化や才能を、日本と、世界と共有したい。「これって、いいよね! すごいよね!」を伝えたい。これが PIE という出版社が始まった動機であり、存在目的です。
Visit piebooks.comWe analyzed Piebooks.com page load time and found that the first response time was 757 ms and then it took 10.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.
piebooks.com performance score
name
value
score
weighting
Value3.8 s
27/100
10%
Value5.9 s
14/100
25%
Value7.8 s
23/100
10%
Value210 ms
88/100
30%
Value0.357
30/100
15%
Value7.0 s
53/100
10%
757 ms
594 ms
332 ms
351 ms
352 ms
Our browser made a total of 80 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Piebooks.com, 96% (77 requests) were made to Pie.co.jp and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (5.7 sec) relates to the external source Pie.co.jp.
Page size can be reduced by 238.7 kB (7%)
3.5 MB
3.2 MB
In fact, the total size of Piebooks.com main page is 3.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. 20% of websites need less resources to load. Images take 3.2 MB which makes up the majority of the site volume.
Potential reduce by 26.7 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 26.7 kB or 73% of the original size.
Potential reduce by 77.4 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. PIE Books images are well optimized though.
Potential reduce by 122.0 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 122.0 kB or 65% of the original size.
Potential reduce by 12.6 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. Piebooks.com needs all CSS files to be minified and compressed as it can save up to 12.6 kB or 77% of the original size.
Number of requests can be reduced by 26 (33%)
78
52
The browser has sent 78 CSS, Javascripts, AJAX and image requests in order to completely render the main page of PIE Books. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 6 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
piebooks.com
757 ms
pie.co.jp
594 ms
common.css
332 ms
top.css
351 ms
jquery.bxslider.css
352 ms
jquery.js
566 ms
jquery.easing.js
390 ms
jquery.bxslider.min.js
406 ms
sly.min.js
659 ms
scrollbar.js
678 ms
reset.css
393 ms
fonts.css
444 ms
lib.css
448 ms
general.css
633 ms
newlogo.gif
188 ms
btn_search.gif
344 ms
head_facebook.gif
350 ms
head_twitter.gif
371 ms
head_pinterest.gif
375 ms
btn_cart.gif
377 ms
btn_english.gif
557 ms
topimg.jpg
1051 ms
topimg.jpg
1037 ms
topimg.jpg
1241 ms
topimg.jpg
2469 ms
topimg.jpg
3025 ms
topimg.jpg
2333 ms
topimg.jpg
2085 ms
topimg.jpg
2467 ms
topimg.jpg
3390 ms
topimg.jpg
3394 ms
topimg.jpg
2964 ms
topimg.jpg
3513 ms
topimg.jpg
3875 ms
topimg.jpg
3743 ms
topimg.jpg
3808 ms
topimg.jpg
4090 ms
topimg.jpg
3986 ms
topimg.jpg
4159 ms
topimg.jpg
5711 ms
topimg.jpg
5115 ms
arrow01.gif
4303 ms
img1_thumb.jpg
4358 ms
img1_thumb.jpg
4441 ms
img1_thumb.jpg
4504 ms
img1_thumb.jpg
4699 ms
img1_thumb.jpg
4709 ms
img1_thumb.jpg
4841 ms
img1_thumb.jpg
4877 ms
analytics.js
27 ms
img1_thumb.jpg
4978 ms
collect
11 ms
img1_thumb.jpg
4871 ms
img1_thumb.jpg
4874 ms
img1_thumb.jpg
4932 ms
img1_thumb.jpg
5054 ms
img1_thumb.jpg
5054 ms
img1_thumb.jpg
5115 ms
img1_thumb.jpg
5033 ms
img1_thumb.jpg
4593 ms
img1_thumb.jpg
4705 ms
img1_thumb.jpg
4553 ms
img1_thumb.jpg
3734 ms
img1_thumb.jpg
3579 ms
img1_thumb.jpg
3488 ms
icon_new.gif
3589 ms
icon_rensai.gif
3110 ms
icon_tsuhan.gif
3144 ms
icon_digital.gif
2812 ms
icon_bookstore.gif
2889 ms
icon_buy.gif
2787 ms
icon_catalog.gif
2704 ms
icon_mailmagazine.gif
2656 ms
b_pankabe.jpg
2839 ms
terada_banner4.jpg
2565 ms
b_abiko.jpg
2535 ms
CITI_banner.jpg
2695 ms
bx_loader.gif
2508 ms
topimg.jpg
3528 ms
bx_controls.png
2450 ms
piebooks.com 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-*] attributes do not match their roles
[aria-hidden="true"] elements contain focusable descendents
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
ARIA toggle fields do not have accessible names
[aria-*] attributes do not have valid values
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
Links do not have a discernible name
piebooks.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
General
Impact
Issue
Detected JavaScript libraries
piebooks.com 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
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
EUC-JP
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Piebooks.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 Piebooks.com 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.
piebooks.com
Open Graph description is not detected on the main page of PIE Books. 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: