2.8 sec in total
307 ms
2 sec
533 ms
Click here to check amazing Aizo content for Japan. Otherwise, check out these important facts you probably never knew about aizo.me
Visit aizo.meWe analyzed Aizo.me page load time and found that the first response time was 307 ms and then it took 2.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
aizo.me performance score
name
value
score
weighting
Value2.4 s
72/100
10%
Value5.7 s
16/100
25%
Value2.6 s
97/100
10%
Value70 ms
99/100
30%
Value0.375
28/100
15%
Value5.7 s
68/100
10%
307 ms
150 ms
6 ms
368 ms
437 ms
Our browser made a total of 44 requests to load all elements on the main page. We found that 89% of them (39 requests) were addressed to the original Aizo.me, 5% (2 requests) were made to Google-analytics.com and 2% (1 request) were made to Code.jquery.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Aizo.me.
Page size can be reduced by 97.1 kB (9%)
1.1 MB
962.8 kB
In fact, the total size of Aizo.me main page is 1.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. 45% of websites need less resources to load. Images take 938.1 kB which makes up the majority of the site volume.
Potential reduce by 8.1 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 8.1 kB or 61% of the original size.
Potential reduce by 4.9 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. Aizo images are well optimized though.
Potential reduce by 16.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 16.9 kB or 58% of the original size.
Potential reduce by 67.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. Aizo.me needs all CSS files to be minified and compressed as it can save up to 67.2 kB or 85% of the original size.
We found no issues to fix!
42
42
The browser has sent 42 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Aizo. According to our analytics all requests are already optimized.
aizo.me
307 ms
aizome.min.css
150 ms
jquery-2.1.4.min.js
6 ms
aizome.min.js
368 ms
top-bg-nami.png
437 ms
top-bg-aizen.jpg
555 ms
aizome-logo.svg
296 ms
denwauranai-aizome.svg
300 ms
icon-call.png
293 ms
icon-menu.png
294 ms
navi-logo.svg
438 ms
navi-logo-wt.svg
440 ms
eyecatch-bg.jpg
442 ms
TOPimg-aizome.jpg
1166 ms
TOPimg-aitorei.jpg
727 ms
TOPimg-first.jpg
875 ms
top-h2-bg.png
585 ms
top-ListBg-01.jpg
728 ms
top-ListBg-02.jpg
699 ms
top-ListBg-03.jpg
1020 ms
arrow-b0.svg
846 ms
top-ListBg-04.jpg
872 ms
top-ListBg-05.jpg
875 ms
top-ListBg-06.jpg
992 ms
top-GDbg-R.png
1018 ms
top-GDbg-L.png
1163 ms
thumbnail.jpg
1020 ms
thumbnail.jpg
1137 ms
top_bnr_bg.jpg
1163 ms
top_bnr_bg.jpg
1164 ms
top_bnr_bg.jpg
1166 ms
top_bnr_bg.jpg
1283 ms
top_bnr_bg.jpg
1308 ms
top_bnr_bg.jpg
1308 ms
top_bnr_bg.jpg
1457 ms
top_bnr_bg.jpg
1308 ms
top_bnr_bg.jpg
1310 ms
thumbnail.jpg
1428 ms
uranai-thumbnail.jpg
1451 ms
analytics.js
42 ms
52 ms
VisaMasterJCB.png
1255 ms
collect
12 ms
32 ms
aizo.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
Image elements do not have [alt] attributes
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.
aizo.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
aizo.me 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 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 Aizo.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 Aizo.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.
aizo.me
Open Graph description is not detected on the main page of Aizo. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: