6.6 sec in total
398 ms
5.5 sec
682 ms
Welcome to poke.co.jp homepage info - get ready to check Poke best content for Japan right away, or after learning these important things about poke.co.jp
Visit poke.co.jpWe analyzed Poke.co.jp page load time and found that the first response time was 398 ms and then it took 6.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
poke.co.jp performance score
name
value
score
weighting
Value4.0 s
23/100
10%
Value22.2 s
0/100
25%
Value8.7 s
16/100
10%
Value2,210 ms
6/100
30%
Value1.229
1/100
15%
Value12.6 s
14/100
10%
398 ms
839 ms
310 ms
620 ms
313 ms
Our browser made a total of 133 requests to load all elements on the main page. We found that 20% of them (26 requests) were addressed to the original Poke.co.jp, 41% (54 requests) were made to Img.poke.co.jp and 8% (10 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (2.7 sec) relates to the external source Img.poke.co.jp.
Page size can be reduced by 348.6 kB (7%)
5.2 MB
4.8 MB
In fact, the total size of Poke.co.jp main page is 5.2 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. 70% of websites need less resources to load. Images take 4.8 MB which makes up the majority of the site volume.
Potential reduce by 76.9 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 28.6 kB, which is 31% 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 76.9 kB or 82% of the original size.
Potential reduce by 127.3 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. Poke images are well optimized though.
Potential reduce by 111.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 111.7 kB or 55% of the original size.
Potential reduce by 32.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. Poke.co.jp needs all CSS files to be minified and compressed as it can save up to 32.6 kB or 82% of the original size.
Number of requests can be reduced by 41 (33%)
123
82
The browser has sent 123 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Poke. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 27 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
poke.co.jp
398 ms
www.poke.co.jp
839 ms
topstyle_renew.css
310 ms
jquery-1.4.2.min.js
620 ms
rollover.min.js
313 ms
jquery.hoverIntent.minified.js
324 ms
jquery.dcmegamenu.1.3.3.min.js
359 ms
megamenu.js
637 ms
sublast.js
637 ms
jquery.cookie.js
639 ms
jquery.geturlparam.min.js
637 ms
common.js
681 ms
s_retargeting.js
552 ms
entry.js
473 ms
conversion.js
15 ms
bl_track.js
328 ms
bnr01.jpg
810 ms
lb
22 ms
logo.png
323 ms
icon_lupe.png
323 ms
bnr_app_android.jpg
547 ms
bnr_app_ios.jpg
547 ms
eventid_3862_pic1.jpg
809 ms
bnr02.jpg
841 ms
bnr03.jpg
853 ms
bnr04.jpg
974 ms
icon_rank01.gif
451 ms
eventid_7574_pic1.jpg
1353 ms
icon_rank02.gif
953 ms
eventid_7538_pic1.jpg
1241 ms
icon_rank03.gif
994 ms
eventid_7575_pic1.jpg
1159 ms
icon_rank_etc.gif
1097 ms
eventid_7722_pic1.jpg
1512 ms
eventid_7904_pic1.jpg
1296 ms
eventid_7554_pic1.jpg
1387 ms
eventid_7611_pic1.jpg
1468 ms
eventid_7719_pic1.jpg
1386 ms
eventid_7641_pic1.jpg
1615 ms
eventid_7775_pic1.jpg
1708 ms
qrcode-android.gif
1540 ms
qrcode-apple.gif
1531 ms
kotori240x92.jpg
1621 ms
192_100_jrset_new.jpg
1700 ms
navibnr04_new.jpg
1675 ms
navibnr_IACE_new.jpg
1701 ms
pokekaru_96%C3%9750_201507.jpg
1771 ms
entabi_banner.jpg
1773 ms
main01.jpg
2399 ms
icon_new.png
1883 ms
main02_01.jpg
1991 ms
main02_02.jpg
1885 ms
main02_03.jpg
2073 ms
main02_04.jpg
2085 ms
main02_05.jpg
2242 ms
main02_06.jpg
2244 ms
eventid_7656_pic1.jpg
2279 ms
sdk.js
39 ms
icon_arrow.png
343 ms
sfr_bg.gif
332 ms
widgets.js
12 ms
bnrboxline.jpg
620 ms
icon01.gif
622 ms
icon02.gif
668 ms
icon03.gif
668 ms
icon04.gif
768 ms
star.png
801 ms
star_blue.png
930 ms
icon05.gif
916 ms
ga.js
40 ms
__utm.gif
24 ms
85 ms
xd_arbiter.php
51 ms
xd_arbiter.php
86 ms
59 ms
blade_track_jp.js
165 ms
54 ms
532127ec-12c3-4ebd-bae3-cd331079d102.js
26 ms
WRf4.js
10 ms
73 ms
74 ms
69 ms
bl_track.cgi
411 ms
30 ms
timeline.1b43d11859b7663a2225b885f87704a5.js
18 ms
39 ms
syndication
107 ms
540094392782966784
239 ms
23 ms
like_box.php
82 ms
24 ms
cookie_enabled_get.html
362 ms
fH5ORRrNfAg.css
42 ms
T-QU3r9cNUv.css
49 ms
Vqr3k1iJZIS.js
63 ms
x5F9OMjKyLw.js
83 ms
ICDbTSzjQEg.js
81 ms
TTCre3391I0.js
81 ms
eventid_7724_pic1.jpg
1933 ms
12670165_943145685764437_9131046095005242510_n.jpg
67 ms
10294316_924702050942134_4918334775292081550_n.jpg
36 ms
1374254_372198256244147_872176296_n.jpg
40 ms
418875_371801946226637_1565243885_n.jpg
40 ms
11822844_812439802205640_8579784674596824246_n.jpg
39 ms
12669643_440251802827352_9206624297917545696_n.jpg
38 ms
550602_268911973206538_1404911866_n.jpg
38 ms
wL6VQj7Ab77.png
30 ms
s7jcwEQH7Sx.png
30 ms
pixel
40 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
10 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
14 ms
I6-MnjEovm5.js
10 ms
vlXaquuXMrr.js
25 ms
tw-icon_normal.jpg
150 ms
bl_track.cgi
356 ms
eventid_7723_pic1.jpg
1594 ms
eventid_7668_pic1.jpg
1796 ms
eventid_7478_pic1.jpg
2670 ms
eventid_2179_pic1.jpg
2160 ms
jot
32 ms
eventid_7913_pic1.jpg
1735 ms
eventid_7827_pic1.jpg
2198 ms
eventid_7876_pic1.jpg
1699 ms
eventid_7784_pic1.jpg
1861 ms
eventid_7826_pic1.jpg
1831 ms
eventid_6308_pic1.jpg
1743 ms
eventid_7533_pic1.jpg
2018 ms
eventid_7708_pic1.jpg
1922 ms
eventid_7621_pic1.jpg
2061 ms
eventid_7757_pic1.jpg
1769 ms
eventid_7_pic1.jpg
2417 ms
pagetop.jpg
1815 ms
imgCopy.jpg
1887 ms
poke.co.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.
ARIA toggle fields do not have accessible names
[aria-*] attributes do not have valid values
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
<frame> or <iframe> elements do not have a title
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.
poke.co.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
General
Impact
Issue
Detected JavaScript libraries
poke.co.jp SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Poke.co.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 Poke.co.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.
poke.co.jp
Open Graph description is not detected on the main page of Poke. 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: