6.4 sec in total
775 ms
5.3 sec
275 ms
Click here to check amazing Elizabeth content for Japan. Otherwise, check out these important facts you probably never knew about elizabeth.jp
ビボ、ポアトル、ラクオリ2、リトルレディリュクス、シュガードールなどを取り扱うエリザベス(伊勢半グループ)の公式サイトです。通信販売も対応しております。
Visit elizabeth.jpWe analyzed Elizabeth.jp page load time and found that the first response time was 775 ms and then it took 5.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
elizabeth.jp performance score
name
value
score
weighting
Value5.5 s
6/100
10%
Value21.3 s
0/100
25%
Value11.1 s
6/100
10%
Value1,090 ms
24/100
30%
Value0.49
17/100
15%
Value24.1 s
0/100
10%
775 ms
329 ms
343 ms
351 ms
8 ms
Our browser made a total of 108 requests to load all elements on the main page. We found that 78% of them (84 requests) were addressed to the original Elizabeth.jp, 4% (4 requests) were made to Platform.twitter.com and 2% (2 requests) were made to Staticxx.facebook.com. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Elizabeth.jp.
Page size can be reduced by 261.7 kB (13%)
2.0 MB
1.8 MB
In fact, the total size of Elizabeth.jp main page is 2.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. 55% of websites need less resources to load. Images take 1.9 MB which makes up the majority of the site volume.
Potential reduce by 41.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. This page needs HTML code to be minified as it can gain 8.9 kB, which is 17% 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 41.1 kB or 78% of the original size.
Potential reduce by 131.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. Elizabeth images are well optimized though.
Potential reduce by 74.9 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 74.9 kB or 59% of the original size.
Potential reduce by 13.8 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. Elizabeth.jp needs all CSS files to be minified and compressed as it can save up to 13.8 kB or 75% of the original size.
Number of requests can be reduced by 49 (46%)
106
57
The browser has sent 106 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Elizabeth. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
elizabeth.jp
775 ms
style.css
329 ms
unique.css
343 ms
top.css
351 ms
jquery.min.js
8 ms
rollover.js
359 ms
smoothScroll.js
384 ms
heightLine.js
400 ms
footerFixed.js
493 ms
jcarousellite_1.0.1.js
512 ms
jquery.easing.min.js
525 ms
unique.css
541 ms
shadowbox.css
576 ms
shadowbox.js
763 ms
line-button.js
525 ms
cal.css
483 ms
cal.js
506 ms
basic.css
373 ms
layout.css
395 ms
head_bk.gif
203 ms
h1_rogo.png
201 ms
category_eye_off.png
212 ms
category_span.png
203 ms
category_lip_off.png
191 ms
category_base_off.png
192 ms
category_skin_off.png
350 ms
category_eyelid_off.png
355 ms
category_nail_off.png
375 ms
category_goods_off.png
416 ms
btn_cart_off.png
378 ms
btn_tw.png
416 ms
pc_SB_matstay.jpg
1638 ms
pc_tint08.jpg
1685 ms
pc_pt%20peeling.jpg
1744 ms
pc_pt%20blush.jpg
1797 ms
pc_SD_aon.jpg
1465 ms
h2_top_info.gif
587 ms
pc_info_2.jpg
1164 ms
arrow_basic.gif
1360 ms
pc_info_ivent.jpg
1743 ms
h2_top_pickup.gif
1648 ms
0218.jpg
1802 ms
h2_top_hit.gif
1831 ms
btn_bonbon02_off.png
1852 ms
btn_bibo_off.png
1918 ms
btn_poretol_off.png
1935 ms
btn_sugardoll_off.png
1980 ms
btn_sugaobore_off.png
1969 ms
h2_top_new.gif
2013 ms
bunner_m_pub.jpg
2021 ms
bunner_m_sugar_all.jpg
2091 ms
bunner_m_pt_blushjpg.jpg
2127 ms
bunner_m_poretol.jpg
2133 ms
bunner_m_futae.jpg
2159 ms
bunner_faq.jpg
2183 ms
icon_new.png
724 ms
widgets.js
19 ms
sdk.js
269 ms
tag.js
22 ms
ga.js
20 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
39 ms
__utm.gif
19 ms
tag
15 ms
bunner_m_history.jpg
2009 ms
h2_top_pickupitem.gif
2084 ms
bon_tint02.jpg
2134 ms
bibo_blow.jpg
2112 ms
sugar_all02.jpg
2148 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html
19 ms
proeye.jpg
2159 ms
jot
103 ms
doran.jpg
2041 ms
bon_stick.jpg
2095 ms
h2_top_list.gif
2100 ms
btn_bonbon_off.png
2149 ms
btn_cutiecutie_off.png
2114 ms
128 ms
btn_littlelady_off.png
2112 ms
xd_arbiter.php
213 ms
xd_arbiter.php
418 ms
btn_tsukematsuge_off.png
1983 ms
btn_quealy_off.png
1457 ms
btn_futaemabuta_off.png
1278 ms
btn_purenatural_off.png
1258 ms
btn_dorandoll_off.png
1074 ms
btn_makekeep_off.png
1058 ms
btn_easylock_off.png
1072 ms
btn_marks_off.png
1053 ms
btn_moiscture_off.png
1059 ms
btn_truecolors_off.png
1080 ms
btn_marypere_off.png
1088 ms
btn_clearance_off.png
1083 ms
h2_top_guide.gif
1086 ms
ico_souryou.gif
1052 ms
bunner_s_pink.jpg
1032 ms
bunner_s_attention.gif
1076 ms
bunner_sw_shinsai.gif
1091 ms
arrow_basic_s.gif
1092 ms
82x20.png
186 ms
oct.js
27 ms
ya.js
318 ms
adsct
86 ms
adsct
48 ms
like.php
80 ms
wy1X4hBW7e7.js
486 ms
LVx-xkvaJ0b.png
548 ms
pb.js
559 ms
335 ms
elizabeth.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
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.
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 IDs are not unique
elizabeth.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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
elizabeth.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
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 Elizabeth.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 Elizabeth.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.
elizabeth.jp
Open Graph description is not detected on the main page of Elizabeth. 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: