8.3 sec in total
533 ms
6.9 sec
858 ms
Welcome to azalea.co.jp homepage info - get ready to check Azalea best content for Japan right away, or after learning these important things about azalea.co.jp
JR川崎駅東口、みんなのライフシェアモール。川崎アゼリアのホームページです。
Visit azalea.co.jpWe analyzed Azalea.co.jp page load time and found that the first response time was 533 ms and then it took 7.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
azalea.co.jp performance score
name
value
score
weighting
Value9.9 s
0/100
10%
Value34.7 s
0/100
25%
Value14.9 s
1/100
10%
Value350 ms
73/100
30%
Value0.329
35/100
15%
Value14.1 s
9/100
10%
533 ms
873 ms
1571 ms
172 ms
345 ms
Our browser made a total of 67 requests to load all elements on the main page. We found that 63% of them (42 requests) were addressed to the original Azalea.co.jp, 31% (21 requests) were made to Fonts.gstatic.com and 3% (2 requests) were made to Botia.actiombot.com. The less responsive or slowest element that took the longest time to load (2.8 sec) belongs to the original domain Azalea.co.jp.
Page size can be reduced by 1.2 MB (23%)
5.1 MB
4.0 MB
In fact, the total size of Azalea.co.jp main page is 5.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. Only a small number of websites need less resources to load. Images take 4.6 MB which makes up the majority of the site volume.
Potential reduce by 23.5 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 23.5 kB or 73% of the original size.
Potential reduce by 798.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, Azalea needs image optimization as it can save up to 798.8 kB or 17% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 340.1 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 340.1 kB or 64% of the original size.
Potential reduce by 2.9 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. Azalea.co.jp needs all CSS files to be minified and compressed as it can save up to 2.9 kB or 32% of the original size.
Number of requests can be reduced by 17 (44%)
39
22
The browser has sent 39 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Azalea. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 5 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
azalea.co.jp
533 ms
www.azalea.co.jp
873 ms
www.azalea.co.jp
1571 ms
reset.css
172 ms
common.css
345 ms
top.css
498 ms
slick.css
516 ms
slick-theme.css
515 ms
jquery-3.7.1.min.js
701 ms
slick.js
697 ms
common.js
530 ms
azalea-hp.js
984 ms
css2
32 ms
gtm.js
59 ms
logo.png
171 ms
icon-search-sp.png
174 ms
_img.php
1732 ms
_img.php
2270 ms
9571_74672518666593a6528af6.jpg
1955 ms
7080_6071749356518b8c658601.jpg
501 ms
9449_1914465130660a028c6ee3c.jpg
2425 ms
9429_22454597965fba068815fd.jpg
1039 ms
9581_3701388216663f098a8942.jpg
1167 ms
9586_1359277496662c5e6f0779.jpg
1313 ms
9579_946781821665d84b1cbcae.jpg
1690 ms
9577_2101357713665d2c2383154.jpg
1633 ms
azalea-bnr.png
1803 ms
footer-icon-search.png
1862 ms
access.gif
1897 ms
icon-event.png
1560 ms
icon-shopinfo.png
1619 ms
icon-shopsearch.png
1647 ms
icon-floormap.png
1714 ms
icon-access.png
1732 ms
icon-search.png
1791 ms
icon-language.png
1811 ms
key-visual-bg.png
2775 ms
slash.png
1905 ms
footer-bnr-shopstaff.png
1964 ms
footer-bnr-line.png
1977 ms
select.gif
2023 ms
320e2b484d624b9bcdbd38213f047e30.png
220 ms
S6uyw4BMUTPHvxk.ttf
58 ms
S6u9w4BMUTPHh7USew8.ttf
67 ms
S6u8w4BMUTPHh30wWw.ttf
69 ms
S6u9w4BMUTPHh6UVew8.ttf
67 ms
S6u9w4BMUTPHh50Xew8.ttf
68 ms
-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFPYk75s.ttf
349 ms
-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFJEk75s.ttf
417 ms
-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFLgk75s.ttf
384 ms
-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFM8k75s.ttf
418 ms
-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFCMj75s.ttf
371 ms
-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFBEj75s.ttf
382 ms
-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFE8j75s.ttf
576 ms
-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFJEj75s.ttf
618 ms
-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFBEi75s.ttf
506 ms
xn71YHs72GKoTvER4Gn3b5eMRtWGkp6o7MjQ2bwxOubA.ttf
854 ms
xn71YHs72GKoTvER4Gn3b5eMRtWGkp6o7MjQ2bwDOubA.ttf
1059 ms
xn71YHs72GKoTvER4Gn3b5eMRtWGkp6o7MjQ2bxvOubA.ttf
1014 ms
xn71YHs72GKoTvER4Gn3b5eMRtWGkp6o7MjQ2byxOubA.ttf
911 ms
xn71YHs72GKoTvER4Gn3b5eMRtWGkp6o7MjQ2bzvPebA.ttf
1092 ms
xn71YHs72GKoTvER4Gn3b5eMRtWGkp6o7MjQ2bzWPebA.ttf
1085 ms
xn71YHs72GKoTvER4Gn3b5eMRtWGkp6o7MjQ2byYPebA.ttf
1163 ms
ajax-loader.gif
1956 ms
slick.woff
2010 ms
slick.ttf
172 ms
slick.svg
172 ms
azalea.co.jp 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-hidden="true"] elements contain focusable descendents
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
Image elements do not have [alt] attributes
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.
azalea.co.jp 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
azalea.co.jp 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 Azalea.co.jp 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 Azalea.co.jp 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.
azalea.co.jp
Open Graph data is detected on the main page of Azalea. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: