1.2 sec in total
123 ms
625 ms
464 ms
Visit app.bunch.ai now to see the best up-to-date App Bunch content for United States and also check out these interesting facts you probably never knew about 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 app.bunch.aiWe analyzed App.bunch.ai page load time and found that the first response time was 123 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 20% of websites can load faster.
app.bunch.ai performance score
name
value
score
weighting
Value2.5 s
68/100
10%
Value32.1 s
0/100
25%
Value22.9 s
0/100
10%
Value49,300 ms
0/100
30%
Value0.029
100/100
15%
Value57.3 s
0/100
10%
123 ms
53 ms
95 ms
135 ms
165 ms
Our browser made a total of 81 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original App.bunch.ai, 26% (21 requests) were made to Miro.medium.com and 21% (17 requests) were made to Glyph.medium.com. The less responsive or slowest element that took the longest time to load (323 ms) relates to the external source Miro.medium.com.
Page size can be reduced by 108.5 kB (47%)
228.6 kB
120.1 kB
In fact, the total size of App.bunch.ai main page is 228.6 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. 70% of websites need less resources to load. HTML takes 123.6 kB which makes up the majority of the site volume.
Potential reduce by 93.4 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 93.4 kB or 76% of the original size.
Potential reduce by 15.1 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, App Bunch needs image optimization as it can save up to 15.1 kB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 46 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. App.bunch.ai has all CSS files already compressed.
Number of requests can be reduced by 41 (64%)
64
23
The browser has sent 64 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 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 42 to 1 for JavaScripts and as a result speed up the page load time.
retiring-the-bunch-assessment-e38f99e406e9
123 ms
unbound.css
53 ms
manifest.b52cb8d4.js
95 ms
221.eb6d4e84.js
135 ms
main.574a4989.js
165 ms
instrumentation.c71f0248.chunk.js
160 ms
4800.b97019a4.chunk.js
138 ms
7371.4a3c1218.chunk.js
160 ms
9282.ec2603ec.chunk.js
137 ms
2837.7bf36ac5.chunk.js
181 ms
AppLayout.12c17691.chunk.js
201 ms
reporting.bbdcaa9d.chunk.js
178 ms
2953.6a4984da.chunk.js
183 ms
1752.a348f767.chunk.js
183 ms
7794.9590314e.chunk.js
194 ms
8316.18f2a6aa.chunk.js
201 ms
5472.5f6d4371.chunk.js
203 ms
4330.73510d98.chunk.js
204 ms
2981.c8b67800.chunk.js
218 ms
3115.38ecb46c.chunk.js
219 ms
5758.4d052c2f.chunk.js
221 ms
4869.15af887a.chunk.js
219 ms
9401.492bc814.chunk.js
223 ms
2307.b2a54ca4.chunk.js
222 ms
7070.02e46a7e.chunk.js
226 ms
9442.5291e270.chunk.js
224 ms
4483.0a43a5ce.chunk.js
226 ms
210.1b33e4a9.chunk.js
241 ms
864.dc58ca67.chunk.js
229 ms
9841.1bb423da.chunk.js
228 ms
3610.44f23015.chunk.js
295 ms
1018.3d424dd7.chunk.js
238 ms
9304.78e04611.chunk.js
238 ms
763.3dd24340.chunk.js
295 ms
8051.c536c001.chunk.js
296 ms
9241.b09496de.chunk.js
316 ms
5887.70c709b9.chunk.js
300 ms
5754.6687b8d5.chunk.js
297 ms
v652eace1692a40cfa3763df669d7439c1639079717194
154 ms
1*xmnmh31zwaiNBTr9ZPfb_w.jpeg
150 ms
0*u2jFwkUnS8aSyUXo.gif
323 ms
2*995_4jCfXNqCiLbHlih2KA.png
125 ms
1*NTGQg4zTTwZab2hhV7ELmg.png
124 ms
1*QDjhmGZ_CWMpD0YSk3yf4Q.jpeg
111 ms
1*Z3y8Wx_ObNsn5KciTJJbOQ.jpeg
239 ms
1*zH8ecr4Y7yV6lyZeB5j-Xg.jpeg
123 ms
1*8PDURa_xAYmwak0YF3Jexg.jpeg
140 ms
0*XBwvc9GR17gDRw3s
148 ms
1*Kwr38Lf68_rAUN72_yiGlg.png
274 ms
1*SA1LMZbKS9cVZW5S8RN4gA.jpeg
143 ms
1*atm4MEQS8u2sA6H7dmygQQ.png
256 ms
1*o5Rd-ydrlZH404dZvqcZpQ.png
220 ms
0*qrq1UVvOy2NgCscX.jpg
217 ms
1*xn0aFYvA3vgiq17kqr_SPg.jpeg
220 ms
1*OPnU0pqNE89xkcxXirgSKQ.jpeg
236 ms
1*O0VrM-PjuqH8hVJ53X7WAg.jpeg
237 ms
1*UEZXFc7XOw0sp-aWglhsyQ.jpeg
248 ms
1*Crl55Tm6yDNMoucPo1tvDg.png
246 ms
1*W_RAPQ62h0em559zluJLdQ.png
243 ms
1*xmnmh31zwaiNBTr9ZPfb_w.jpeg
317 ms
sohne-400-normal.woff
47 ms
sohne-400-normal.woff
115 ms
sohne-500-normal.woff
91 ms
sohne-500-normal.woff
94 ms
sohne-300-normal.woff
78 ms
sohne-300-normal.woff
109 ms
sohne-700-normal.woff
107 ms
sohne-700-normal.woff
108 ms
PostPage.MainContent.4dc53f59.chunk.js
224 ms
1987.e87f9d80.chunk.js
181 ms
8237.1eb3b71c.chunk.js
179 ms
7994.2c775893.chunk.js
176 ms
PostPage.RightColumnContent.3109f2af.chunk.js
165 ms
source-serif-pro-400-normal.woff
36 ms
source-serif-pro-400-normal.woff
32 ms
source-serif-pro-700-normal.woff
32 ms
source-serif-pro-700-normal.woff
29 ms
source-serif-pro-400-italic.woff
31 ms
source-serif-pro-400-italic.woff
15 ms
source-serif-pro-700-italic.woff
74 ms
source-serif-pro-700-italic.woff
75 ms
app.bunch.ai 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-*] attributes do not match their roles
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
Buttons do not have an accessible name
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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.
app.bunch.ai best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
app.bunch.ai SEO score
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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise App.bunch.ai 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 App.bunch.ai 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.
app.bunch.ai
Open Graph data is detected on the main page of App Bunch. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: