1.3 sec in total
14 ms
568 ms
729 ms
Click here to check amazing Go Branch content for India. Otherwise, check out these important facts you probably never knew about go.branch.io
Get your users where you want them. Build seamless experiences and measure campaign ROI with Branch's deep linking and mobile attribution.
Visit go.branch.ioWe analyzed Go.branch.io page load time and found that the first response time was 14 ms and then it took 1.3 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.
go.branch.io performance score
name
value
score
weighting
Value4.1 s
22/100
10%
Value8.9 s
1/100
25%
Value5.2 s
59/100
10%
Value570 ms
52/100
30%
Value0.028
100/100
15%
Value9.8 s
28/100
10%
14 ms
35 ms
52 ms
14 ms
23 ms
Our browser made a total of 66 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Go.branch.io, 79% (52 requests) were made to Branch.io and 8% (5 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (232 ms) relates to the external source Branch.io.
Page size can be reduced by 294.2 kB (29%)
1.0 MB
732.9 kB
In fact, the total size of Go.branch.io 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. 60% of websites need less resources to load. Images take 565.1 kB which makes up the majority of the site volume.
Potential reduce by 170.3 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 82.1 kB, which is 42% 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 170.3 kB or 88% of the original size.
Potential reduce by 31.7 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. Go Branch images are well optimized though.
Potential reduce by 92.2 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 92.2 kB or 34% of the original size.
Number of requests can be reduced by 17 (29%)
59
42
The browser has sent 59 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Go Branch. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 10 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
go.branch.io
14 ms
branch.io
35 ms
css
52 ms
design_system.css
14 ms
localized.css
23 ms
marketo-form.css
29 ms
font-awesome.min.css
52 ms
all.js
40 ms
v4.js
56 ms
topbar.css
32 ms
forms2.min.js
168 ms
marketo-prefill.js
31 ms
home.css
41 ms
date.js
40 ms
hp.js
36 ms
resource.js
40 ms
css
49 ms
gtm.js
199 ms
logo-white.svg
35 ms
close-x.svg
38 ms
MLP.svg
40 ms
MMP.svg
42 ms
nav_journeys.svg
40 ms
nav_universal-ads.svg
43 ms
nav_universal-email.svg
44 ms
nav-seo-search.svg
56 ms
nav_nativelink.svg
52 ms
nav_QR.svg
57 ms
nav_data-feeds.svg
54 ms
nav_SKAN.svg
58 ms
nav_OTT.svg
59 ms
nav_attribution.svg
66 ms
nav_persona-graph.svg
73 ms
nav_resource-help-center.svg
66 ms
nav_resource-branch-university.svg
68 ms
nav_resource-docs.svg
70 ms
nav_resource-library.svg
64 ms
nav_case-studies.svg
158 ms
nav_webinars.svg
151 ms
nav_white-papers.svg
158 ms
nav_blog.svg
153 ms
nav_podcast.svg
162 ms
globe.svg
161 ms
search.svg
165 ms
Hero-video.png
232 ms
play-button.svg
226 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf
145 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf
157 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf
219 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf
219 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf
223 ms
home-lg.css
89 ms
logo-dark.svg
82 ms
orange-arrow-right.svg
51 ms
warner_bros_discovery.png
51 ms
daniel_joseph.png
47 ms
credit_karma.png
46 ms
andrew_touchstone.png
45 ms
audacy.png
45 ms
jon-pacino.png
52 ms
philips.png
49 ms
gianna.jpg
48 ms
shutterfly.png
50 ms
razan.png
51 ms
branch-latest.min.js
31 ms
otSDKStub.js
60 ms
go.branch.io 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
Buttons do not have an accessible 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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
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.
go.branch.io 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
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
go.branch.io SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
robots.txt is not valid
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
N/A
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Go.branch.io 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 Go.branch.io 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.
go.branch.io
Open Graph data is detected on the main page of Go Branch. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: