Tools & Wizards About Us
2bro.jp screenshot

Report Summary

  • 53

    Performance

    Renders faster than
    70% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 44% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

2bro.jp

2BRO. OFFICIAL PAGE

Page Load Speed

1.4 sec in total

First Response

282 ms

Resources Loaded

972 ms

Page Rendered

152 ms

2bro.jp screenshot

About Website

Welcome to 2bro.jp homepage info - get ready to check 2BRO best content for Japan right away, or after learning these important things about 2bro.jp

YouTubeで2BRO.として活動中。 PLAY WITH USがモットー。

Visit 2bro.jp

Key Findings

We analyzed 2bro.jp page load time and found that the first response time was 282 ms and then it took 1.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.

Performance Metrics

2bro.jp performance score

53

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.1 s

80/100

10%

LCP (Largest Contentful Paint)

Value6.3 s

10/100

25%

SI (Speed Index)

Value2.3 s

99/100

10%

TBT (Total Blocking Time)

Value610 ms

49/100

30%

CLS (Cumulative Layout Shift)

Value0.051

99/100

15%

TTI (Time to Interactive)

Value9.5 s

30/100

10%

Network Requests Diagram

2bro.jp

282 ms

pre_tumblelog.js

16 ms

js

322 ms

index.build.css

19 ms

css

27 ms

Our browser made a total of 74 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original 2bro.jp, 53% (39 requests) were made to Static.tumblr.com and 18% (13 requests) were made to Assets.tumblr.com. The less responsive or slowest element that took the longest time to load (358 ms) relates to the external source Assets.tumblr.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 271.4 kB (26%)

Content Size

1.0 MB

After Optimization

757.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of 2bro.jp main page is 1.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 739.2 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 83.2 kB

  • Original 104.3 kB
  • After minification 92.5 kB
  • After compression 21.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 11.7 kB, which is 11% 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 83.2 kB or 80% of the original size.

Image Optimization

-25%

Potential reduce by 187.3 kB

  • Original 739.2 kB
  • After minification 551.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. Obviously, 2BRO needs image optimization as it can save up to 187.3 kB or 25% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-0%

Potential reduce by 387 B

  • Original 147.3 kB
  • After minification 147.3 kB
  • After compression 146.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. This website has mostly compressed JavaScripts.

CSS Optimization

-1%

Potential reduce by 523 B

  • Original 37.8 kB
  • After minification 37.6 kB
  • After compression 37.3 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. 2bro.jp has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 17 (33%)

Requests Now

52

After Optimization

35

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 52 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 2BRO. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

2bro.jp

2bro.jp

282 ms

pre_tumblelog.js

pre_tumblelog.js

16 ms

js

js

322 ms

index.build.css

index.build.css

19 ms

css

css

27 ms

main.min.css

main.min.css

20 ms

modernizr.js

modernizr.js

20 ms

queryloader2.min.js

queryloader2.min.js

21 ms

bilmur.min.js

bilmur.min.js

47 ms

tumblelog_post_message_queue.js

tumblelog_post_message_queue.js

18 ms

stylesheet.css

stylesheet.css

14 ms

jquery.js

jquery.js

21 ms

candice_plugins.js

candice_plugins.js

20 ms

tweenmax.min.js

tweenmax.min.js

21 ms

scrolltoplugin.min.js

scrolltoplugin.min.js

20 ms

index.build.js

index.build.js

24 ms

modernizr.js

modernizr.js

44 ms

main.min.css

main.min.css

47 ms

queryloader2.min.js

queryloader2.min.js

46 ms

jquery.js

jquery.js

87 ms

candice_plugins.js

candice_plugins.js

86 ms

scrolltoplugin.min.js

scrolltoplugin.min.js

45 ms

tweenmax.min.js

tweenmax.min.js

85 ms

avatar_f1ee18bf12e6_128.pnj

avatar_f1ee18bf12e6_128.pnj

342 ms

like_iframe.html

like_iframe.html

358 ms

tumblr_pqgf1dQPn51ukfuj1o1_1280.jpg

tumblr_pqgf1dQPn51ukfuj1o1_1280.jpg

339 ms

avatar_f1ee18bf12e6_64.pnj

avatar_f1ee18bf12e6_64.pnj

347 ms

color-bordered-n.png

color-bordered-n.png

245 ms

tumblr_static_e52yfk1k4b48kkwwsgck884cc.jpg

tumblr_static_e52yfk1k4b48kkwwsgck884cc.jpg

349 ms

facebook.png

facebook.png

243 ms

twitter.png

twitter.png

245 ms

g_.png

g_.png

245 ms

impixu

impixu

207 ms

g.gif

g.gif

177 ms

impixu

impixu

128 ms

font

font

183 ms

AlternateGothicNo2-webfont.woff

AlternateGothicNo2-webfont.woff

93 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

166 ms

analytics.html

analytics.html

90 ms

login_check.html

login_check.html

31 ms

facebook.png

facebook.png

91 ms

twitter.png

twitter.png

90 ms

g_.png

g_.png

91 ms

color-bordered-n.png

color-bordered-n.png

94 ms

theee-dots-black.svg

theee-dots-black.svg

89 ms

pinterest.png

pinterest.png

102 ms

ball-triangle-grey.svg

ball-triangle-grey.svg

50 ms

g.gif

g.gif

73 ms

consent

consent

93 ms

color-bordered-n.png

color-bordered-n.png

16 ms

tumblr_static_e52yfk1k4b48kkwwsgck884cc.jpg

tumblr_static_e52yfk1k4b48kkwwsgck884cc.jpg

39 ms

theee-dots-black.svg

theee-dots-black.svg

14 ms

facebook.png

facebook.png

14 ms

twitter.png

twitter.png

14 ms

g_.png

g_.png

15 ms

pinterest.png

pinterest.png

15 ms

avatar_f1ee18bf12e6_128.pnj

avatar_f1ee18bf12e6_128.pnj

28 ms

avatar_f1ee18bf12e6_128.pnj

avatar_f1ee18bf12e6_128.pnj

24 ms

tumblr_pqgf1dQPn51ukfuj1o1_1280.jpg

tumblr_pqgf1dQPn51ukfuj1o1_1280.jpg

37 ms

tumblr_pqgf1dQPn51ukfuj1o1_1280.jpg

tumblr_pqgf1dQPn51ukfuj1o1_1280.jpg

36 ms

avatar_f1ee18bf12e6_64.pnj

avatar_f1ee18bf12e6_64.pnj

36 ms

avatar_f1ee18bf12e6_128.pnj

avatar_f1ee18bf12e6_128.pnj

36 ms

theee-dots-black.svg

theee-dots-black.svg

240 ms

facebook.png

facebook.png

103 ms

twitter.png

twitter.png

106 ms

g_.png

g_.png

106 ms

color-bordered-n.png

color-bordered-n.png

101 ms

pinterest.png

pinterest.png

103 ms

cs.js

cs.js

5 ms

header.build.js

header.build.js

2 ms

exceptions.js

exceptions.js

5 ms

index.build.js

index.build.js

34 ms

cdn.json

cdn.json

4 ms

g.gif

g.gif

7 ms

Accessibility Review

2bro.jp accessibility score

77

Accessibility Issues

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

High

Buttons do not have an accessible name

High

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

2bro.jp best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

2bro.jp SEO score

86

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 2bro.jp can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that 2bro.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.

Social Sharing Optimization

2bro.jp

Open Graph data is detected on the main page of 2BRO. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: