Tools & Wizards About Us
staging-app.bunch.ai screenshot

Report Summary

  • 53

    Performance

    Renders faster than
    70% of other websites

  • 91

    Accessibility

    Visual factors better than
    that of 76% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 99

    SEO

    Google-friendlier than
    93% of websites

staging-app.bunch.ai

Retiring the Bunch Assessment. There’s been a lot of good news at… | by Darja Gutnick | Medium

Page Load Speed

1.1 sec in total

First Response

128 ms

Resources Loaded

877 ms

Page Rendered

137 ms

staging-app.bunch.ai screenshot

About Website

Welcome to staging-app.bunch.ai homepage info - get ready to check Staging App Bunch best content for United States right away, or after learning these important things about staging-app.bunch.ai

There’s been a lot of good news at BUNCH lately, but today I’ve got a bittersweet update to share about the Bunch Assessment, the SaaS platform we launched in 2017 for building high performance…

Visit staging-app.bunch.ai

Key Findings

We analyzed Staging-app.bunch.ai page load time and found that the first response time was 128 ms and then it took 1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.

Performance Metrics

staging-app.bunch.ai performance score

53

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.5 s

2/100

10%

LCP (Largest Contentful Paint)

Value6.5 s

9/100

25%

SI (Speed Index)

Value6.5 s

39/100

10%

TBT (Total Blocking Time)

Value190 ms

91/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value7.5 s

47/100

10%

Network Requests Diagram

staging-app.bunch.ai

128 ms

retiring-the-bunch-assessment-e38f99e406e9

484 ms

unbound.css

39 ms

manifest.8f22140e.js

58 ms

9865.1496d74a.js

91 ms

Our browser made a total of 53 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Staging-app.bunch.ai, 55% (29 requests) were made to Cdn-client.medium.com and 32% (17 requests) were made to Glyph.medium.com. The less responsive or slowest element that took the longest time to load (484 ms) relates to the external source Darja-bunch.medium.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.1 kB (0%)

Content Size

387.8 kB

After Optimization

386.6 kB

  • Images
  • JavaScript
  • CSS

In fact, the total size of Staging-app.bunch.ai main page is 387.8 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. Javascripts take 378.0 kB which makes up the majority of the site volume.

HTML Optimization

-0%

Potential reduce by -8 B

  • Original 0 B

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 web page is already compressed.

Image Optimization

-4%

Potential reduce by 310 B

  • Original 8.7 kB
  • After minification 8.4 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. Staging App Bunch images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 770 B

  • Original 378.0 kB
  • After minification 378.0 kB
  • After compression 377.3 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

-6%

Potential reduce by 60 B

  • Original 1.0 kB
  • After minification 1.0 kB
  • After compression 960 B

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. Staging-app.bunch.ai has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 30 (86%)

Requests Now

35

After Optimization

5

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

staging-app.bunch.ai

staging-app.bunch.ai

128 ms

retiring-the-bunch-assessment-e38f99e406e9

retiring-the-bunch-assessment-e38f99e406e9

484 ms

unbound.css

unbound.css

39 ms

manifest.8f22140e.js

manifest.8f22140e.js

58 ms

9865.1496d74a.js

9865.1496d74a.js

91 ms

main.03a26c24.js

main.03a26c24.js

108 ms

instrumentation.d9108df7.chunk.js

instrumentation.d9108df7.chunk.js

77 ms

reporting.ff22a7a5.chunk.js

reporting.ff22a7a5.chunk.js

78 ms

5049.d1ead72d.chunk.js

5049.d1ead72d.chunk.js

80 ms

4810.6318add7.chunk.js

4810.6318add7.chunk.js

76 ms

6618.db187378.chunk.js

6618.db187378.chunk.js

97 ms

1386.014e2ad3.chunk.js

1386.014e2ad3.chunk.js

98 ms

9977.343f5002.chunk.js

9977.343f5002.chunk.js

102 ms

5250.fc15c18c.chunk.js

5250.fc15c18c.chunk.js

102 ms

8261.80c0631e.chunk.js

8261.80c0631e.chunk.js

111 ms

7975.b019beb1.chunk.js

7975.b019beb1.chunk.js

110 ms

2648.a582e725.chunk.js

2648.a582e725.chunk.js

115 ms

2712.0f6c85f5.chunk.js

2712.0f6c85f5.chunk.js

115 ms

2793.01d2b056.chunk.js

2793.01d2b056.chunk.js

120 ms

1530.2779d8ee.chunk.js

1530.2779d8ee.chunk.js

133 ms

3735.ca2f95e3.chunk.js

3735.ca2f95e3.chunk.js

125 ms

5642.0ebb50fd.chunk.js

5642.0ebb50fd.chunk.js

131 ms

6546.7e5d2ee6.chunk.js

6546.7e5d2ee6.chunk.js

135 ms

6834.f2d3924e.chunk.js

6834.f2d3924e.chunk.js

157 ms

2420.0330d157.chunk.js

2420.0330d157.chunk.js

140 ms

2106.21ff89d3.chunk.js

2106.21ff89d3.chunk.js

145 ms

6696.92b2dfc3.chunk.js

6696.92b2dfc3.chunk.js

147 ms

5832.a567559e.chunk.js

5832.a567559e.chunk.js

163 ms

3366.1571a1d5.chunk.js

3366.1571a1d5.chunk.js

157 ms

6040.6ceb7f43.chunk.js

6040.6ceb7f43.chunk.js

155 ms

4391.fd55a702.chunk.js

4391.fd55a702.chunk.js

170 ms

PostPage.MainContent.3c324843.chunk.js

PostPage.MainContent.3c324843.chunk.js

181 ms

vcd15cbe7772f49c399c6a5babf22c1241717689176015

vcd15cbe7772f49c399c6a5babf22c1241717689176015

56 ms

1*dmbNkD5D-u45r44go_cf0g.png

1*dmbNkD5D-u45r44go_cf0g.png

49 ms

1*xmnmh31zwaiNBTr9ZPfb_w.jpeg

1*xmnmh31zwaiNBTr9ZPfb_w.jpeg

67 ms

1*xmnmh31zwaiNBTr9ZPfb_w.jpeg

1*xmnmh31zwaiNBTr9ZPfb_w.jpeg

82 ms

sohne-400-normal.woff

sohne-400-normal.woff

38 ms

sohne-400-normal.woff

sohne-400-normal.woff

67 ms

sohne-500-normal.woff

sohne-500-normal.woff

44 ms

sohne-500-normal.woff

sohne-500-normal.woff

38 ms

sohne-300-normal.woff

sohne-300-normal.woff

50 ms

sohne-300-normal.woff

sohne-300-normal.woff

32 ms

sohne-700-normal.woff

sohne-700-normal.woff

58 ms

sohne-700-normal.woff

sohne-700-normal.woff

62 ms

source-serif-pro-400-normal.woff

source-serif-pro-400-normal.woff

35 ms

source-serif-pro-400-normal.woff

source-serif-pro-400-normal.woff

21 ms

source-serif-pro-700-normal.woff

source-serif-pro-700-normal.woff

35 ms

source-serif-pro-700-normal.woff

source-serif-pro-700-normal.woff

36 ms

source-serif-pro-400-italic.woff

source-serif-pro-400-italic.woff

36 ms

source-serif-pro-400-italic.woff

source-serif-pro-400-italic.woff

22 ms

source-serif-pro-700-italic.woff

source-serif-pro-700-italic.woff

49 ms

source-serif-pro-700-italic.woff

source-serif-pro-700-italic.woff

49 ms

main.js

main.js

14 ms

Accessibility Review

staging-app.bunch.ai accessibility score

91

Accessibility Issues

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

staging-app.bunch.ai 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

General

Impact

Issue

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

staging-app.bunch.ai SEO score

99

Search Engine Optimization Advices

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

    EN

  • Language Claimed

    N/A

  • Encoding

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Staging-app.bunch.ai 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 Staging-app.bunch.ai main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

staging-app.bunch.ai

Open Graph description is not detected on the main page of Staging App Bunch. 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: