5.3 sec in total
907 ms
4.2 sec
118 ms
Welcome to aun.tools homepage info - get ready to check AUN best content for Japan right away, or after learning these important things about aun.tools
AUNは、Web制作の現場で、バグや修正の指示をスムーズにするために作られました。デザインやコーディングの指示書を作る手間も省けます。
Visit aun.toolsWe analyzed Aun.tools page load time and found that the first response time was 907 ms and then it took 4.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
aun.tools performance score
name
value
score
weighting
Value3.5 s
36/100
10%
Value4.0 s
49/100
25%
Value8.9 s
15/100
10%
Value1,580 ms
12/100
30%
Value0.725
6/100
15%
Value17.0 s
4/100
10%
907 ms
1045 ms
694 ms
55 ms
1291 ms
Our browser made a total of 52 requests to load all elements on the main page. We found that 50% of them (26 requests) were addressed to the original Aun.tools, 13% (7 requests) were made to Fonts.gstatic.com and 6% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Aun.tools.
Page size can be reduced by 316.9 kB (46%)
682.8 kB
365.8 kB
In fact, the total size of Aun.tools main page is 682.8 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. Only a small number of websites need less resources to load. Javascripts take 277.7 kB which makes up the majority of the site volume.
Potential reduce by 22.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 22.7 kB or 71% of the original size.
Potential reduce by 4.6 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. AUN images are well optimized though.
Potential reduce by 176.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 176.4 kB or 64% of the original size.
Potential reduce by 113.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. Aun.tools needs all CSS files to be minified and compressed as it can save up to 113.2 kB or 88% of the original size.
Number of requests can be reduced by 11 (29%)
38
27
The browser has sent 38 CSS, Javascripts, AJAX and image requests in order to completely render the main page of AUN. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and as a result speed up the page load time.
aun.tools
907 ms
jquery-1.11.1.min.js
1045 ms
jquery.fullPage.min.js
694 ms
0
55 ms
aun.css
1291 ms
ga
352 ms
jquery.magnific-popup.min.js
175 ms
ga
1079 ms
jquery.magnific-popup.min.js
1260 ms
177 ms
56ed4f037701d34e82054939
506 ms
notosansjapanese.css
26 ms
font-awesome.css
176 ms
font-awesome.css
483 ms
logo.png
214 ms
img_explanation01.gif
1582 ms
scene-panel02.jpg
215 ms
scene-panel01.jpg
408 ms
scene-panel03.jpg
213 ms
scene-panel04.jpg
750 ms
img_hatebu.svg
407 ms
logo_tokoton.png
405 ms
drop_down_arrow.png
466 ms
analytics.js
89 ms
bg1.jpg
385 ms
bg2.jpg
678 ms
bg3.jpg
512 ms
bg4.jpg
507 ms
desktop_wovn_logo.png
457 ms
NotoSansJP-Light.woff
87 ms
NotoSansJP-Thin.woff
89 ms
NotoSansJP-DemiLight.woff
186 ms
NotoSansJP-Regular.woff
186 ms
NotoSansJP-Medium.woff
184 ms
NotoSansJP-Bold.woff
181 ms
NotoSansJP-Black.woff
380 ms
pta.js
547 ms
aun.tools
205 ms
entry.count
501 ms
img_explanation02.gif
849 ms
img_explanation03.gif
1014 ms
img_explanation04.gif
684 ms
fontawesome-webfont.woff
514 ms
linkid.js
95 ms
widget_v2.134.js
21 ms
collect
86 ms
collect
151 ms
__$$__stringtable_lang_ja.js
68 ms
7ef15786.js
507 ms
pn
524 ms
avatar_simple_visitor.png
57 ms
aL63HcygAAVYuCCsAAA==
1 ms
aun.tools 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
Links do not have a discernible name
aun.tools 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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
aun.tools 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
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Aun.tools 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 Aun.tools 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.
aun.tools
Open Graph data is detected on the main page of AUN. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: