Tools & Wizards About Us
api.blowhorn.com screenshot

Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

api.blowhorn.com

Blowhorn | Same day delivery partner for your business

Page Load Speed

1.9 sec in total

First Response

384 ms

Resources Loaded

1.5 sec

Page Rendered

71 ms

api.blowhorn.com screenshot

About Website

Visit api.blowhorn.com now to see the best up-to-date Api Blowhorn content for India and also check out these interesting facts you probably never knew about api.blowhorn.com

Grow your brand on Blowhorn’s same day delivery network with our full-stack fulfillment model. Partner with the leading eCommerce fulfillment Company in India

Visit api.blowhorn.com

Key Findings

We analyzed Api.blowhorn.com page load time and found that the first response time was 384 ms and then it took 1.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.

Performance Metrics

api.blowhorn.com performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.0 s

4/100

10%

LCP (Largest Contentful Paint)

Value13.5 s

0/100

25%

SI (Speed Index)

Value12.7 s

3/100

10%

TBT (Total Blocking Time)

Value4,610 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value26.6 s

0/100

10%

Network Requests Diagram

api.blowhorn.com

384 ms

api.blowhorn.com

762 ms

99 ms

d727ed7.js

74 ms

4500bff.js

90 ms

Our browser made a total of 7 requests to load all elements on the main page. We found that 29% of them (2 requests) were addressed to the original Api.blowhorn.com, 71% (5 requests) were made to Blowhorn.com. The less responsive or slowest element that took the longest time to load (762 ms) belongs to the original domain Api.blowhorn.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 5.7 kB (75%)

Content Size

7.6 kB

After Optimization

1.9 kB

  • HTML

In fact, the total size of Api.blowhorn.com main page is 7.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. Only 5% of websites need less resources to load. HTML takes 7.6 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 5.7 kB

  • Original 7.6 kB
  • After minification 7.5 kB
  • After compression 1.9 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 5.7 kB or 75% of the original size.

Requests Breakdown

Number of requests can be reduced by 3 (75%)

Requests Now

4

After Optimization

1

  • JavaScript

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

Network Requests Diagram

api.blowhorn.com

api.blowhorn.com

384 ms

api.blowhorn.com

api.blowhorn.com

762 ms

99 ms

d727ed7.js

d727ed7.js

74 ms

4500bff.js

4500bff.js

90 ms

97c2188.js

97c2188.js

223 ms

a88084c.js

a88084c.js

93 ms

Accessibility Review

api.blowhorn.com accessibility score

84

Accessibility Issues

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

High

[aria-*] attributes do not match their roles

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

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

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

api.blowhorn.com 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

api.blowhorn.com SEO score

92

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

api.blowhorn.com

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