7 sec in total
679 ms
6 sec
296 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 679 ms and then it took 6.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.
unicorn.jp performance score
name
value
score
weighting
Value3.2 s
44/100
10%
Value6.2 s
11/100
25%
Value3.7 s
85/100
10%
Value610 ms
48/100
30%
Value0.054
98/100
15%
Value7.7 s
45/100
10%
679 ms
425 ms
447 ms
1088 ms
36 ms
Our browser made a total of 77 requests to load all elements on the main page. We found that 4% of them (3 requests) were addressed to the original Unicorn.jp, 60% (46 requests) were made to Sonymusic.co.jp and 14% (11 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.4 sec) relates to the external source Sonymusic.co.jp.
Page size can be reduced by 195.9 kB (12%)
1.6 MB
1.5 MB
In fact, the total size of Unicorn.jp main page is 1.6 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. 45% of websites need less resources to load. Images take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 3.4 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 1.4 kB, which is 30% 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 3.4 kB or 72% of the original size.
Potential reduce by 49.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. UNICORN images are well optimized though.
Potential reduce by 135.6 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 135.6 kB or 56% of the original size.
Potential reduce by 7.1 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. Unicorn.jp needs all CSS files to be minified and compressed as it can save up to 7.1 kB or 74% of the original size.
Number of requests can be reduced by 36 (48%)
75
39
The browser has sent 75 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 23 to 1 for JavaScripts and as a result speed up the page load time.
unicorn.jp
679 ms
top.css
425 ms
readXml.js
447 ms
s_code.js
1088 ms
conversion.js
36 ms
ga.js
55 ms
index.html
792 ms
__utm.gif
12 ms
__utm.gif
14 ms
top.css
587 ms
jquery.js
1180 ms
jquery.easing.1.3.js
608 ms
jquery.vgrid.0.1.6.js
1213 ms
liquid.js
443 ms
slide.js
591 ms
smoothscroll.js
652 ms
smartRollover.js
786 ms
jsapi
21 ms
readXml.js
797 ms
s_code.js
1011 ms
conversion.js
28 ms
s_retargeting.js
541 ms
16 ms
default+en.css
6 ms
default+en.I.js
7 ms
logo_title.png
218 ms
chara.png
210 ms
info.png
215 ms
new.png
207 ms
live.png
213 ms
media.png
243 ms
bio.png
469 ms
disco.png
469 ms
sblog.png
409 ms
special.png
465 ms
mail.png
468 ms
links.png
471 ms
bnr_abedon50.jpg
988 ms
whatsnew_header.gif
608 ms
whatsnew_bottom.gif
626 ms
bnr_ebi50dvd.jpg
1984 ms
bnr_ebi50.jpg
1042 ms
bnr_ot50.jpg
1224 ms
smam.jpg
803 ms
bnr_ot50dvd.jpg
1236 ms
bnr_egadvd.jpg
1987 ms
e-gaAL_banner.jpg
1564 ms
otweb.png
1819 ms
abe.jpg
1858 ms
dendai.jpg
1445 ms
bnr_twitter.jpg
1852 ms
banner_app.jpg
1953 ms
mobile_rocket.jpg
2211 ms
youtube_tessy.jpg
2261 ms
btn_pagetop.png
2076 ms
c.png
2153 ms
sarucorn.png
2378 ms
__utm.gif
15 ms
__utm.gif
116 ms
103 ms
gtm.js
135 ms
message.xml
2025 ms
112 ms
analytics.js
28 ms
s29268917748704
101 ms
linkid.js
42 ms
collect
54 ms
collect
89 ms
collect
39 ms
collect
35 ms
collect
37 ms
collect
49 ms
collect
72 ms
collect
70 ms
Gfeeds
343 ms
Gfeeds
770 ms
whatsnew_yajirushi.gif
219 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
Image elements do not have [alt] attributes
Links do not have a discernible name
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
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
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: