10.5 sec in total
2.2 sec
7.5 sec
805 ms
Click here to check amazing Naotokimura content for Japan. Otherwise, check out these important facts you probably never knew about naotokimura.tokyo
木村直人 air/ LOVEST SN.Div.Manager air&LOVESTの発信統括マネージャーの公式メディア
Visit naotokimura.tokyoWe analyzed Naotokimura.tokyo page load time and found that the first response time was 2.2 sec and then it took 8.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
naotokimura.tokyo performance score
name
value
score
weighting
Value6.2 s
3/100
10%
Value9.3 s
1/100
25%
Value20.7 s
0/100
10%
Value4,030 ms
1/100
30%
Value0
100/100
15%
Value29.3 s
0/100
10%
2204 ms
350 ms
337 ms
71 ms
344 ms
Our browser made a total of 78 requests to load all elements on the main page. We found that 38% of them (30 requests) were addressed to the original Naotokimura.tokyo, 8% (6 requests) were made to I2.wp.com and 8% (6 requests) were made to Tpc.googlesyndication.com. The less responsive or slowest element that took the longest time to load (4.5 sec) relates to the external source I2.wp.com.
Page size can be reduced by 370.0 kB (26%)
1.4 MB
1.1 MB
In fact, the total size of Naotokimura.tokyo main page is 1.4 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. 65% of websites need less resources to load. Images take 901.5 kB which makes up the majority of the site volume.
Potential reduce by 45.8 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 45.8 kB or 67% of the original size.
Potential reduce by 49.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. Naotokimura images are well optimized though.
Potential reduce by 182.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 182.7 kB or 51% of the original size.
Potential reduce by 92.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. Naotokimura.tokyo needs all CSS files to be minified and compressed as it can save up to 92.6 kB or 80% of the original size.
Number of requests can be reduced by 35 (47%)
75
40
The browser has sent 75 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Naotokimura. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
naotokimura.tokyo
2204 ms
jquery-1.8.2.min.js.pagespeed.jm.Gy0gWi7liO.js
350 ms
jquery.page-scroller-308.js.pagespeed.jm.V6Z-i7XF-a.js
337 ms
plusone.js
71 ms
widget.css,qver=4.4.2.pagespeed.ce.zL7CaAGBe2.css
344 ms
font-awesome.min.css,qver=4.4.2.pagespeed.ce.CDHLpqZw5A.css
381 ms
celtispack-style.css,qver=4.4.2.pagespeed.ce.8LDWYAC8Hw.css
384 ms
styles.css,qver=4.3.1.pagespeed.ce.fIjaP8m3jJ.css
385 ms
pagenavi-css.css,qver=2.70.pagespeed.ce.c9Keyzrk6y.css
502 ms
wpp.css,qver=3.3.3.pagespeed.ce.ZUwz9rjzGg.css
515 ms
amazonjs.css,qver=0.7.3.pagespeed.ce.jqhVZYB6D0.css
518 ms
jetpack.css,qver=3.9.1.pagespeed.ce.PTZZkZbS-K.css
542 ms
jquery.js,qver=1.11.3.pagespeed.jm.zixJPNMRNN.js
744 ms
jquery-migrate.min.js,qver=1.2.1.pagespeed.jm.mhpNjdU8Wl.js
551 ms
style.css.pagespeed.ce.1vT6-RWph-.css
669 ms
adsbygoogle.js
8 ms
brand
17 ms
brand
69 ms
jquery.form.min.js,qver=3.51.0-2014.06.20.pagespeed.jm.RVBOol6lkO.js
527 ms
scripts.js,qver=4.3.1.pagespeed.jm.iZTDISK5pG.js
527 ms
devicepx-jetpack.js
55 ms
e-201609.js
6 ms
cb=gapi.loaded_0
69 ms
common.css
172 ms
layout.css
185 ms
sdk.js
49 ms
20160302093706.jpg
4535 ms
20160302082346.jpg
12 ms
20160301072259.jpg
42 ms
20160301104253.png
44 ms
20160301125723.jpg
44 ms
20160301082845.jpg
43 ms
20160229090219.jpg
43 ms
20160229084751.jpg
44 ms
20160302093706.jpg
4542 ms
xbg_index.jpg.pagespeed.ic.cTDaN7pO5j.jpg
884 ms
335x136xbnr_air.png.pagespeed.ic.vokHRBVJQ4.png
209 ms
335x136xbnr_lovest.png.pagespeed.ic.ICGfxXJdNP.png
378 ms
335x110xbnr_multiverse.jpg.pagespeed.ic.wA6IdHIlFk.jpg
208 ms
335x172xbnr_pool.png.pagespeed.ic.UwHhX-NYq0.png
376 ms
335x86xbnr_bulk.png.pagespeed.ic.LVlL86G4ue.png
286 ms
335x124xbnr_selecty.png.pagespeed.ic.tno-IXr_d_.jpg
399 ms
335x110xbnr_sirabee.png.pagespeed.ic.JQGsb4wNUX.png
380 ms
20160301085727.jpg
42 ms
20160229070756.jpg
43 ms
20160229022058.jpg
45 ms
20160229112431.jpg
45 ms
20160228043214.jpg
100 ms
logo_l.png
816 ms
ca-pub-6464352704003204.js
276 ms
zrt_lookup.html
268 ms
show_ads_impl.js
142 ms
321 ms
xd_arbiter.php
90 ms
xd_arbiter.php
257 ms
88x31.png
241 ms
bnr_b02.jpg
403 ms
ico_naoto.jpg
370 ms
ico_sns.png
392 ms
google_custom_search_watermark.gif
215 ms
ads
251 ms
osd.js
89 ms
ads
355 ms
embeds.js
129 ms
analytics.js
77 ms
ads
185 ms
g.gif
24 ms
collect
25 ms
collect
59 ms
13510213370479641603
45 ms
abg.js
52 ms
m_js_controller.js
70 ms
googlelogo_color_112x36dp.png
138 ms
8691107216535003099
119 ms
s
54 ms
x_button_blue2.png
48 ms
11204545574924786011
10 ms
MdyApZkAHG2-UELdOwjNjjFZXSz-CGj4o1JtDR7aGgs.js
11 ms
naotokimura.tokyo 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
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
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>).
naotokimura.tokyo best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
naotokimura.tokyo SEO score
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 doesn't use legible font sizes
Tap targets are not sized appropriately
N/A
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Naotokimura.tokyo can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is Japanese. Our system also found out that Naotokimura.tokyo 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.
naotokimura.tokyo
Open Graph data is detected on the main page of Naotokimura. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: