11.4 sec in total
338 ms
10.1 sec
924 ms
Visit lidea.today now to see the best up-to-date Lidea content for Japan and also check out these interesting facts you probably never knew about lidea.today
Lideaとは、“今日”という一日一日を誰よりも愛するLidea編集部が、ライオンの製品やそこに詰まった技術、生活への考え方を通して、くらしへの好奇心や、毎日を慈しむ気持ちをプラスしていく生活情報メディアです。
Visit lidea.todayWe analyzed Lidea.today page load time and found that the first response time was 338 ms and then it took 11.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
lidea.today performance score
name
value
score
weighting
Value3.3 s
41/100
10%
Value20.5 s
0/100
25%
Value12.1 s
3/100
10%
Value2,030 ms
7/100
30%
Value1.076
2/100
15%
Value43.9 s
0/100
10%
338 ms
839 ms
324 ms
482 ms
135 ms
Our browser made a total of 213 requests to load all elements on the main page. We found that 38% of them (82 requests) were addressed to the original Lidea.today, 9% (19 requests) were made to Lidea-assets.s3.amazonaws.com and 8% (18 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (2.3 sec) belongs to the original domain Lidea.today.
Page size can be reduced by 942.2 kB (27%)
3.5 MB
2.6 MB
In fact, the total size of Lidea.today 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. 70% of websites need less resources to load. Images take 2.5 MB which makes up the majority of the site volume.
Potential reduce by 51.2 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 51.2 kB or 73% of the original size.
Potential reduce by 213.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. Lidea images are well optimized though.
Potential reduce by 554.2 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 554.2 kB or 69% of the original size.
Potential reduce by 123.2 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. Lidea.today needs all CSS files to be minified and compressed as it can save up to 123.2 kB or 87% of the original size.
Number of requests can be reduced by 87 (42%)
205
118
The browser has sent 205 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lidea. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 60 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
lidea.today
338 ms
lidea.today
839 ms
index.css
324 ms
adlpo.js
482 ms
plusone.js
135 ms
index.js
979 ms
jquery.js
2001 ms
i_search_assist.js
1175 ms
1.jpg
1274 ms
82x20.png
855 ms
idsync
956 ms
1.jpg
1278 ms
cover.jpg
1050 ms
cover.jpg
1051 ms
1.jpg
1229 ms
thumb_1.jpg
867 ms
thumb_1.jpg
1062 ms
thumb_fabric201311_1_m.jpg
1222 ms
thumb_1.jpg
1232 ms
thumb_cover_792.jpg
1228 ms
thumb_cover.jpg
1408 ms
thumb_1.jpg
1545 ms
thumb_0.jpg
1417 ms
thumb_cover.jpg
1546 ms
hd_logo.png
177 ms
ico_logo-corp.png
176 ms
ico_search.png
385 ms
btn_carousel-prev.png
384 ms
btn_carousel-next.png
487 ms
ico_article.png
521 ms
ico_clip.png
542 ms
ico_project.png
543 ms
tag-pickup.png
564 ms
thumb_top.jpg
647 ms
img_meister-trip.jpg
1554 ms
thumb.jpg
673 ms
img_knowledge.jpg
1328 ms
img_lifestyle-check.jpg
1328 ms
img_woman-quiz.jpg
1665 ms
img_nursery-recipe.jpg
1125 ms
ico_report.png
831 ms
thumb.jpg
990 ms
ico_qa.png
1149 ms
ico_q.png
1287 ms
ico_qa-login.png
1306 ms
ico_alliance.png
1447 ms
bnr_iemo.png
1464 ms
bnr_jooy.png
1488 ms
bnr_cafy.png
1483 ms
bnr_cuta.png
1607 ms
bnr_healthcare.png
1622 ms
bnr_kurashinista.png
1643 ms
img_signup.png
1643 ms
logo_question_small.png
1703 ms
ico_topics.png
1767 ms
banner_kajifes.jpg
2250 ms
banner_729.png
1958 ms
ico_ranking.png
1800 ms
sdk.js
439 ms
ico_rank1.png
1825 ms
c.js
1202 ms
ico_rank2.png
1692 ms
ico_rank3.png
1760 ms
ico_rank4.png
1586 ms
ico_rank5.png
1644 ms
136 ms
xd_arbiter.php
423 ms
ico_rank6.png
1538 ms
ico_rank7.png
1608 ms
ico_rank8.png
1607 ms
ico_rank9.png
1584 ms
ico_rank10.png
1633 ms
ico_page-top.png
1641 ms
hd_logo-footer.png
1607 ms
sync.php
941 ms
ico_external.png
1609 ms
ico_clipped.png
1453 ms
sync.php
750 ms
ico_unclipped.png
1334 ms
ico_articles_focus.png
1259 ms
ico_nav-arrow.png
1268 ms
c.js
214 ms
ico_nav-washing.png
1131 ms
ico_nav-cleaning.png
1185 ms
ico_nav-kitchen.png
1168 ms
ico_nav-oralcare.png
1168 ms
ico_nav-healthcare.png
1149 ms
ico_nav-childcare.png
1133 ms
1.jpg
175 ms
c.js
233 ms
ico_nav-matome.png
1115 ms
ico_qa.png
1119 ms
ico_projects.png
1058 ms
ico_bullet.png
1020 ms
bg_header-line.png
1119 ms
bg_corp-color.png
1085 ms
ico_nav-kitchen_current.png
1086 ms
bg_tag.png
1103 ms
ico_nav-healthcare_current.png
1063 ms
1.jpg
372 ms
c.js
215 ms
ico_nav-oralcare_current.png
1013 ms
ico_nav-washing_current.png
1092 ms
ico_nav-cleaning_current.png
1052 ms
oral201312_2_m.jpg
188 ms
c.js
231 ms
TOP.png
501 ms
c.js
220 ms
ico_nav-projects-sub_current.png
733 ms
fabric20120321_3_m.jpg
352 ms
widgets.js
77 ms
plugins.js
988 ms
cb=gapi.loaded_0
69 ms
bg_arrow-text-link.png
490 ms
bg_cover.png
493 ms
bg_skew.png
502 ms
bg_town.png
618 ms
log.php
912 ms
c.js
219 ms
sync.php
517 ms
tag.js
53 ms
jsonp.js
1212 ms
yahoo-min.js
1517 ms
dom-min.js
1526 ms
searchAssistTemplate.js
2080 ms
iSearchAssistJSON.js
1370 ms
tag
32 ms
18,97,187,499,539,550,636,637,643,667,706,721,759,760,783,786,787,792,794,796
257 ms
summary
235 ms
button.831500944bc3eb7ea5276ccdc3f71d2e.js
33 ms
analytics.js
81 ms
am_lion.js
409 ms
favorite.pl
1060 ms
cb=gapi.loaded_1
24 ms
fastbutton
144 ms
like.php
116 ms
page.php
308 ms
postmessageRelay
124 ms
tweet_button.6a78875565a912489e9aef879c881358.ja.html
45 ms
collect
78 ms
collect
134 ms
rU2ubZ6l1Q5.js
262 ms
LVx-xkvaJ0b.png
261 ms
cb=gapi.loaded_0
119 ms
cb=gapi.loaded_1
117 ms
api.js
184 ms
core:rpc:shindig.random:shindig.sha1.js
183 ms
2536007149-postmessagerelay.js
224 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
237 ms
jot
412 ms
SjqsVDvTIBF.css
102 ms
AAMYCR68qe3.css
98 ms
MKiDk2JIhZf.css
99 ms
_rx8naC75Dy.js
105 ms
3o1espZ6Mhb.js
130 ms
nfTYZZc0iSn.js
149 ms
SFuJyO56WQT.js
133 ms
pJPDNGWM_rf.js
148 ms
itm.js
299 ms
so_sg.js
400 ms
11666315_1447015545604772_6735614620438079022_n.jpg
235 ms
safe_image.php
241 ms
lRyN50VcaFW.js
45 ms
10414842_1447015152271478_9181551983909943041_n.png
81 ms
11659364_1045481492136203_8029339768894502431_n.jpg
93 ms
10968367_853112264753729_3940158100595147776_n.jpg
96 ms
1379841_10150004552801901_469209496895221757_n.jpg
100 ms
10847916_1376708932624412_8383480743232510966_n.jpg
103 ms
1465373_548541488555413_441937680_n.jpg
101 ms
1544588_1436375100023697_2353982992222496346_n.jpg
101 ms
10154162_746230352088957_2189369335801136334_n.jpg
103 ms
safe_image.php
92 ms
safe_image.php
104 ms
safe_image.php
111 ms
safe_image.php
108 ms
wL6VQj7Ab77.png
30 ms
s7jcwEQH7Sx.png
30 ms
LT9rONw9UJp.png
29 ms
am_tpc.js
656 ms
audience
721 ms
R9a_DtVRZgv.js
9 ms
cUDgRFxaoIk.js
11 ms
0JBr1QHp8Gi.js
12 ms
kDOzhTr2W91.js
13 ms
js
179 ms
ebdabf5a3fba3aec_2223.js
784 ms
mixi_check_entry.css
376 ms
json.js
593 ms
underscore-string-1.3.3-2.0.0-compress.js
594 ms
namespace-brook-compress.js
604 ms
prototype-effects-1.6.1-1.8.3-compress.js
1201 ms
mixi.js
829 ms
favorite.production.js
850 ms
jquery-1.7.1.min-noconflict-compress.js
1688 ms
plog
835 ms
gtm.js
116 ms
td-1.2.0.js
69 ms
beacon.html
105 ms
set
615 ms
pageviews
45 ms
am_tpc.js
152 ms
comment001.gif
10 ms
combo
161 ms
pb.html
3 ms
pixel
58 ms
664 ms
631 ms
pixel
15 ms
737 ms
favorite_button004.png
9 ms
comment_content_top001.gif
4 ms
rep
668 ms
156 ms
lidea.today 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
Form elements do not have associated labels
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>).
lidea.today 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
Missing source maps for large first-party JavaScript
lidea.today 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
Tap targets are not sized appropriately
JA
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lidea.today can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Lidea.today 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.
lidea.today
Open Graph data is detected on the main page of Lidea. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: