29.6 sec in total
1.6 sec
27.4 sec
549 ms
Click here to check amazing Sho Yamane content for Japan. Otherwise, check out these important facts you probably never knew about sho-yamane.me
福岡市在住のフリーランスWebデザイナー兼フロントエンドエンジニアです。上場企業などのWeb製作、運用保守、中小企業の集客コンサルティングなどをやっています。
Visit sho-yamane.meWe analyzed Sho-yamane.me page load time and found that the first response time was 1.6 sec and then it took 28 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
sho-yamane.me performance score
name
value
score
weighting
Value4.9 s
10/100
10%
Value0
0/100
25%
Value8.7 s
16/100
10%
Value200 ms
90/100
30%
Value0
100/100
15%
Value7.3 s
50/100
10%
1591 ms
1037 ms
821 ms
627 ms
381 ms
Our browser made a total of 104 requests to load all elements on the main page. We found that 35% of them (36 requests) were addressed to the original Sho-yamane.me, 19% (20 requests) were made to Scontent.cdninstagram.com and 12% (12 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (19.7 sec) belongs to the original domain Sho-yamane.me.
Page size can be reduced by 678.8 kB (15%)
4.6 MB
3.9 MB
In fact, the total size of Sho-yamane.me main page is 4.6 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. 60% of websites need less resources to load. Images take 3.9 MB which makes up the majority of the site volume.
Potential reduce by 64.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 64.8 kB or 78% of the original size.
Potential reduce by 147.2 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. Sho Yamane images are well optimized though.
Potential reduce by 232.8 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 232.8 kB or 69% of the original size.
Potential reduce by 234.1 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. Sho-yamane.me needs all CSS files to be minified and compressed as it can save up to 234.1 kB or 86% of the original size.
Number of requests can be reduced by 49 (55%)
89
40
The browser has sent 89 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Sho Yamane. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 35 to 1 for JavaScripts and from 16 to 1 for CSS and as a result speed up the page load time.
www.sho-yamane.me
1591 ms
wp-emoji-release.min.js
1037 ms
crayon.min.css
821 ms
sublime-text.css
627 ms
monaco.css
381 ms
styles.css
395 ms
pagenavi-css.css
580 ms
animate.css
1446 ms
notosansjapanese.css
99 ms
css
128 ms
font-awesome.min.css
153 ms
keyframe.css
860 ms
style.css
1537 ms
responsive.css
773 ms
amazonjs.css
868 ms
jetpack.css
2113 ms
jquery.js
2063 ms
jquery-migrate.min.js
1225 ms
crayon.min.js
1464 ms
jquery.cycle.js
1483 ms
slideshow-shortcode.js
1284 ms
jquery.form.min.js
1303 ms
scripts.js
1149 ms
devicepx-jetpack.js
50 ms
gprofiles.js
81 ms
wpgroho.js
1334 ms
velocity.min.js
56 ms
sns.js
1673 ms
jquery.heightLine.js
1525 ms
jquery.simplyscroll.min.js
1716 ms
instafeed.min.js
1839 ms
ext_subscribe.js
884 ms
custom.js
1880 ms
wp-embed.min.js
1707 ms
e-201614.js
37 ms
analytics.js
27 ms
profile.jpg
6706 ms
wp_post_eyee.png
9170 ms
wp_login.png
1922 ms
wp_install.png
7739 ms
wp-server-1024x683.png
19720 ms
wp_eye-1024x361.png
3705 ms
instant-articles-wordpress-hero1-1024x576.jpg
3272 ms
collect
14 ms
graph.facebook.com
166 ms
count.json
1041 ms
entry.count
957 ms
graph.facebook.com
250 ms
count.json
1211 ms
entry.count
995 ms
graph.facebook.com
354 ms
count.json
1396 ms
entry.count
1025 ms
graph.facebook.com
365 ms
count.json
1589 ms
entry.count
1034 ms
graph.facebook.com
402 ms
count.json
1862 ms
entry.count
1035 ms
graph.facebook.com
365 ms
count.json
2073 ms
entry.count
1101 ms
graph.facebook.com
361 ms
count.json
2077 ms
entry.count
1171 ms
hovercard.css
38 ms
services.css
68 ms
recent
578 ms
g.gif
22 ms
NotoSansJP-Regular.woff
129 ms
NotoSansJP-Medium.woff
208 ms
NotoSansJP-DemiLight.woff
738 ms
NotoSansJP-Light.woff
538 ms
NotoSansJP-Thin.woff
564 ms
NotoSansJP-Bold.woff
736 ms
NotoSansJP-Black.woff
728 ms
10311299_1524270234540626_1056405665_n.jpg
181 ms
12383442_907880902664433_150007705_n.jpg
126 ms
12729406_987967961279573_969116723_n.jpg
212 ms
12725125_1117243658307819_420566658_n.jpg
183 ms
12825711_200338333658093_21926623_n.jpg
180 ms
12826245_1670434309900267_1396530329_n.jpg
202 ms
11349314_827977890640271_534113236_n.jpg
167 ms
12424749_1695264307412915_1863066017_n.jpg
270 ms
914518_1738153756471842_1618971822_n.jpg
267 ms
1172481_136776806716259_1907695185_n.jpg
276 ms
12783266_1580075565645092_283071321_n.jpg
328 ms
12751521_1700220360267181_1705746494_n.jpg
299 ms
12716478_1565932453697242_1882708269_n.jpg
319 ms
12748267_1569845946674675_1149746353_n.jpg
421 ms
12798094_1701312400112216_861637670_n.jpg
384 ms
12519091_1075415829163719_683262654_n.jpg
427 ms
12797673_455365944658777_999469140_n.jpg
418 ms
12905248_1687615804821488_1326887449_n.jpg
430 ms
12826187_462397803959792_660382271_n.jpg
455 ms
12135174_1136982606341281_1856853579_n.jpg
524 ms
blog-bk.jpg
12073 ms
kamogawa.jpg
3787 ms
xgzbb53t8j-Mo-vYa23n5onF5uFdDttMLvmWuJdhhgs.ttf
86 ms
C6HYlRF50SGJq1XyXj04zwV_pQ1T3xN3K1c3sB361us.ttf
47 ms
q9w3H4aeBxj0hZ8Osfi3d2-gXUWvikdRm39El-Kldqo.ttf
48 ms
C6HYlRF50SGJq1XyXj04z1FZMcfX2SbzQ69I7OWmkGo.ttf
35 ms
C6HYlRF50SGJq1XyXj04z306qf9KHRHwsVx7iw5MXmY.ttf
46 ms
fontawesome-webfont.woff
129 ms
sho-yamane.me accessibility score
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
Buttons do not have an accessible name
Links do not have a discernible name
sho-yamane.me 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
sho-yamane.me 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
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 Sho-yamane.me 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 Sho-yamane.me 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.
sho-yamane.me
Open Graph data is detected on the main page of Sho Yamane. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: