3 sec in total
17 ms
2.6 sec
430 ms
Click here to check amazing UNICORN content for Japan. Otherwise, check out these important facts you probably never knew about unicorn.jp
ユニコーンのオフィシャルサイト
Visit unicorn.jpWe analyzed Unicorn.jp page load time and found that the first response time was 17 ms and then it took 3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
unicorn.jp performance score
name
value
score
weighting
Value3.1 s
47/100
10%
Value28.8 s
0/100
25%
Value4.2 s
77/100
10%
Value1,200 ms
20/100
30%
Value0.074
95/100
15%
Value13.7 s
10/100
10%
17 ms
358 ms
349 ms
368 ms
353 ms
Our browser made a total of 70 requests to load all elements on the main page. We found that 37% of them (26 requests) were addressed to the original Unicorn.jp, 19% (13 requests) were made to Sma.co.jp and 10% (7 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Unicorn.jp.
Page size can be reduced by 57.3 kB (1%)
4.0 MB
4.0 MB
In fact, the total size of Unicorn.jp main page is 4.0 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. 70% of websites need less resources to load. Images take 3.9 MB which makes up the majority of the site volume.
Potential reduce by 20.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. This page needs HTML code to be minified as it can gain 6.7 kB, which is 25% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 20.7 kB or 76% of the original size.
Potential reduce by 32.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. UNICORN images are well optimized though.
Potential reduce by 3.3 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. This website has mostly compressed JavaScripts.
Potential reduce by 460 B
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. Unicorn.jp needs all CSS files to be minified and compressed as it can save up to 460 B or 23% of the original size.
Number of requests can be reduced by 26 (39%)
67
41
The browser has sent 67 CSS, Javascripts, AJAX and image requests in order to completely render the main page of UNICORN. 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 as a result speed up the page load time.
unicorn.jp
17 ms
unicorn.jp
358 ms
top.css
349 ms
jquery.js
368 ms
jquery.easing.1.3.js
353 ms
jquery.vgrid.0.1.6.js
196 ms
liquid.js
365 ms
slide.js
362 ms
banner.js
547 ms
smoothscroll.js
696 ms
smartRollover.js
691 ms
jsapi
25 ms
readXml.js
707 ms
js
56 ms
s_retargeting.js
688 ms
loader.js
20 ms
gtm.js
88 ms
ver2_banner_list
909 ms
ver2_banner_list
1039 ms
message.xml
368 ms
bg_visual1115.jpg
563 ms
logo_title.png
370 ms
chara.png
371 ms
info.png
370 ms
live.png
369 ms
media.png
853 ms
bio.png
605 ms
disco.png
852 ms
goods.png
851 ms
special.png
852 ms
links.png
865 ms
fc.png
943 ms
c.png
1052 ms
js
146 ms
js
146 ms
analytics.js
140 ms
js
214 ms
edge.js
212 ms
uwt.js
199 ms
fbevents.js
352 ms
td.min.js
386 ms
collect
236 ms
collect
231 ms
linkid.js
215 ms
adsct
343 ms
adsct
343 ms
369821989886395
95 ms
collect
62 ms
a_unicorn_of_accesslog
53 ms
collect
35 ms
collect
47 ms
collect
33 ms
collect
39 ms
collect
34 ms
collect
17 ms
js
57 ms
js
54 ms
ga-audiences
14 ms
1050350075041433
176 ms
628fe5e0da75a8c579251240116b4.jpg
241 ms
4165aee3618ba2fd962fea1577a7a.jpg
189 ms
ab9e8d88a121674b65822a476c07f.jpg
192 ms
46f4880b96a6dc3f82fa7797aa30c.jpg
206 ms
70aedb1df8c591b97c0aa50d17aec.jpg
202 ms
511bc7a553c91ba8745d82b84f68a.jpg
200 ms
0dbbbee9ed5f440c3c59cef2a17c6.png
281 ms
e6ebfe87cd2ad663a8f89d2541f63.png
374 ms
84fc624cc75e9a70ef1359e603d58.jpg
388 ms
c4f231f88fd4d6cceb47a17e0cb67.png
395 ms
0dd28afad423285bfb5fafb5a31ae.png
380 ms
unicorn.jp 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
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>).
unicorn.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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
unicorn.jp 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
N/A
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Unicorn.jp can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is Japanese. Our system also found out that Unicorn.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.
unicorn.jp
Open Graph description is not detected on the main page of UNICORN. 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: