17.1 sec in total
1 sec
5.9 sec
10.2 sec
Click here to check amazing BRID content. Otherwise, check out these important facts you probably never knew about brid.tokyo
プロダクトからコンセプト(概念/価値)を変えていくライフスタイルブランド
Visit brid.tokyoWe analyzed Brid.tokyo page load time and found that the first response time was 1 sec and then it took 16.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
brid.tokyo performance score
name
value
score
weighting
Value7.0 s
1/100
10%
Value13.7 s
0/100
25%
Value17.8 s
0/100
10%
Value2,400 ms
5/100
30%
Value0.717
7/100
15%
Value18.9 s
3/100
10%
1008 ms
231 ms
335 ms
338 ms
80 ms
Our browser made a total of 72 requests to load all elements on the main page. We found that 86% of them (62 requests) were addressed to the original Brid.tokyo, 3% (2 requests) were made to Netdna.bootstrapcdn.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (3.7 sec) belongs to the original domain Brid.tokyo.
Page size can be reduced by 315.0 kB (2%)
15.0 MB
14.7 MB
In fact, the total size of Brid.tokyo main page is 15.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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 14.6 MB which makes up the majority of the site volume.
Potential reduce by 69.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 69.3 kB or 82% of the original size.
Potential reduce by 70.2 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. BRID images are well optimized though.
Potential reduce by 108.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 108.9 kB or 54% of the original size.
Potential reduce by 66.7 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. Brid.tokyo needs all CSS files to be minified and compressed as it can save up to 66.7 kB or 82% of the original size.
Number of requests can be reduced by 24 (35%)
69
45
The browser has sent 69 CSS, Javascripts, AJAX and image requests in order to completely render the main page of BRID. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
www.brid.tokyo
1008 ms
style.css
231 ms
slick.css
335 ms
drawer.min.css
338 ms
font-awesome.css
80 ms
js
126 ms
sb-instagram-2-2.min.css
332 ms
style.min.css
516 ms
styles.css
499 ms
styles.css
476 ms
jquery-2.2.4.min.js
55 ms
ajaxzip3.js
82 ms
jquery.min.js
67 ms
sl.js
340 ms
drawer.min.js
92 ms
slick.min.js
447 ms
act.js
691 ms
iscroll-lite.js
710 ms
img.js
693 ms
scripts.js
700 ms
jquery.form.min.js
706 ms
scripts.js
702 ms
wp-embed.min.js
711 ms
sb-instagram-2-2.min.js
712 ms
css
55 ms
analytics.js
249 ms
wp-emoji-release.min.js
446 ms
zozotownlogo-sp.jpg
350 ms
zozotownlogo.jpg
339 ms
logo.jpg
344 ms
TOP-1-2018.04.jpg
1245 ms
TOP-2-2018.04.jpg
1211 ms
TOP-3-2018.04.jpg
3688 ms
TOP-4-2018.04.jpg
1083 ms
TOP-5-2018.04.jpg
1575 ms
TOP-6-2018.04.jpg
1422 ms
003236_m01.jpg
1261 ms
000274_k01.jpg
1379 ms
001412_m02new.jpg
1421 ms
003275_m10-1.jpg
1432 ms
003276_m06.jpg
2544 ms
003275_m023.jpg
1600 ms
003269_m03.jpg
1602 ms
003113_m01.jpg
1625 ms
003280_c01.jpg
1751 ms
003275_mc01-e1596072264783.jpg
1754 ms
003276_m01.jpg
1752 ms
003279_m01.jpg
1768 ms
003278_m01.jpg
1937 ms
003269_c01.jpg
1920 ms
001447_m01.jpg
1923 ms
001446_m01.jpg
1926 ms
003277_c02.jpg
2096 ms
003268_c02.jpg
1796 ms
003266_c01.jpg
1790 ms
003272_d02.jpg
1796 ms
placeholder.png
1949 ms
fontawesome-webfont.woff
72 ms
collect
363 ms
119415079_424771931825584_2791259961145563074_nfull.jpg
1490 ms
118916814_329204511471381_3068519691461231031_nfull.jpg
1499 ms
118728946_311896370071983_1114038902002964037_nfull.jpg
1658 ms
117790201_1083972965338400_4174125223404355038_nfull.jpg
1656 ms
116435577_119038552981774_1289259246602903805_nfull.jpg
1667 ms
108593596_559582044737237_5226850352332960243_nfull.jpg
1721 ms
106484601_605692036725560_5206804115715607448_nfull.jpg
1821 ms
106689933_835123153561711_4624273301741611030_nfull.jpg
1823 ms
100958657_344792113157168_5771390268988039271_nfull.jpg
1530 ms
89821015_145393576757003_6287889896711900241_nfull.jpg
1459 ms
87402723_239464177222100_1603012350794106255_nfull.jpg
1464 ms
88276345_858200474627921_1530422128797404172_nfull.jpg
1502 ms
ajax-loader.gif
234 ms
brid.tokyo accessibility score
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 input fields do not have accessible names
ARIA toggle fields do not have accessible names
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
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>).
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.
brid.tokyo 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
Browser errors were logged to the console
brid.tokyo 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
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Brid.tokyo can be misinterpreted by Google and other search engines. Our service has detected that English 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 Brid.tokyo 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.
brid.tokyo
Open Graph description is not detected on the main page of BRID. 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: