11.6 sec in total
1 sec
10.2 sec
379 ms
Welcome to precure.channel.or.jp homepage info - get ready to check Precure Channel best content for Japan right away, or after learning these important things about precure.channel.or.jp
「ひろがるスカイ!プリキュア」のバンダイ公式おもちゃ情報サイトです。「ひろがるスカイ!プリキュア」に登場する変身ぬいぐるみなど、おもちゃの最新情報を続々更新していきます!
Visit precure.channel.or.jpWe analyzed Precure.channel.or.jp page load time and found that the first response time was 1 sec and then it took 10.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
precure.channel.or.jp performance score
name
value
score
weighting
Value8.0 s
0/100
10%
Value28.0 s
0/100
25%
Value11.4 s
5/100
10%
Value420 ms
66/100
30%
Value0.787
5/100
15%
Value20.1 s
2/100
10%
1017 ms
381 ms
387 ms
598 ms
411 ms
Our browser made a total of 112 requests to load all elements on the main page. We found that 63% of them (71 requests) were addressed to the original Precure.channel.or.jp, 7% (8 requests) were made to Mnw.bandainamcoid.com and 6% (7 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (6.4 sec) belongs to the original domain Precure.channel.or.jp.
Page size can be reduced by 658.3 kB (17%)
3.8 MB
3.2 MB
In fact, the total size of Precure.channel.or.jp main page is 3.8 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 3.0 MB which makes up the majority of the site volume.
Potential reduce by 33.3 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 4.7 kB, which is 11% 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 33.3 kB or 79% of the original size.
Potential reduce by 71.5 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. Precure Channel images are well optimized though.
Potential reduce by 507.9 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 507.9 kB or 72% of the original size.
Potential reduce by 45.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. Precure.channel.or.jp needs all CSS files to be minified and compressed as it can save up to 45.7 kB or 83% of the original size.
Number of requests can be reduced by 35 (32%)
111
76
The browser has sent 111 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Precure Channel. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 29 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
precure.channel.or.jp
1017 ms
basic.css
381 ms
top.css
387 ms
slider-pro.css
598 ms
colorbox.css
411 ms
jquery.js
1462 ms
jquery.sliderPro.min.js
1773 ms
jquery.rollover.js
799 ms
common.js
804 ms
top.js
806 ms
nmw.bnr.js
988 ms
ptop.js
1193 ms
jquery.colorbox-min.js
1213 ms
fb.btn.js
1211 ms
reset.css
1004 ms
layout.css
1414 ms
share.js
297 ms
conversion.js
35 ms
ga.js
31 ms
plusone.js
56 ms
__utm.gif
32 ms
cb=gapi.loaded_0
118 ms
mnwsys.js
472 ms
bg.jpg
2428 ms
I000011527.JPEG
340 ms
btn_gnavi_stone_off.png
617 ms
btn_gnavi_goods_off.png
656 ms
ico_new.png
439 ms
btn_gnavi_topics_off.png
651 ms
btn_gnavi_campaign_off.png
654 ms
btn_gnavi_movie_off.png
1068 ms
btn_menu.png
1022 ms
btn_menu_close.png
1269 ms
btn_gnavi_stone.png
1519 ms
btn_gnavi_goods.png
1508 ms
btn_gnavi_topics.png
1868 ms
btn_gnavi_campaign.png
1917 ms
btn_gnavi_movie.png
1873 ms
btn_gnavi_mmg.png
2272 ms
bnr_dvd.jpg
3519 ms
bnr_cp_photo.jpg
3868 ms
bnr_cp_mofu.jpg
3756 ms
bnr_touch.jpg
3590 ms
bnr_stone.jpg
3832 ms
btn_movie_01.jpg
3221 ms
img_goods02.jpg
5935 ms
img_goods03.jpg
5180 ms
img_goods04.jpg
5199 ms
bnr_link_toei.jpg
4150 ms
bnr_link_abc.jpg
4459 ms
bnr_link_bgc.gif
4277 ms
bnr_apparel.jpg
4754 ms
bnr_gashapon.jpg
4676 ms
bnr_life.jpg
5288 ms
bnr_charadeco.jpg
5271 ms
precure_bnr.jpg
5139 ms
logo_bandai.gif
5528 ms
btn_ptop_off.png
5591 ms
I000010238.JPEG
331 ms
I000010239.JPEG
365 ms
I000010240.JPEG
375 ms
I000010241.JPEG
353 ms
sdk.js
207 ms
logo.png
5779 ms
bg_gnavi.png
5647 ms
widgets.js
112 ms
share_button.html
348 ms
share
353 ms
cb=gapi.loaded_1
57 ms
fastbutton
96 ms
52 ms
postmessageRelay
41 ms
button.831500944bc3eb7ea5276ccdc3f71d2e.js
164 ms
cb=gapi.loaded_0
36 ms
cb=gapi.loaded_1
19 ms
api.js
70 ms
core:rpc:shindig.random:shindig.sha1.js
97 ms
2536007149-postmessagerelay.js
88 ms
54 ms
xd_arbiter.php
138 ms
xd_arbiter.php
248 ms
tweet_button.6a78875565a912489e9aef879c881358.ja.html
44 ms
bt_check_1.png
21 ms
jquery-1.7.2.min.js
21 ms
btn_iine_20.png
354 ms
bg_main_bnr.png
6391 ms
jErsQuery.js
940 ms
MnwAdTemplate.js
439 ms
respondweb.js
316 ms
layout_max.css
318 ms
jot
101 ms
tit_news.png
5326 ms
ico_title.png
5361 ms
bg_news.png
5429 ms
ico_news.png
5528 ms
bg_movie.png
5299 ms
tit_goods.png
5275 ms
bg_goods.png
5132 ms
layout_min.css
159 ms
addef.jsonp
158 ms
bg_sub_top.png
4976 ms
bg_sub_bottom.png
5056 ms
AdPageView
162 ms
bg_sub_middle.png
4861 ms
bg_sub_inner.jpg
4881 ms
btn_sub_mmg_off.png
5287 ms
bg_sub_botton.png
4594 ms
btn_tel.png
5146 ms
btn_stone.png
4502 ms
bg_footer.png
3804 ms
img_left_off.png
3637 ms
img_right_off.png
3492 ms
precure.channel.or.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-*] 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.
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
Image elements do not have [alt] attributes
Links do not have a discernible name
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>).
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.
precure.channel.or.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
precure.channel.or.jp SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
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 Precure.channel.or.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 Precure.channel.or.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.
precure.channel.or.jp
Open Graph data is detected on the main page of Precure Channel. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: