9 sec in total
2.9 sec
5.6 sec
419 ms
Welcome to makoto-tanaka.com homepage info - get ready to check Makoto Tanaka best content for Japan right away, or after learning these important things about makoto-tanaka.com
エンジニア・起業家の雑記
Visit makoto-tanaka.comWe analyzed Makoto-tanaka.com page load time and found that the first response time was 2.9 sec and then it took 6.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
makoto-tanaka.com performance score
name
value
score
weighting
Value3.7 s
29/100
10%
Value8.4 s
2/100
25%
Value14.1 s
1/100
10%
Value1,510 ms
14/100
30%
Value0
100/100
15%
Value11.6 s
18/100
10%
2928 ms
474 ms
339 ms
352 ms
358 ms
Our browser made a total of 51 requests to load all elements on the main page. We found that 88% of them (45 requests) were addressed to the original Makoto-tanaka.com, 4% (2 requests) were made to Google-analytics.com and 4% (2 requests) were made to Staticxx.facebook.com. The less responsive or slowest element that took the longest time to load (2.9 sec) belongs to the original domain Makoto-tanaka.com.
Page size can be reduced by 598.7 kB (28%)
2.1 MB
1.5 MB
In fact, the total size of Makoto-tanaka.com main page is 2.1 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. 30% of websites need less resources to load. Images take 1.7 MB which makes up the majority of the site volume.
Potential reduce by 92.3 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 92.3 kB or 84% of the original size.
Potential reduce by 328.8 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. Obviously, Makoto Tanaka needs image optimization as it can save up to 328.8 kB or 19% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 77.4 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 77.4 kB or 55% of the original size.
Potential reduce by 100.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. Makoto-tanaka.com needs all CSS files to be minified and compressed as it can save up to 100.2 kB or 67% of the original size.
Number of requests can be reduced by 16 (32%)
50
34
The browser has sent 50 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Makoto Tanaka. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 7 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
makoto-tanaka.com
2928 ms
app.css
474 ms
style.css
339 ms
styles.css
352 ms
screen.min.css
358 ms
wpp.css
371 ms
dashicons.min.css
543 ms
thickbox.css
524 ms
amazonjs.min.css
535 ms
shCore.css
561 ms
shCoreMidnight.css
644 ms
shThemeMidnight.css
721 ms
all.js
913 ms
shCore.js
706 ms
shAutoloader.js
705 ms
shBrushXml.js
706 ms
javascript.js
706 ms
ga.js
127 ms
logo.png
172 ms
photo-1445295029071-5151176738d0-400x266.jpeg
246 ms
cropped-hiro-1-400x400.png
1308 ms
487388660_5f38d0cb44.jpg
200 ms
%E3%82%B9%E3%82%AF%E3%83%AA%E3%83%BC%E3%83%B3%E3%82%B7%E3%83%A7%E3%83%83%E3%83%88-2015-11-14-15.59.10-400x234.png
583 ms
%E3%82%B9%E3%82%AF%E3%83%AA%E3%83%BC%E3%83%B3%E3%82%B7%E3%83%A7%E3%83%83%E3%83%88-2013-08-28-9.56.52.png
392 ms
logo.a2242142-400x266.png
399 ms
%E3%82%B9%E3%82%AF%E3%83%AA%E3%83%BC%E3%83%B3%E3%82%B7%E3%83%A7%E3%83%83%E3%83%88-2015-11-05-13.05.35-400x204.png
616 ms
%E3%82%B9%E3%82%AF%E3%83%AA%E3%83%BC%E3%83%B3%E3%82%B7%E3%83%A7%E3%83%83%E3%83%88-2015-10-29-15.46.56-400x194.png
670 ms
%E3%82%B9%E3%82%AF%E3%83%AA%E3%83%BC%E3%83%B3%E3%82%B7%E3%83%A7%E3%83%83%E3%83%88-2015-10-07-0.01.20-400x217.png
1402 ms
%E3%82%B9%E3%82%AF%E3%83%AA%E3%83%BC%E3%83%B3%E3%82%B7%E3%83%A7%E3%83%83%E3%83%88-2015-10-05-21.53.23-400x260.png
1277 ms
google-analytics.png
757 ms
%E3%82%B9%E3%82%AF%E3%83%AA%E3%83%BC%E3%83%B3%E3%82%B7%E3%83%A7%E3%83%83%E3%83%88-2015-10-01-0.11.58-400x219.png
996 ms
%E3%82%B9%E3%82%AF%E3%83%AA%E3%83%BC%E3%83%B3%E3%82%B7%E3%83%A7%E3%83%83%E3%83%88-2015-09-30-23.35.50-400x221.png
1555 ms
%E3%82%B9%E3%82%AF%E3%83%AA%E3%83%BC%E3%83%B3%E3%82%B7%E3%83%A7%E3%83%83%E3%83%88-2015-09-30-13.27.47-400x214.png
1409 ms
S001_megane0120140830145829-400x224.jpg
1197 ms
8465131121_78966bba25_b-400x500.jpg
1568 ms
detail1_ff91b11d-1d2c-4987-abb0-c678cdefcf61-400x299.jpg
1490 ms
%E3%82%B9%E3%82%AF%E3%83%AA%E3%83%BC%E3%83%B3%E3%82%B7%E3%83%A7%E3%83%83%E3%83%88-2015-09-14-0.58.18-400x298.png
1682 ms
%E3%82%B9%E3%82%AF%E3%83%AA%E3%83%BC%E3%83%B3%E3%82%B7%E3%83%A7%E3%83%83%E3%83%88-2015-09-12-19.04.02-400x200.png
1590 ms
%E3%82%B9%E3%82%AF%E3%83%AA%E3%83%BC%E3%83%B3%E3%82%B7%E3%83%A7%E3%83%83%E3%83%88-2015-09-12-17.48.23-400x224.png
1604 ms
42-featured-75x75.jpg
1667 ms
no_thumb.jpg
1728 ms
1382-featured-75x75.jpg
1931 ms
122-featured-75x75.png
1760 ms
853-featured-75x75.jpg
1768 ms
fontawesome-webfont.woff
1924 ms
icomoon.woff
1759 ms
__utm.gif
12 ms
sdk.js
71 ms
137 ms
xd_arbiter.php
79 ms
xd_arbiter.php
142 ms
makoto-tanaka.com 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
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
<frame> or <iframe> elements do not have a title
Form elements do not have associated labels
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
makoto-tanaka.com 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
makoto-tanaka.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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 Makoto-tanaka.com 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 Makoto-tanaka.com 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.
makoto-tanaka.com
Open Graph data is detected on the main page of Makoto Tanaka. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: