9.5 sec in total
577 ms
6.4 sec
2.6 sec
Visit shellbear.com now to see the best up-to-date Shellbear content and also check out these interesting facts you probably never knew about shellbear.com
銀座・有楽町で雑誌や口コミで人気・おすすめの美容室シェルベアーの公式サイト。全席カーテンで仕切られ、完全個室のシャンプー台を完備したヘアサロンです。東銀座駅から徒歩2分。新橋駅から徒歩8分。
Visit shellbear.comWe analyzed Shellbear.com page load time and found that the first response time was 577 ms and then it took 9 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
shellbear.com performance score
name
value
score
weighting
Value8.1 s
0/100
10%
Value12.6 s
0/100
25%
Value13.7 s
2/100
10%
Value450 ms
63/100
30%
Value0.008
100/100
15%
Value11.9 s
17/100
10%
577 ms
1835 ms
387 ms
44 ms
1170 ms
Our browser made a total of 76 requests to load all elements on the main page. We found that 71% of them (54 requests) were addressed to the original Shellbear.com, 5% (4 requests) were made to Img21.shop-pro.jp and 5% (4 requests) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (2.3 sec) belongs to the original domain Shellbear.com.
Page size can be reduced by 729.8 kB (5%)
16.2 MB
15.5 MB
In fact, the total size of Shellbear.com main page is 16.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. 60% of websites need less resources to load. Images take 15.4 MB which makes up the majority of the site volume.
Potential reduce by 56.5 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 14.4 kB, which is 21% 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 56.5 kB or 83% of the original size.
Potential reduce by 259.7 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. Shellbear images are well optimized though.
Potential reduce by 14.4 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 399.2 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. Shellbear.com needs all CSS files to be minified and compressed as it can save up to 399.2 kB or 82% of the original size.
Number of requests can be reduced by 19 (27%)
70
51
The browser has sent 70 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Shellbear. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
shellbear.com
577 ms
shellbear.com
1835 ms
view-d6b54e7723c987341abd70d8c3a369e39c16542f3179aa5696f33304cc04209d.css
387 ms
all.css
44 ms
1-3cccd6524fec46f7b6578a4410455e22.css
1170 ms
2-46d6bdae78169e7b51fd2af9239b8607.css
981 ms
13-18f52db2eec15aff3b90ed23737b9a8d.css
597 ms
14-cf7b5ac4c1bc3ac7e6c2629cd193dcfe.css
597 ms
5-5b154941fa8bc90f4af58cd2b7f0ac0a.css
1185 ms
view-3bc88a0e6410831f43682b6bb9bd1e6cc86e72d1dbd3b472fff230a7a797aa12.js
1230 ms
jquery.min.js
38 ms
ofi.js
45 ms
jquery.matchHeight.js
56 ms
4-67059252bfaab6f5854d6c258ec4b827.js
791 ms
15-27766f7f253c55e082376b092bcf2f1e.js
789 ms
7-a642913dc45c3b0e692d566c68e49b4a.js
984 ms
js
83 ms
css2
30 ms
ga.js
272 ms
182092823.png
290 ms
embed
520 ms
embed
681 ms
182092817.png
108 ms
182092813.png
112 ms
182092809.png
111 ms
top-mask.png
242 ms
top1.png
615 ms
f0801947ab2afe257a83e2e518f3b0a4.jpg
429 ms
scroll.png
242 ms
dac0d1506ef64d73651d1442b2e0181c.jpg
623 ms
947fe5edcfbcd4944b5dc939b1a7559f.jpg
615 ms
feature1.jpg
811 ms
feature2.jpg
1586 ms
feature3.jpg
1023 ms
feature4.jpg
1196 ms
menu1.jpg
811 ms
menu2.jpg
826 ms
menu3.jpg
1006 ms
menu4.jpg
1005 ms
menu5.jpg
1024 ms
B047855916.jpg
1977 ms
shellbear.com
1789 ms
B046272481.jpg
1221 ms
B034890421.jpg
1422 ms
160607_other_0252.JPG
1978 ms
B008772001.jpg
1428 ms
B007501514.jpg
1817 ms
b6803f49114cb96ef27605f9c8c24127.jpg
1636 ms
cdf74f6c986be3406708833fa37d1771.jpg
1788 ms
B112183528.jpg
1834 ms
cb80a4d743a26f40c6aaafcda0500cdc.jpeg
1987 ms
B111818019.jpg
1987 ms
B137094487.jpg
2025 ms
B111856448%20(2).jpg
2041 ms
B111856472%20(1).jpg
2175 ms
ae9cc72c5ac23713c1cabfd860d2759b.jpg
2173 ms
cbba5e2c0182ca1869921b480d437647.jpg
2182 ms
9c7904a63a3608bffc3e7f2c00d8143d.jpg
2187 ms
baf9b9f7f7e09d535ccaec54609fa446.jpg
2225 ms
-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFE8j75g.woff
104 ms
KFOlCnqEu92Fr1MmSU5vAA.woff
119 ms
fa-solid-900.woff
52 ms
fa-regular-400.woff
39 ms
3f8d4c59fcad746401330140cb9a51dd.jpg
2223 ms
__utm.gif
52 ms
748210266a69ec292cc906e1b08e17e3.png
2325 ms
4f8e407c693e73ab3ad07f0f966210f1.png
2330 ms
js
34 ms
search.js
5 ms
geometry.js
7 ms
main.js
13 ms
3656d00d7eb2297061a49fb0ffe8b72c.jpeg
1958 ms
50e89975ae86b7b3299d15d0cbf43126.jpg
1811 ms
2.jpg
1838 ms
3077762e9af5eeb7fca102e018667ddf.jpg
1963 ms
page-top.png
1813 ms
shellbear.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.
Definition list items are not wrapped in <dl> elements
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
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
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
shellbear.com 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
shellbear.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
![]()
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Shellbear.com can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Shellbear.com 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.
shellbear.com
Open Graph description is not detected on the main page of Shellbear. 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: