Tools & Wizards About Us
dooly.ai screenshot

Report Summary

  • 32

    Performance

    Renders faster than
    52% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 57% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 93

    SEO

    Google-friendlier than
    84% of websites

dooly.ai

Dooly: Win more deals, together

Page Load Speed

5.1 sec in total

First Response

395 ms

Resources Loaded

2.4 sec

Page Rendered

2.3 sec

dooly.ai screenshot

About Website

Click here to check amazing Dooly content for United States. Otherwise, check out these important facts you probably never knew about dooly.ai

Dooly helps revenue teams win more deals by improving CRM hygiene, running a winning sales process, and eliminating low value work.

Visit dooly.ai

Key Findings

We analyzed Dooly.ai page load time and found that the first response time was 395 ms and then it took 4.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

dooly.ai performance score

32

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

27/100

10%

LCP (Largest Contentful Paint)

Value4.2 s

45/100

25%

SI (Speed Index)

Value7.4 s

27/100

10%

TBT (Total Blocking Time)

Value4,610 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.028

100/100

15%

TTI (Time to Interactive)

Value15.7 s

6/100

10%

Network Requests Diagram

dooly.ai

395 ms

www.dooly.ai

577 ms

header.css

55 ms

bsnav.min.css

217 ms

font-awesome.min.css

210 ms

Our browser made a total of 99 requests to load all elements on the main page. We found that 82% of them (81 requests) were addressed to the original Dooly.ai, 3% (3 requests) were made to Unpkg.com and 2% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (650 ms) relates to the external source Cdn.segment.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 403.7 kB (14%)

Content Size

2.8 MB

After Optimization

2.4 MB

  • HTML
  • Images

In fact, the total size of Dooly.ai main page is 2.8 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. 75% 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 2.4 MB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 403.7 kB

  • Original 461.8 kB
  • After minification 455.6 kB
  • After compression 58.1 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 403.7 kB or 87% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 2.4 MB
  • After minification 2.4 MB

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. Dooly images are well optimized though.

Requests Breakdown

Number of requests can be reduced by 39 (45%)

Requests Now

87

After Optimization

48

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

dooly.ai

dooly.ai

395 ms

www.dooly.ai

www.dooly.ai

577 ms

header.css

header.css

55 ms

bsnav.min.css

bsnav.min.css

217 ms

font-awesome.min.css

font-awesome.min.css

210 ms

elementor-icons.min.css

elementor-icons.min.css

41 ms

frontend-lite.min.css

frontend-lite.min.css

129 ms

swiper.min.css

swiper.min.css

66 ms

frontend-lite.min.css

frontend-lite.min.css

74 ms

jquery.min.js

jquery.min.js

83 ms

isotope.pkgd.min.js

isotope.pkgd.min.js

31 ms

css2

css2

33 ms

isotope.pkgd.min.js

isotope.pkgd.min.js

13 ms

isotope.pkgd.min.js

isotope.pkgd.min.js

18 ms

lazysizes.min.js

lazysizes.min.js

40 ms

bootstrap.min.js

bootstrap.min.js

55 ms

custom.js

custom.js

56 ms

E-v1.js

E-v1.js

27 ms

dooly-forms.js

dooly-forms.js

63 ms

bsnav-v2.min.js

bsnav-v2.min.js

80 ms

lazyload.min.js

lazyload.min.js

89 ms

pminstantpage.min.js

pminstantpage.min.js

88 ms

webpack-pro.runtime.min.js

webpack-pro.runtime.min.js

90 ms

webpack.runtime.min.js

webpack.runtime.min.js

106 ms

frontend-modules.min.js

frontend-modules.min.js

111 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

119 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

122 ms

wp-polyfill.min.js

wp-polyfill.min.js

142 ms

hooks.min.js

hooks.min.js

137 ms

i18n.min.js

i18n.min.js

338 ms

frontend.min.js

frontend.min.js

358 ms

waypoints.min.js

waypoints.min.js

338 ms

core.min.js

core.min.js

339 ms

frontend.min.js

frontend.min.js

341 ms

elements-handlers.min.js

elements-handlers.min.js

341 ms

gtm.js

gtm.js

254 ms

analytics.min.js

analytics.min.js

650 ms

arrow__light.svg

arrow__light.svg

145 ms

menu__arrow.svg

menu__arrow.svg

157 ms

Pattern-Background-01.svg

Pattern-Background-01.svg

143 ms

Background-Pattern-01-Half-Bottom-Right.svg

Background-Pattern-01-Half-Bottom-Right.svg

140 ms

Background-Pattern-01-Half-Bottom-Left.svg

Background-Pattern-01-Half-Bottom-Left.svg

159 ms

Calibre-Bold.woff

Calibre-Bold.woff

375 ms

Calibre-Black.woff

Calibre-Black.woff

191 ms

Calibre-SemiBold.woff

Calibre-SemiBold.woff

374 ms

Calibre-Medium.woff

Calibre-Medium.woff

116 ms

Calibre.woff

Calibre.woff

118 ms

Calibre-Light.woff

Calibre-Light.woff

186 ms

Calibre-Thin.woff

Calibre-Thin.woff

373 ms

2059.js

2059.js

105 ms

dooly.svg

dooly.svg

117 ms

logo-white.svg

logo-white.svg

119 ms

dooly_logo_white.svg

dooly_logo_white.svg

168 ms

scarlett-thumbnail.png

scarlett-thumbnail.png

165 ms

DealSpace-Main-View-1.png

DealSpace-Main-View-1.png

374 ms

Notes-In-Meeting-Capture-1024x932.png

Notes-In-Meeting-Capture-1024x932.png

371 ms

Pipeline-Deal-Stage-Field-Update-1024x810.png

Pipeline-Deal-Stage-Field-Update-1024x810.png

373 ms

logo-Figma-white.svg

logo-Figma-white.svg

403 ms

logo-Procore-white.svg

logo-Procore-white.svg

400 ms

logo-Intercom-white.svg

logo-Intercom-white.svg

401 ms

logo-BigCommerce-white.svg

logo-BigCommerce-white.svg

397 ms

logo-Formstack-white.svg

logo-Formstack-white.svg

402 ms

logo-Ramp-white.svg

logo-Ramp-white.svg

398 ms

logo-LinkSquares-white.svg

logo-LinkSquares-white.svg

434 ms

logo-Writer-white.svg

logo-Writer-white.svg

418 ms

logo-Juro-white.svg

logo-Juro-white.svg

427 ms

logo-CrowdRiff-white.svg

logo-CrowdRiff-white.svg

428 ms

logo-CrowdRiff-lightpink.svg

logo-CrowdRiff-lightpink.svg

426 ms

customer-courtney-malinas.png

customer-courtney-malinas.png

425 ms

Too-Many-Tabs.png

Too-Many-Tabs.png

475 ms

Too-Many-Tabs-Mobile-1024x376.png

Too-Many-Tabs-Mobile-1024x376.png

477 ms

Sales-Process-Chaos.png

Sales-Process-Chaos.png

461 ms

Dooly-in-the-App-Bar.png

Dooly-in-the-App-Bar.png

478 ms

Dooly-in-the-App-Bar-Mobile-1024x187.png

Dooly-in-the-App-Bar-Mobile-1024x187.png

474 ms

Dooly-Arrow-Pink.svg

Dooly-Arrow-Pink.svg

481 ms

icon-google-chrome.svg

icon-google-chrome.svg

579 ms

icon-google-calendar.svg

icon-google-calendar.svg

554 ms

icon-outreach.svg

icon-outreach.svg

601 ms

icon-slack.svg

icon-slack.svg

499 ms

icon-gong.svg

icon-gong.svg

506 ms

js

js

93 ms

tags.js

tags.js

231 ms

insight.min.js

insight.min.js

340 ms

fbevents.js

fbevents.js

221 ms

a000ae7b1aca4ca2a4aa59e9ea327c1f.js.ubembed.com

a000ae7b1aca4ca2a4aa59e9ea327c1f.js.ubembed.com

214 ms

icon-linkedin.svg

icon-linkedin.svg

521 ms

DealSpace-Main-View-1-1024x706.png

DealSpace-Main-View-1-1024x706.png

495 ms

logo-Figma-lightpink.svg

logo-Figma-lightpink.svg

474 ms

customer-kyle-parrish.png

customer-kyle-parrish.png

454 ms

Dooly-Illustration-Sales-Teams-1024x1024.png

Dooly-Illustration-Sales-Teams-1024x1024.png

469 ms

Dooly-Illustration-CS-Teams-1024x1024.png

Dooly-Illustration-CS-Teams-1024x1024.png

480 ms

Dooly-Illustration-Ops-Enablement-Teams-1024x1024.png

Dooly-Illustration-Ops-Enablement-Teams-1024x1024.png

360 ms

logo-ThoughtExchange-lightpink.svg

logo-ThoughtExchange-lightpink.svg

354 ms

customer-michaela-becker.png

customer-michaela-becker.png

361 ms

destinations.min.js

destinations.min.js

186 ms

tracking.min.js

tracking.min.js

142 ms

insight.beta.min.js

insight.beta.min.js

24 ms

insight_tag_errors.gif

insight_tag_errors.gif

106 ms

p

p

155 ms

Accessibility Review

dooly.ai accessibility score

84

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

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

dooly.ai best practices score

92

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

Page has valid source maps

SEO Factors

dooly.ai SEO score

93

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

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

Social Sharing Optimization

dooly.ai

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