694 ms in total
69 ms
517 ms
108 ms
Visit cabbi.bo now to see the best up-to-date Cabbi content for India and also check out these interesting facts you probably never knew about cabbi.bo
Long Live Synesthesia
Visit cabbi.boWe analyzed Cabbi.bo page load time and found that the first response time was 69 ms and then it took 625 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 10% of websites can load faster.
cabbi.bo performance score
name
value
score
weighting
Value2.8 s
56/100
10%
Value3.4 s
67/100
25%
Value4.2 s
78/100
10%
Value1,400 ms
16/100
30%
Value0
100/100
15%
Value6.4 s
60/100
10%
69 ms
15 ms
62 ms
89 ms
110 ms
Our browser made a total of 44 requests to load all elements on the main page. We found that 68% of them (30 requests) were addressed to the original Cabbi.bo, 16% (7 requests) were made to Player.vimeo.com and 7% (3 requests) were made to F.vimeocdn.com. The less responsive or slowest element that took the longest time to load (150 ms) relates to the external source F.vimeocdn.com.
Page size can be reduced by 383.4 kB (72%)
531.2 kB
147.8 kB
In fact, the total size of Cabbi.bo main page is 531.2 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. 55% of websites need less resources to load. Javascripts take 390.9 kB which makes up the majority of the site volume.
Potential reduce by 14.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 14.4 kB or 72% of the original size.
Potential reduce by 262.8 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 262.8 kB or 67% of the original size.
Potential reduce by 106.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. Cabbi.bo needs all CSS files to be minified and compressed as it can save up to 106.3 kB or 88% of the original size.
Number of requests can be reduced by 29 (69%)
42
13
The browser has sent 42 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Cabbi. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 30 to 1 for JavaScripts and as a result speed up the page load time.
cabbi.bo
69 ms
main.css
15 ms
three.js
62 ms
jquery.min.js
89 ms
stats.min.js
110 ms
dat.gui.min.js
108 ms
underscore.js
107 ms
Tween.js
118 ms
ShaderLoader.js
120 ms
AudioController.js
104 ms
AudioTexture.js
122 ms
LoadedAudio.js
107 ms
TextCreator.js
114 ms
TextParticles.js
119 ms
ObjectControls.js
119 ms
RiggedSkeleton.js
114 ms
ParticleUtils.js
116 ms
PhysicsRenderer.js
119 ms
ConvexGeometry.js
116 ms
Loader.js
122 ms
SnowflakeGeometry.js
124 ms
initSnowflake.js
124 ms
Global.js
124 ms
Link.js
119 ms
Section.js
141 ms
Ball.js
123 ms
PhysicsText.js
141 ms
links.js
138 ms
analytics.js
19 ms
collect
59 ms
GeosansLight.ttf
50 ms
loadGif.gif
44 ms
96964491
89 ms
84019684
99 ms
96993614
93 ms
96993970
103 ms
78139371
101 ms
96872530
100 ms
player.js
150 ms
player.css
80 ms
ga.js
95 ms
vuid.min.js
95 ms
86874956
27 ms
__utm.gif
39 ms
cabbi.bo accessibility score
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
Document doesn't have a <title> element
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
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
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.
cabbi.bo 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
Missing source maps for large first-party JavaScript
cabbi.bo SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Document doesn't have a <title> element
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
N/A
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Cabbi.bo can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Cabbi.bo 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.
cabbi.bo
Open Graph data is detected on the main page of Cabbi. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: