6.8 sec in total
1 sec
5.2 sec
596 ms
Welcome to ikeyan.jugem.jp homepage info - get ready to check Ikeyan Jugem best content for Japan right away, or after learning these important things about ikeyan.jugem.jp
いけやんの日々の伝説的なコメント・名言を綴る、有志によるアーカイブ
Visit ikeyan.jugem.jpWe analyzed Ikeyan.jugem.jp page load time and found that the first response time was 1 sec and then it took 5.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
ikeyan.jugem.jp performance score
name
value
score
weighting
Value2.3 s
74/100
10%
Value2.5 s
90/100
25%
Value5.3 s
58/100
10%
Value2,520 ms
4/100
30%
Value0
100/100
15%
Value12.8 s
13/100
10%
1008 ms
311 ms
6 ms
343 ms
7 ms
Our browser made a total of 168 requests to load all elements on the main page. We found that 6% of them (10 requests) were addressed to the original Ikeyan.jugem.jp, 8% (13 requests) were made to Imaging.jugem.jp and 7% (11 requests) were made to Dsum.casalemedia.com. The less responsive or slowest element that took the longest time to load (3.7 sec) belongs to the original domain Ikeyan.jugem.jp.
Page size can be reduced by 273.2 kB (45%)
604.6 kB
331.4 kB
In fact, the total size of Ikeyan.jugem.jp main page is 604.6 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 55% of websites need less resources to load. Javascripts take 325.5 kB which makes up the majority of the site volume.
Potential reduce by 70.7 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 70.7 kB or 80% of the original size.
Potential reduce by 10.0 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. Ikeyan Jugem images are well optimized though.
Potential reduce by 184.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 184.9 kB or 57% of the original size.
Potential reduce by 7.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. Ikeyan.jugem.jp needs all CSS files to be minified and compressed as it can save up to 7.7 kB or 79% of the original size.
Number of requests can be reduced by 96 (65%)
148
52
The browser has sent 148 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ikeyan Jugem. 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 as a result speed up the page load time.
ikeyan.jugem.jp
1008 ms
jm_style.css
311 ms
style.css
6 ms
cookie.js
343 ms
script.js
7 ms
widgets.js
8 ms
share.js
295 ms
AdLantisLoader.js
541 ms
cookie.js
5 ms
analytics.js
25 ms
background.jpg
156 ms
20090901_1504336.jpg
489 ms
20081018_66343.jpg
306 ms
ikeyan.jugem.jp
3729 ms
powered_07b.gif
173 ms
bg_header.gif
6 ms
logo_jugem.gif
16 ms
bg_dot.gif
17 ms
logo_pepabo.gif
16 ms
header.jpg
303 ms
back.jpg
310 ms
entryback.gif
310 ms
ajs.php
23 ms
collect
28 ms
lg.php
21 ms
ajs.php
160 ms
compass.js
11 ms
collect
62 ms
cookie_enabled_get_apac.html
382 ms
match.aspx
19 ms
background.jpg
6 ms
powered_07b.gif
3 ms
12492.js
19 ms
lg.php
12 ms
sync
18 ms
225912-15.js
167 ms
header.jpg
7 ms
back.jpg
3 ms
entryback.gif
8 ms
ajs.php
436 ms
ad
594 ms
lg.php
180 ms
emily.html
25 ms
ajs.php
88 ms
afr
21 ms
ajs.php
304 ms
ri
8 ms
lg.php
12 ms
match.aspx
11 ms
sync
10 ms
225914-15.js
148 ms
a1040359.js
320 ms
ic
334 ms
ajs.php
186 ms
yads.js
500 ms
lg.php
181 ms
a1040358.js
200 ms
lg.php
174 ms
jsk
366 ms
jsk
369 ms
yads_vimps-1.4.1.js
605 ms
tag
435 ms
yads.js
534 ms
pixel
20 ms
sync
17 ms
gl2
178 ms
pixel
18 ms
a.js
347 ms
gl2
174 ms
sync
351 ms
acs
179 ms
acs
177 ms
329 ms
b
345 ms
cs
180 ms
share_button.html
311 ms
share_button.html
309 ms
share_button.html
311 ms
share_button.html
310 ms
share_button.html
309 ms
share_button.html
312 ms
share_button.html
631 ms
share_button.html
626 ms
share_button.html
626 ms
share_button.html
628 ms
tap.php
5 ms
tag
476 ms
sdk.js
11 ms
list.gif
166 ms
ga.js
17 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
72 ms
swfobject.js
396 ms
adlantis.www.js
189 ms
swfobject.js
395 ms
__utm.gif
62 ms
216 ms
yads-iframe.html
196 ms
pd
52 ms
xd_arbiter.php
72 ms
xd_arbiter.php
96 ms
60da0e62-155d-e918-adfd-091aed03b445
88 ms
pixel
42 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html
47 ms
sd
47 ms
sd
45 ms
usermatch
66 ms
acs
183 ms
cs
162 ms
sd
68 ms
list.gif
66 ms
usermatch
27 ms
share_button.php
98 ms
share_button.php
125 ms
gr
19 ms
VutM18AoJUwAAEURJ8kAAAG7%26617
32 ms
pixel
29 ms
casale
15 ms
cs
229 ms
tag
438 ms
rum
29 ms
casale
17 ms
pixel
52 ms
share_button.php
101 ms
share_button.php
192 ms
share_button.php
181 ms
cs
271 ms
share_button.php
187 ms
share_button.php
191 ms
share_button.php
194 ms
crum
67 ms
crum
29 ms
crum
28 ms
crum
21 ms
share_button.php
187 ms
bt_check_6.png
14 ms
share_button.php
244 ms
crum
15 ms
sd
10 ms
m
63 ms
wy1X4hBW7e7.js
58 ms
LVx-xkvaJ0b.png
114 ms
crum
90 ms
yads-iframe.html
225 ms
load_script
371 ms
342 ms
jot.html
80 ms
usermatch
23 ms
oi
214 ms
tag
380 ms
sd
12 ms
cs
162 ms
pixel.htm
35 ms
cse
132 ms
crum
15 ms
rum
225 ms
rum
119 ms
crum
13 ms
ddc.htm
25 ms
rum
23 ms
rum
123 ms
rum
19 ms
798315294da4e9471456480246413226_original.jpg
81 ms
a75869f2bec919121cee72bed286150c2eccce04.png
621 ms
QC_300_250.jpg
761 ms
gcs
352 ms
gcs
355 ms
oi
405 ms
01e634e31752f691150c9acb0402f044
20 ms
ikeyan.jugem.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
<frame> or <iframe> elements do not have a title
<input type="image"> elements do not have [alt] text
Form elements do not have associated labels
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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.
ikeyan.jugem.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
ikeyan.jugem.jp SEO score
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
N/A
EUC-JP
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ikeyan.jugem.jp 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 Ikeyan.jugem.jp main page’s claimed encoding is euc-jp. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
ikeyan.jugem.jp
Open Graph data is detected on the main page of Ikeyan Jugem. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: