8.1 sec in total
803 ms
7 sec
347 ms
Click here to check amazing UNICUS Sc content for Japan. Otherwise, check out these important facts you probably never knew about unicus-sc.jp
埼玉県(南古谷・上里・川越・伊奈・秩父・鴻巣・吉川)、千葉県(野田・成田)、群馬県(高崎)に展開するショッピングセンター。
Visit unicus-sc.jpWe analyzed Unicus-sc.jp page load time and found that the first response time was 803 ms and then it took 7.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
unicus-sc.jp performance score
name
value
score
weighting
Value6.0 s
4/100
10%
Value12.6 s
0/100
25%
Value10.7 s
7/100
10%
Value140 ms
95/100
30%
Value0.238
52/100
15%
Value6.7 s
56/100
10%
803 ms
416 ms
595 ms
420 ms
2389 ms
Our browser made a total of 74 requests to load all elements on the main page. We found that 97% of them (72 requests) were addressed to the original Unicus-sc.jp, 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (3.2 sec) belongs to the original domain Unicus-sc.jp.
Page size can be reduced by 409.4 kB (8%)
5.2 MB
4.8 MB
In fact, the total size of Unicus-sc.jp main page is 5.2 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. 20% of websites need less resources to load. Images take 4.9 MB which makes up the majority of the site volume.
Potential reduce by 12.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 12.3 kB or 81% of the original size.
Potential reduce by 116.3 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. UNICUS Sc images are well optimized though.
Potential reduce by 272.8 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 272.8 kB or 81% of the original size.
Potential reduce by 8.0 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. Unicus-sc.jp needs all CSS files to be minified and compressed as it can save up to 8.0 kB or 76% of the original size.
Number of requests can be reduced by 6 (8%)
73
67
The browser has sent 73 CSS, Javascripts, AJAX and image requests in order to completely render the main page of UNICUS Sc. 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 as a result speed up the page load time.
unicus-sc.jp
803 ms
reset.css
416 ms
master.css
595 ms
style.css
420 ms
jquery.js
2389 ms
top.js
408 ms
bg01.gif
263 ms
jquery.backstretch.js
195 ms
smoothRollOver.js
199 ms
liheight.js
204 ms
pagetop.js
197 ms
logo.png
191 ms
nav1_off.png
193 ms
nav2_off.png
203 ms
nav3_off.png
200 ms
nav4_off.png
219 ms
img_btm.png
206 ms
h2_title.png
396 ms
shop7_off.png
1558 ms
tel7.png
390 ms
shop3_off.png
1430 ms
tel3.png
421 ms
shop11_off.png
627 ms
tel11.png
585 ms
shop6_off.png
1168 ms
tel6.png
638 ms
shop4_off.png
1529 ms
tel4.png
827 ms
shop9_off.png
1863 ms
tel9.png
1024 ms
shop10_off.png
1434 ms
tel10.png
1365 ms
shop5_off.png
1944 ms
tel5.png
1637 ms
shop1_off.png
1637 ms
tel1.png
1720 ms
shop8_off.png
2126 ms
tel8.png
1839 ms
bg_foot.png
1830 ms
title_pickup.png
1906 ms
bnr_01.png
2024 ms
bnr_02.png
2040 ms
fnav1_off.png
2065 ms
fnav2_off.png
2093 ms
fnav3_off.png
2132 ms
fnav4_off.png
2214 ms
fnav5_off.png
2225 ms
analytics.js
35 ms
collect
13 ms
btn_pagetop_off.png
2089 ms
main1.jpg
3113 ms
main2.jpg
3249 ms
main3.jpg
3054 ms
main4.jpg
2875 ms
nav1_on.png
2264 ms
nav2_on.png
2099 ms
nav3_on.png
2289 ms
nav4_on.png
2276 ms
shop7_on.png
2512 ms
shop3_on.png
2485 ms
shop11_on.png
2639 ms
shop6_on.png
2479 ms
shop4_on.png
2297 ms
shop9_on.png
2283 ms
shop10_on.png
2110 ms
shop5_on.png
2063 ms
shop1_on.png
2077 ms
shop8_on.png
2009 ms
fnav1_on.png
2080 ms
fnav2_on.png
2003 ms
fnav3_on.png
2028 ms
fnav4_on.png
1956 ms
fnav5_on.png
1884 ms
btn_pagetop_on.png
1902 ms
unicus-sc.jp accessibility score
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
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.
unicus-sc.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
unicus-sc.jp SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
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 doesn't use 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 Unicus-sc.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 Unicus-sc.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.
unicus-sc.jp
Open Graph description is not detected on the main page of UNICUS Sc. 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: