7.9 sec in total
335 ms
6.9 sec
592 ms
Visit conobie.jp now to see the best up-to-date Conobie content for Japan and also check out these interesting facts you probably never knew about conobie.jp
Conobieは、赤ちゃんや子どもの子育て中のママパパやプレママのための、教育・お世話・しつけ・あそび・グッズ・健康・ライフスタイル・ファッション・美容・マタニティに関する情報が集まるメディアです。子どもの個性をのばすために必要なママパパ向けの情報がたくさんあります。
Visit conobie.jpWe analyzed Conobie.jp page load time and found that the first response time was 335 ms and then it took 7.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
conobie.jp performance score
name
value
score
weighting
Value3.7 s
29/100
10%
Value6.2 s
11/100
25%
Value15.1 s
1/100
10%
Value22,200 ms
0/100
30%
Value0
100/100
15%
Value34.6 s
0/100
10%
335 ms
1379 ms
711 ms
1477 ms
241 ms
Our browser made a total of 114 requests to load all elements on the main page. We found that 49% of them (56 requests) were addressed to the original Conobie.jp, 18% (20 requests) were made to Static.xx.fbcdn.net and 8% (9 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain Conobie.jp.
Page size can be reduced by 821.5 kB (13%)
6.3 MB
5.5 MB
In fact, the total size of Conobie.jp main page is 6.3 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 5.5 MB which makes up the majority of the site volume.
Potential reduce by 56.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. This page needs HTML code to be minified as it can gain 9.2 kB, which is 13% 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 56.4 kB or 77% of the original size.
Potential reduce by 260.1 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. Conobie images are well optimized though.
Potential reduce by 436.6 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 436.6 kB or 72% of the original size.
Potential reduce by 68.4 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. Conobie.jp needs all CSS files to be minified and compressed as it can save up to 68.4 kB or 84% of the original size.
Number of requests can be reduced by 36 (32%)
111
75
The browser has sent 111 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Conobie. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 28 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
conobie.jp
335 ms
conobie.jp
1379 ms
application-381cae81718b7789c08bc67af6bc5458.css
711 ms
application-b01aab531e12578b3ad6683dd134a79e.js
1477 ms
plusone.js
241 ms
bookmark_button_wo_al.js
708 ms
widgets.js
178 ms
btn.js
198 ms
analytics.js
238 ms
fbds.js
197 ms
gpt.js
200 ms
gtm.js
276 ms
pc_logo.png
335 ms
sprite-91483eaf21186c35de45c192351019ee.png
195 ms
57ac0a7d1791a540896b1358f939ebf0c3028d38.jpg
1012 ms
f526d71a5c9a9200344707d5710812fe038ba3b5.jpg
620 ms
c458fae96d4b5b813629c2429132aba65310e051_m.jpg
631 ms
cache.14504_effa05e77b9171085f62677c12da839f31c74e96_m.jpg
970 ms
8921d4d47881ebac1de5c47b026f6de72e83d6ab_m.jpg
972 ms
h2_pickup-1ae013a9394a377fc21c926fd5c9dba6.png
539 ms
45c25ca6e41726b763be46791d2fb39e72ef7237_m.jpg
1690 ms
ac5f93a91755d56f9c512aa41bc0e4a49a7bc11c_s.jpg
767 ms
b56100a778a70a5b91cf4b8032147ddf0ddc3d05_m.jpg
1528 ms
b2118d356de96cb710ca555a871ef0efe0fbca59_s.png
915 ms
827f7056f83d01448e14f709a3597d6c5d8dcd38_m.JPG
1210 ms
cache.200_9f9af029585ba014e07cd3910ca976cf56160616_s.JPG
1125 ms
3257108de498546e84f115c6c81ee1da5b76f39b_m.jpg
1747 ms
26cb31fae06a24af9117512f19e958c2d3427089_s.jpg
1158 ms
c1404f9bf01dc29ac35bdd08a37002796ba329a3_m.jpg
1746 ms
060de412d6b803c94571a0dac3372e9afa93bf9c_s.gif
1310 ms
a56f05af2fab9a0987e8a0b67ee4a1b7f2987c10_m.jpg
1507 ms
650046b4ddbc39a7d403f0c81c4c8ced0016abd0_s.JPG
1608 ms
6960faa11b6d09e0c7837c629a5a056f3f2d25e7_m.jpeg
1802 ms
2a497a78839acae4a6d983e578544105e89ca98f_s.JPG
1675 ms
bc3ad0993ab51e69fb1c8353ee4c2fb24e444e1d_m.jpg
2061 ms
cache.221_9a70776c743352cfcf688e52512673332e5e4007_s.JPG
1828 ms
9fbce3b6e602104ddf44ea9e830e99f600fe2447_m.jpg
2013 ms
e37b61450b765042bcdeac491f4c62277ecf7112_s.JPG
1896 ms
42783067f6bf7c470ea550ac9362074515c1958e_m.png
2057 ms
5dc6fe21e6e46aa4896e1820164b811cf0a66d15_s.png
1948 ms
c4fb3751c880444cf28060cf3e12053bf8a5ccb1_m.jpg
2274 ms
3858c79c22c3de04545ad632e458a3324ee24bd7_m.jpg
2207 ms
e266bfe901622699e1568ef2c0cb792db99307e4_s.jpg
2094 ms
b14bf85839b512f4b5cb092d6126115b3c2d9750_m.jpg
2335 ms
ec28484d4b7974827ea6d596b16a522f834a3639_m.jpg
2209 ms
cache.139_fa755791d0509bb06ae715a2072de724815ed84d_s.jpg
2201 ms
9a40e3d9374923f0763cab4cb47b34005223db1e_m.jpg
2389 ms
sdk.js
56 ms
sdk.js
120 ms
widgets.js
42 ms
568605e598c2bbb9f5574c0419e16410852f2607_s.jpg
2254 ms
158 ms
pubads_impl_81.js
76 ms
collect
18 ms
cb=gapi.loaded_0
48 ms
e686e0f79bbff4284feb48a038f775dd4379e19a_m.jpg
2302 ms
138 ms
collect
104 ms
xd_arbiter.php
86 ms
collect
51 ms
container.html
55 ms
80 ms
95a2c1febfa3dad38979a272b5a6f700ccd48905_s.jpg
2051 ms
7c95dc1f9467e45460bca0946da3e6eb69e8c33e_m.jpg
2053 ms
cache.378_0d990fa9636db56c6349320acba1a0c6499a1db3_s.jpg
1898 ms
e2122adbb5b1dd2c7eb7039c61774e111b7fb2e2_m.png
2340 ms
44f364b41c036598db5e495f2de8d1a1ac6b22cd_m.jpg
1772 ms
144f742fa69f2e2dc9bc4dc396514c982bdc7385_m.jpg
1788 ms
a6f599a1562a42073e5e02088483f2baeed417b3_s.jpg
1713 ms
h2_ranking-e43a96c8f0215401bfbda07e2378616d.png
1715 ms
a3f403010b1587ffa0c870b024e9a38a7ec5f95a_m.jpg
1845 ms
4b5dad48d64cb5a9e0acfaf708b349f0c19c824b_m.jpg
1619 ms
h2_recommended-ce1d56e870e3c0e0bfdacbd454afd0d6.png
1688 ms
98271d9682ae621faae4a255d666777adbfd0c2b_m.jpg
1944 ms
2597206057cfcc8e40c217400bf01aa28d7a92f8_m.jpg
1541 ms
topWriter-bf91db76b9e7c241e6ee7ce8e288180f.jpg
1388 ms
h2_keyword-271995de49355494e5e73710f87db8d4.png
1485 ms
nr-885.min.js
50 ms
page.php
321 ms
6f207f5e1b
108 ms
SjqsVDvTIBF.css
46 ms
AAMYCR68qe3.css
49 ms
MKiDk2JIhZf.css
53 ms
CWIR4ZpwcEg.css
53 ms
_rx8naC75Dy.js
63 ms
3o1espZ6Mhb.js
61 ms
nfTYZZc0iSn.js
84 ms
SFuJyO56WQT.js
60 ms
pJPDNGWM_rf.js
100 ms
qLkez9vV75x.js
113 ms
g7eQ7KS-feD.js
125 ms
10346046_1641685599398229_6600177662844716993_n.jpg
190 ms
safe_image.php
221 ms
lRyN50VcaFW.js
33 ms
safe_image.php
55 ms
safe_image.php
57 ms
safe_image.php
55 ms
safe_image.php
56 ms
11114243_1641685479398241_3137965593328176393_n.png
37 ms
12647151_1677211709221938_7789236461521497160_n.jpg
117 ms
252585_127357250676599_2409103_n.jpg
50 ms
12802823_976199102459857_9176821967087510349_n.jpg
51 ms
12741902_1658495427736027_3694907395717742108_n.jpg
56 ms
10471482_569029123255378_8367308835886161153_n.jpg
51 ms
11902499_873931432685185_957480102559364448_n.jpg
55 ms
12801437_811152379028235_6502480155989947920_n.jpg
115 ms
wL6VQj7Ab77.png
35 ms
s7jcwEQH7Sx.png
34 ms
LT9rONw9UJp.png
27 ms
6GqoI2ZyIrf.png
35 ms
R9a_DtVRZgv.js
4 ms
cUDgRFxaoIk.js
7 ms
0JBr1QHp8Gi.js
4 ms
kDOzhTr2W91.js
5 ms
conobie.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
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>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
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.
conobie.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
Browser errors were logged to the console
conobie.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
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Conobie.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 Conobie.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.
conobie.jp
Open Graph data is detected on the main page of Conobie. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: