7.6 sec in total
532 ms
6.9 sec
180 ms
Welcome to izumi.co.jp homepage info - get ready to check Izumi best content for Japan right away, or after learning these important things about izumi.co.jp
中国・四国・九州エリアに「ゆめタウン」を展開する株式会社イズミの企業サイトです。会社情報、IR情報、CSR(環境・社会活動)、採用情報。
Visit izumi.co.jpWe analyzed Izumi.co.jp page load time and found that the first response time was 532 ms and then it took 7.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
izumi.co.jp performance score
name
value
score
weighting
Value4.9 s
11/100
10%
Value19.9 s
0/100
25%
Value12.3 s
3/100
10%
Value1,980 ms
8/100
30%
Value0.279
43/100
15%
Value20.5 s
2/100
10%
532 ms
1618 ms
343 ms
673 ms
505 ms
Our browser made a total of 88 requests to load all elements on the main page. We found that 45% of them (40 requests) were addressed to the original Izumi.co.jp, 14% (12 requests) were made to Googletagmanager.com and 3% (3 requests) were made to T.co. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Izumi.co.jp.
Page size can be reduced by 121.6 kB (17%)
709.7 kB
588.2 kB
In fact, the total size of Izumi.co.jp main page is 709.7 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. 70% of websites need less resources to load. Images take 494.7 kB which makes up the majority of the site volume.
Potential reduce by 21.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 21.1 kB or 78% of the original size.
Potential reduce by 9.5 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. Izumi images are well optimized though.
Potential reduce by 63.5 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 63.5 kB or 41% of the original size.
Potential reduce by 27.5 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. Izumi.co.jp needs all CSS files to be minified and compressed as it can save up to 27.5 kB or 84% of the original size.
Number of requests can be reduced by 54 (64%)
84
30
The browser has sent 84 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Izumi. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 27 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
izumi.co.jp
532 ms
izumi.co.jp
1618 ms
normalize.css
343 ms
style.css
673 ms
common.css
505 ms
style.css
515 ms
index.css
522 ms
jquery-1.8.3.min.js
1603 ms
common.js
927 ms
jquery.cookie.js
521 ms
conversion.js
82 ms
shadow_bottom.png
210 ms
logo.gif
203 ms
link_blank.gif
201 ms
arrow_pink.png
202 ms
btn_search.png
194 ms
gnavi.png
193 ms
h1_bg.png
579 ms
h1.png
569 ms
lead.png
569 ms
links_bg.png
583 ms
links_message.jpg
774 ms
text_box_bg.png
582 ms
text_vision.png
777 ms
links_recruit2404_2.jpg
1020 ms
text_recruit.png
775 ms
links_csr.jpg
986 ms
text_sustainability.png
777 ms
links_ir.jpg
1110 ms
text_ir.png
877 ms
bg_dot.gif
877 ms
news_release.png
878 ms
bn_stock2.jpg
1226 ms
bn_ir_en.jpg
1051 ms
bn_tenant.jpg
1047 ms
bn_search.jpg
1158 ms
main_img_2018.jpg
2024 ms
footer_bg.gif
1214 ms
logo.gif
1224 ms
izumi.gif
203 ms
page_top.png
203 ms
34 ms
gtm.js
60 ms
60 ms
analytics.js
115 ms
destination
81 ms
destination
142 ms
fbevents.js
409 ms
destination
174 ms
destination
174 ms
ytag.js
888 ms
destination
281 ms
destination
171 ms
destination
279 ms
destination
408 ms
destination
411 ms
destination
409 ms
uwt.js
277 ms
segmentation.js
399 ms
lt.js
394 ms
akd1jpvcak
392 ms
events.js
399 ms
collect
281 ms
collect
317 ms
js
200 ms
clarity.js
170 ms
err.gif
668 ms
cnt
708 ms
main.MTIyYzc3NzllMA.js
106 ms
err.gif
668 ms
adsct
163 ms
adsct
151 ms
adsct
108 ms
adsct
109 ms
adsct
88 ms
adsct
89 ms
beacon.html
36 ms
pixel
153 ms
tap.php
158 ms
Pug
143 ms
set
396 ms
pixel
148 ms
sync
859 ms
report
904 ms
c.gif
7 ms
sd
28 ms
bounce
23 ms
sync
381 ms
izumi.co.jp accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
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.
izumi.co.jp 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
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
izumi.co.jp SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Izumi.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 Izumi.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.
izumi.co.jp
Open Graph data is detected on the main page of Izumi. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: