Tools & Wizards About Us
broadly.com screenshot

Report Summary

  • 43

    Performance

    Renders faster than
    62% of other websites

  • 76

    Accessibility

    Visual factors better than
    that of 42% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

broadly.com

AI-Powered Customer Engagement and Review Management for Local Businesses - Broadly

Page Load Speed

3.5 sec in total

First Response

145 ms

Resources Loaded

2.4 sec

Page Rendered

895 ms

broadly.com screenshot

About Website

Click here to check amazing Broadly content for United States. Otherwise, check out these important facts you probably never knew about broadly.com

Boost your online reputation and attract more customers with Broadly's AI-powered platform. Our all-in-one solution helps local businesses manage reviews, engage with customers, and improve their...

Visit broadly.com

Key Findings

We analyzed Broadly.com page load time and found that the first response time was 145 ms and then it took 3.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

broadly.com performance score

43

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.9 s

87/100

10%

LCP (Largest Contentful Paint)

Value3.4 s

66/100

25%

SI (Speed Index)

Value7.8 s

23/100

10%

TBT (Total Blocking Time)

Value3,740 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value23.9 s

1/100

10%

Network Requests Diagram

broadly.com

145 ms

broadly.com

362 ms

jquery.min.js

489 ms

jquery-migrate.min.js

207 ms

main.js

217 ms

Our browser made a total of 69 requests to load all elements on the main page. We found that 77% of them (53 requests) were addressed to the original Broadly.com, 7% (5 requests) were made to Youtube.com and 3% (2 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Broadly.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 328.0 kB (29%)

Content Size

1.1 MB

After Optimization

790.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Broadly.com main page is 1.1 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 497.5 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 195.4 kB

  • Original 233.0 kB
  • After minification 217.1 kB
  • After compression 37.6 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 195.4 kB or 84% of the original size.

Image Optimization

-2%

Potential reduce by 11.6 kB

  • Original 497.5 kB
  • After minification 485.9 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. Broadly images are well optimized though.

JavaScript Optimization

-37%

Potential reduce by 121.0 kB

  • Original 327.7 kB
  • After minification 327.5 kB
  • After compression 206.7 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 121.0 kB or 37% of the original size.

CSS Optimization

-0%

Potential reduce by 0 B

  • Original 59.7 kB
  • After minification 59.7 kB
  • After compression 59.7 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. Broadly.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 18 (28%)

Requests Now

65

After Optimization

47

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

broadly.com

broadly.com

145 ms

broadly.com

broadly.com

362 ms

jquery.min.js

jquery.min.js

489 ms

jquery-migrate.min.js

jquery-migrate.min.js

207 ms

main.js

main.js

217 ms

fbevents.js

fbevents.js

33 ms

gidget.js

gidget.js

111 ms

Ve-lX9FGfxE

Ve-lX9FGfxE

213 ms

phone-icon.svg

phone-icon.svg

113 ms

yui3.min.js

yui3.min.js

432 ms

fl-slideshow.min.js

fl-slideshow.min.js

416 ms

21252-layout.js

21252-layout.js

429 ms

theme.min.js

theme.min.js

440 ms

389-layout-partial.js

389-layout-partial.js

428 ms

lazyload.min.js

lazyload.min.js

438 ms

gtm.js

gtm.js

75 ms

slick.min.js

slick.min.js

442 ms

www-player.css

www-player.css

7 ms

www-embed-player.js

www-embed-player.js

92 ms

base.js

base.js

121 ms

ad_status.js

ad_status.js

230 ms

RAiHx6Z8aI87xfn3BcPOACt6MzvCMtPfFa8gMAvLcEc.js

RAiHx6Z8aI87xfn3BcPOACt6MzvCMtPfFa8gMAvLcEc.js

160 ms

embed.js

embed.js

90 ms

logo.svg

logo.svg

254 ms

review-badges.png

review-badges.png

335 ms

auto-mechanic-hero.png

auto-mechanic-hero.png

334 ms

play-button-broadly.png

play-button-broadly.png

332 ms

Broadly-AI-WebChat.png

Broadly-AI-WebChat.png

357 ms

car.svg

car.svg

203 ms

home.svg

home.svg

375 ms

pet.svg

pet.svg

383 ms

LocalSEO-2.png

LocalSEO-2.png

488 ms

ListingCitations.png

ListingCitations.png

357 ms

ListingSync.png

ListingSync.png

376 ms

ReviewResponse.png

ReviewResponse.png

510 ms

AdvertisingIntelligence-2.png

AdvertisingIntelligence-2.png

519 ms

AIWebChat.png

AIWebChat.png

587 ms

SMSMessaging.png

SMSMessaging.png

614 ms

AppointmentScheduler.png

AppointmentScheduler.png

513 ms

Multi-Channel-Inbox1.png

Multi-Channel-Inbox1.png

715 ms

EmailTextCampaign.png

EmailTextCampaign.png

763 ms

ReviewRequest.png

ReviewRequest.png

596 ms

SocialMediaManager.png

SocialMediaManager.png

592 ms

shop-ware-png-img.png

shop-ware-png-img.png

820 ms

quickbook-png-img.png

quickbook-png-img.png

763 ms

gingr-png-img.png

gingr-png-img.png

673 ms

jobber-png-img.png

jobber-png-img.png

799 ms

shopmonkey-png-img.png

shopmonkey-png-img.png

858 ms

clio-png-img.png

clio-png-img.png

795 ms

booker-png-img.png

booker-png-img.png

867 ms

mitchell-png-img.png

mitchell-png-img.png

983 ms

napa-png-img.png

napa-png-img.png

870 ms

paw-png-img.png

paw-png-img.png

1041 ms

pet-png-img.png

pet-png-img.png

1022 ms

Arrow-Icon-left.png

Arrow-Icon-left.png

1036 ms

Arrow-Icon-right.png

Arrow-Icon-right.png

947 ms

Homepage-2-702x1024.webp

Homepage-2-702x1024.webp

1202 ms

2023BPTW_GeneralBadgeYear_FullColor-1.png

2023BPTW_GeneralBadgeYear_FullColor-1.png

1079 ms

fb.svg

fb.svg

1159 ms

KFOmCnqEu92Fr1Mu4mxM.woff

KFOmCnqEu92Fr1Mu4mxM.woff

47 ms

KFOlCnqEu92Fr1MmEU9fBBc-.woff

KFOlCnqEu92Fr1MmEU9fBBc-.woff

47 ms

id

id

27 ms

Create

Create

142 ms

tw.svg

tw.svg

1018 ms

ln.svg

ln.svg

901 ms

yt.svg

yt.svg

893 ms

inst.svg

inst.svg

931 ms

GenerateIT

GenerateIT

19 ms

aem.js

aem.js

50 ms

Accessibility Review

broadly.com accessibility score

76

Accessibility Issues

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

High

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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.

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

broadly.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

broadly.com SEO score

77

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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 Broadly.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 Broadly.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

broadly.com

Open Graph data is detected on the main page of Broadly. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: