9.3 sec in total
363 ms
8.6 sec
302 ms
Visit platonics.jp now to see the best up-to-date Platonics content for Japan and also check out these interesting facts you probably never knew about platonics.jp
Visit platonics.jpWe analyzed Platonics.jp page load time and found that the first response time was 363 ms and then it took 8.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
platonics.jp performance score
name
value
score
weighting
Value4.8 s
12/100
10%
Value13.4 s
0/100
25%
Value18.3 s
0/100
10%
Value2,820 ms
3/100
30%
Value0.045
99/100
15%
Value18.6 s
3/100
10%
363 ms
5377 ms
477 ms
479 ms
479 ms
Our browser made a total of 137 requests to load all elements on the main page. We found that 85% of them (116 requests) were addressed to the original Platonics.jp, 10% (14 requests) were made to Fonts.gstatic.com and 1% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (5.4 sec) belongs to the original domain Platonics.jp.
Page size can be reduced by 599.1 kB (39%)
1.5 MB
950.1 kB
In fact, the total size of Platonics.jp main page is 1.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. 65% of websites need less resources to load. Javascripts take 563.9 kB which makes up the majority of the site volume.
Potential reduce by 329.4 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 329.4 kB or 84% of the original size.
Potential reduce by 5.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. Platonics images are well optimized though.
Potential reduce by 174.7 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 174.7 kB or 31% of the original size.
Potential reduce by 89.8 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. Platonics.jp needs all CSS files to be minified and compressed as it can save up to 89.8 kB or 38% of the original size.
Number of requests can be reduced by 90 (78%)
115
25
The browser has sent 115 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Platonics. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 41 to 1 for JavaScripts and from 51 to 1 for CSS and as a result speed up the page load time.
platonics.jp
363 ms
platonics.jp
5377 ms
mediaelementplayer-legacy.min.css
477 ms
wp-mediaelement.min.css
479 ms
styles.css
479 ms
elementor-icons.min.css
485 ms
frontend-lite.min.css
489 ms
swiper.min.css
634 ms
post-10.css
636 ms
post-103.css
638 ms
xstore.min.css
970 ms
elementor.min.css
650 ms
back-top.min.css
792 ms
mobile-panel.min.css
794 ms
global.min.css
796 ms
contact-forms.min.css
813 ms
contacts.min.css
950 ms
menu.min.css
952 ms
search.min.css
955 ms
archive.min.css
976 ms
product-view-default.min.css
1109 ms
blog-global.min.css
1111 ms
portfolio.min.css
1113 ms
kirki-styles.css
1130 ms
style.css
1138 ms
css
38 ms
fontawesome.min.css
1425 ms
brands.min.css
1270 ms
jquery.min.js
1433 ms
jquery-migrate.min.js
1291 ms
js.cookie.min.js
1299 ms
s-202430.js
16 ms
etheme-scripts.min.js
1422 ms
frontend.min.js
1431 ms
script.min.js
1452 ms
script.min.js
1461 ms
js-sdk-pro.min.js
297 ms
categories-carousel.min.css
475 ms
widget-icon-box.min.css
149 ms
css
19 ms
pe-icon-7-stroke.css
377 ms
ajax-search.min.css
378 ms
off-canvas.min.css
378 ms
mobile-menu.min.css
378 ms
toggles-by-arrow.min.css
379 ms
cart-widget.min.css
474 ms
post-4676.css
477 ms
banner.min.css
481 ms
banners-global.min.css
487 ms
mega-menu.min.css
512 ms
post-4684.css
522 ms
full-width-search.min.css
631 ms
account.min.css
634 ms
et-timer.min.css
640 ms
swatches.min.css
646 ms
quick-view.min.css
673 ms
etheme-testimonials.min.css
685 ms
instagram.min.css
789 ms
post-6691.css
792 ms
xstore-icons.css
798 ms
light.css
805 ms
rs6.css
834 ms
index.js
846 ms
index.js
946 ms
e-202430.js
2 ms
rbtools.min.js
1398 ms
rs6.min.js
1464 ms
jquery.blockUI.min.js
940 ms
add-to-cart.min.js
964 ms
widget-icon-box.min.css
865 ms
woocommerce.min.js
1245 ms
cart-fragments.min.js
1236 ms
comment-reply.min.js
1236 ms
imagesLoaded.js
1225 ms
woocommerce.min.js
1217 ms
js-sdk-event.min.js
27 ms
jquery.lazyload.js
1167 ms
S6uyw4BMUTPHjx4wWw.ttf
19 ms
S6uyw4BMUTPHjx4wWCWtFCc.woff
22 ms
S6uyw4BMUTPHjxAwWCWtFCfQ7A.woff
25 ms
S6u9w4BMUTPHh7USSwiPHA.ttf
28 ms
S6u8w4BMUTPHh30AXC-v.ttf
28 ms
S6u9w4BMUTPHh6UVSwiPHA.ttf
28 ms
S6u9w4BMUTPHh50XSwiPHA.ttf
28 ms
S6u8w4BMUTPHjxsAXC-v.ttf
19 ms
S6u_w4BMUTPHjxsI9w2_Gwfo.ttf
19 ms
S6u-w4BMUTPHjxsIPx-oPCc.ttf
21 ms
S6u_w4BMUTPHjxsI5wq_Gwfo.ttf
20 ms
S6u_w4BMUTPHjxsI3wi_Gwfo.ttf
19 ms
swiper.min.js
1107 ms
tabs.min.js
1030 ms
fixedHeader.min.js
1030 ms
ajaxSearch.min.js
1088 ms
mobileMenu.min.js
1089 ms
productCategoriesWidget.min.js
1175 ms
PAJJhLM6sSoWKfWCAAwDAjgbRAAB42mNgYGBkAIIbCZo5IPrmUn0hGA0AO8EFTQAA
1 ms
mega-menu.min.js
1082 ms
cartProgressBar.min.js
1109 ms
promoTextCarousel.min.js
1111 ms
countdown.min.js
1110 ms
ethemeElementorSlider.min.js
1095 ms
mobilePanel.min.js
1122 ms
back-top.min.js
1030 ms
webpack.runtime.min.js
1107 ms
frontend-modules.min.js
1108 ms
waypoints.min.js
1110 ms
core.min.js
1095 ms
frontend.min.js
1122 ms
xstore-icons-light.ttf
1197 ms
fa-brands-400.woff
1265 ms
X_STORE_3.png
1108 ms
menu-shop-banner-women.jpg
1109 ms
menu-shop-banner-men.jpg
1089 ms
menu-pages-banner-men.jpg
1120 ms
menu-pages-banner-women.jpg
1126 ms
woocommerce-placeholder-300x300.png
1110 ms
dummy.png
1088 ms
rocket.png
729 ms
sale.png
749 ms
returs.png
814 ms
MW0MW07435_100_main.jpg
821 ms
5.jpg
829 ms
11.jpg
840 ms
about-us-avatar.jpg
887 ms
about-us-avatar2.jpg
907 ms
about-us-avatar3.jpg
968 ms
9oRPNYsQpS4zjuA_iwgT.ttf
45 ms
pxiEyp8kv8JHgFVrJJfedw.ttf
44 ms
payment_methods.png
961 ms
drag.png
927 ms
slider-elipse-1.png
937 ms
slider-elipse-3.png
982 ms
Pe-icon-7-stroke.woff
1143 ms
patternstripes-1.png
978 ms
slider-elipse-2.png
967 ms
testim-bg.jpg
150 ms
testim-bg.jpg
1132 ms
platonics.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.
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
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
platonics.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
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
Issues were logged in the Issues panel in Chrome Devtools
platonics.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
EN
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Platonics.jp can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Japanese language. Our system also found out that Platonics.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.
platonics.jp
Open Graph description is not detected on the main page of Platonics. 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: