Tools & Wizards About Us
bm.straightline.jp screenshot

Report Summary

  • 43

    Performance

    Renders faster than
    62% of other websites

  • 54

    Accessibility

    Visual factors better than
    that of 23% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 88

    SEO

    Google-friendlier than
    65% of websites

bm.straightline.jp

Tters - 棲み分けしやすい匿名SNS

Page Load Speed

14.3 sec in total

First Response

590 ms

Resources Loaded

13.4 sec

Page Rendered

316 ms

bm.straightline.jp screenshot

About Website

Click here to check amazing Bm Straightline content for Taiwan. Otherwise, check out these important facts you probably never knew about bm.straightline.jp

Tters(ッターズ)は、自分に合った〇〇ッターを作成し、フォローして自由につぶやける匿名SNSです。匿名だからこそ、人間関係のストレスやプレッシャーとは無縁で、自分らしく自然体でありながら自己表現が可能な空間を提供しています。SNSに疲れた人々が集まる寄り合い所でもあります。

Visit bm.straightline.jp

Key Findings

We analyzed Bm.straightline.jp page load time and found that the first response time was 590 ms and then it took 13.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

bm.straightline.jp performance score

43

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.3 s

18/100

10%

LCP (Largest Contentful Paint)

Value4.8 s

30/100

25%

SI (Speed Index)

Value9.1 s

14/100

10%

TBT (Total Blocking Time)

Value630 ms

47/100

30%

CLS (Cumulative Layout Shift)

Value0.005

100/100

15%

TTI (Time to Interactive)

Value8.7 s

36/100

10%

Network Requests Diagram

bm.straightline.jp

590 ms

tters.jp

1516 ms

css2

36 ms

normalize.css

802 ms

element.css

788 ms

Our browser made a total of 118 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Bm.straightline.jp, 92% (109 requests) were made to Tters.jp and 2% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (3.7 sec) relates to the external source Tters.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 198.6 kB (51%)

Content Size

391.4 kB

After Optimization

192.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Bm.straightline.jp main page is 391.4 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 40% of websites need less resources to load. HTML takes 159.8 kB which makes up the majority of the site volume.

HTML Optimization

-95%

Potential reduce by 151.0 kB

  • Original 159.8 kB
  • After minification 57.5 kB
  • After compression 8.8 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 102.2 kB, which is 64% 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 151.0 kB or 95% of the original size.

Image Optimization

-1%

Potential reduce by 389 B

  • Original 30.6 kB
  • After minification 30.3 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. Bm Straightline images are well optimized though.

JavaScript Optimization

-19%

Potential reduce by 29.5 kB

  • Original 157.6 kB
  • After minification 157.6 kB
  • After compression 128.0 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 29.5 kB or 19% of the original size.

CSS Optimization

-41%

Potential reduce by 17.7 kB

  • Original 43.5 kB
  • After minification 43.5 kB
  • After compression 25.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. Bm.straightline.jp needs all CSS files to be minified and compressed as it can save up to 17.7 kB or 41% of the original size.

Requests Breakdown

Number of requests can be reduced by 109 (95%)

Requests Now

115

After Optimization

6

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

bm.straightline.jp

bm.straightline.jp

590 ms

tters.jp

tters.jp

1516 ms

css2

css2

36 ms

normalize.css

normalize.css

802 ms

element.css

element.css

788 ms

style.css

style.css

838 ms

mootools-core-1.5.1.js

mootools-core-1.5.1.js

879 ms

mootools-more-1.5.1.js

mootools-more-1.5.1.js

1096 ms

common-util.js

common-util.js

1172 ms

extra.js

extra.js

1550 ms

js

js

50 ms

pub-3927695913149942

pub-3927695913149942

75 ms

33.png

33.png

303 ms

125.png

125.png

553 ms

190.png

190.png

593 ms

53.png

53.png

659 ms

160.png

160.png

569 ms

20.png

20.png

734 ms

59.png

59.png

876 ms

134.png

134.png

1150 ms

192.png

192.png

1115 ms

137.png

137.png

1189 ms

31.png

31.png

1238 ms

102.png

102.png

1315 ms

26.png

26.png

1457 ms

52.png

52.png

1677 ms

131.png

131.png

1742 ms

194.png

194.png

1769 ms

64.png

64.png

1813 ms

28.png

28.png

1904 ms

101.png

101.png

2054 ms

162.png

162.png

2239 ms

187.png

187.png

2289 ms

44.png

44.png

2346 ms

105.png

105.png

2372 ms

170.png

170.png

2484 ms

154.png

154.png

2643 ms

51.png

51.png

2801 ms

76.png

76.png

2847 ms

38.png

38.png

2907 ms

25.png

25.png

2970 ms

37.png

37.png

3040 ms

201.png

201.png

3219 ms

129.png

129.png

3359 ms

155.png

155.png

3461 ms

174.png

174.png

3456 ms

191.png

191.png

3566 ms

145.png

145.png

3528 ms

js

js

107 ms

analytics.js

analytics.js

101 ms

font

font

227 ms

font

font

233 ms

collect

collect

18 ms

icomoon.ttf

icomoon.ttf

3728 ms

82.png

82.png

3427 ms

121.png

121.png

3445 ms

2.png

2.png

3466 ms

124.png

124.png

3461 ms

30.png

30.png

3452 ms

12.png

12.png

3685 ms

163.png

163.png

3461 ms

96.png

96.png

3479 ms

106.png

106.png

3461 ms

93.png

93.png

3449 ms

171.png

171.png

3467 ms

23.png

23.png

3664 ms

199.png

199.png

3490 ms

115.png

115.png

3467 ms

63.png

63.png

3460 ms

5.png

5.png

3449 ms

88.png

88.png

3419 ms

90.png

90.png

3658 ms

107.png

107.png

3540 ms

184.png

184.png

3478 ms

176.png

176.png

3461 ms

164.png

164.png

3438 ms

98.png

98.png

3401 ms

61.png

61.png

3681 ms

128.png

128.png

3558 ms

135.png

135.png

3475 ms

7.png

7.png

3478 ms

120.png

120.png

3412 ms

57.png

57.png

3453 ms

16.png

16.png

3684 ms

166.png

166.png

3527 ms

55.png

55.png

3482 ms

32.png

32.png

3470 ms

22.png

22.png

3377 ms

156.png

156.png

3473 ms

47.png

47.png

3471 ms

144.png

144.png

3491 ms

66.png

66.png

3444 ms

173.png

173.png

3463 ms

169.png

169.png

3389 ms

3.png

3.png

3457 ms

24.png

24.png

3453 ms

198.png

198.png

3483 ms

72.png

72.png

3422 ms

18.png

18.png

3458 ms

74.png

74.png

3414 ms

97.png

97.png

3443 ms

1.png

1.png

3505 ms

188.png

188.png

3457 ms

180.png

180.png

3458 ms

57.png

57.png

3464 ms

124.png

124.png

3404 ms

35.png

35.png

3493 ms

58.png

58.png

3502 ms

133.png

133.png

3418 ms

186.png

186.png

3479 ms

187.png

187.png

3434 ms

121.png

121.png

3498 ms

125.png

125.png

3477 ms

75.png

75.png

3459 ms

137.png

137.png

3465 ms

168.png

168.png

3492 ms

16.png

16.png

3438 ms

15.png

15.png

3484 ms

Accessibility Review

bm.straightline.jp accessibility score

54

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

bm.straightline.jp best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

bm.straightline.jp SEO score

88

Search Engine Optimization Advices

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Bm.straightline.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 Bm.straightline.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

bm.straightline.jp

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