Tools & Wizards About Us
certainly.io screenshot

Report Summary

  • 25

    Performance

    Renders faster than
    44% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

certainly.io

Welcome to Certainly | Your All-in-One AI Chatbot Solution

Page Load Speed

2.6 sec in total

First Response

183 ms

Resources Loaded

1.8 sec

Page Rendered

600 ms

certainly.io screenshot

About Website

Click here to check amazing Certainly content for Denmark. Otherwise, check out these important facts you probably never knew about certainly.io

Explore Certainly for versatile AI chatbot solutions across industries, enhancing customer engagement and streamlining operations.

Visit certainly.io

Key Findings

We analyzed Certainly.io page load time and found that the first response time was 183 ms and then it took 2.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

certainly.io performance score

25

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

45/100

10%

LCP (Largest Contentful Paint)

Value9.0 s

1/100

25%

SI (Speed Index)

Value5.9 s

48/100

10%

TBT (Total Blocking Time)

Value6,170 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value22.8 s

1/100

10%

Network Requests Diagram

certainly.io

183 ms

fonts.css

98 ms

certainly_popups.css

107 ms

polyfills-c67a75d1b6f99dc8.js

200 ms

webpack-e4439daf584fa4af.js

119 ms

Our browser made a total of 109 requests to load all elements on the main page. We found that 20% of them (22 requests) were addressed to the original Certainly.io, 26% (28 requests) were made to 25189408.fs1.hubspotusercontent-eu1.net and 25% (27 requests) were made to Img.plasmic.app. The less responsive or slowest element that took the longest time to load (1.5 sec) relates to the external source 25189408.fs1.hubspotusercontent-eu1.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 6.3 MB (35%)

Content Size

18.1 MB

After Optimization

11.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Certainly.io main page is 18.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. Only a small number of websites need less resources to load. Images take 16.1 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 1.3 MB

  • Original 1.6 MB
  • After minification 1.6 MB
  • After compression 311.2 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 1.3 MB or 80% of the original size.

Image Optimization

-31%

Potential reduce by 5.0 MB

  • Original 16.1 MB
  • After minification 11.1 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. Obviously, Certainly needs image optimization as it can save up to 5.0 MB or 31% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-16%

Potential reduce by 74.5 kB

  • Original 477.2 kB
  • After minification 477.2 kB
  • After compression 402.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 74.5 kB or 16% of the original size.

CSS Optimization

-34%

Potential reduce by 568 B

  • Original 1.7 kB
  • After minification 1.7 kB
  • After compression 1.1 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. Certainly.io needs all CSS files to be minified and compressed as it can save up to 568 B or 34% of the original size.

Requests Breakdown

Number of requests can be reduced by 34 (34%)

Requests Now

99

After Optimization

65

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 99 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Certainly. 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.

Network Requests Diagram

certainly.io

certainly.io

183 ms

fonts.css

fonts.css

98 ms

certainly_popups.css

certainly_popups.css

107 ms

polyfills-c67a75d1b6f99dc8.js

polyfills-c67a75d1b6f99dc8.js

200 ms

webpack-e4439daf584fa4af.js

webpack-e4439daf584fa4af.js

119 ms

framework-a0992c1421fb9c84.js

framework-a0992c1421fb9c84.js

223 ms

main-5108f608b760434e.js

main-5108f608b760434e.js

104 ms

_app-98e63706abf4b6fb.js

_app-98e63706abf4b6fb.js

386 ms

935-8adb2e3f62b872d5.js

935-8adb2e3f62b872d5.js

112 ms

%5B%5B...catchall%5D%5D-f1efcbcfd6374585.js

%5B%5B...catchall%5D%5D-f1efcbcfd6374585.js

219 ms

_buildManifest.js

_buildManifest.js

218 ms

_ssgManifest.js

_ssgManifest.js

218 ms

css2

css2

97 ms

FAQ%20v2.svg

FAQ%20v2.svg

556 ms

img

img

67 ms

Feastables-Carousel-logo.svg

Feastables-Carousel-logo.svg

604 ms

devices.svg

devices.svg

302 ms

integrate.svg

integrate.svg

305 ms

conversational-commerce.svg

conversational-commerce.svg

303 ms

img

img

163 ms

img

img

208 ms

img

img

300 ms

img

img

299 ms

img

img

307 ms

img

img

307 ms

img

img

473 ms

Matas-Carousel-logo.svg

Matas-Carousel-logo.svg

851 ms

Ganni-Carousel-logo.svg

Ganni-Carousel-logo.svg

926 ms

JosephJoseph-Carousel-logo.svg

JosephJoseph-Carousel-logo.svg

851 ms

RatandBoa-Carousel-logo.svg

RatandBoa-Carousel-logo.svg

848 ms

Carlsberg-Carousel-logo.svg

Carlsberg-Carousel-logo.svg

852 ms

LucyandYak-Carousel-logo.svg

LucyandYak-Carousel-logo.svg

847 ms

The-Fragrance-shop-Carousel-logo.svg

The-Fragrance-shop-Carousel-logo.svg

944 ms

Quad-lock-Carousel-logo.svg

Quad-lock-Carousel-logo.svg

979 ms

Sephora-Carousel-logo.svg

Sephora-Carousel-logo.svg

985 ms

Discovery-Carousel-logo.svg

Discovery-Carousel-logo.svg

980 ms

Bumpli-Carousel-logo.svg

Bumpli-Carousel-logo.svg

949 ms

Ticketmaster-Carousel-logo.svg

Ticketmaster-Carousel-logo.svg

977 ms

Magasin-Carousel-logo.svg

Magasin-Carousel-logo.svg

1053 ms

Liewood-Carousel-logo.svg

Liewood-Carousel-logo.svg

1069 ms

DW-Carousel-logo.svg

DW-Carousel-logo.svg

1089 ms

Sostrene%20Grene-Carousel-logo.svg

Sostrene%20Grene-Carousel-logo.svg

1083 ms

Rockwool-Carousel-logo.svg

Rockwool-Carousel-logo.svg

1076 ms

Culture-Kings-logo.svg

Culture-Kings-logo.svg

1104 ms

CCP-Carousel-logo.svg

CCP-Carousel-logo.svg

1143 ms

Interflora-Carousel-logo.svg

Interflora-Carousel-logo.svg

1180 ms

Trustpilot-Carousel-logo.svg

Trustpilot-Carousel-logo.svg

1175 ms

Boost%20Average%20Order%20visual.png

Boost%20Average%20Order%20visual.png

1295 ms

Deflect%2050%25%20of%20support%20tickets%20visual.png

Deflect%2050%25%20of%20support%20tickets%20visual.png

1353 ms

Collect%20valuable%20customer%20data%202.png

Collect%20valuable%20customer%20data%202.png

1481 ms

Drive%20customer%20activation%20.png

Drive%20customer%20activation%20.png

1464 ms

dfbe41ae5f6dadbfe88ac5322e8cfa8c.svg

dfbe41ae5f6dadbfe88ac5322e8cfa8c.svg

343 ms

img

img

326 ms

img

img

230 ms

img

img

360 ms

img

img

360 ms

img

img

327 ms

img

img

362 ms

img

img

366 ms

img

img

363 ms

img

img

365 ms

img

img

366 ms

img

img

367 ms

img

img

370 ms

img

img

431 ms

img

img

370 ms

img

img

377 ms

img

img

367 ms

img

img

426 ms

img

img

371 ms

img

img

373 ms

arrow-circle-prev.png

arrow-circle-prev.png

1174 ms

arrow-circle-next.png

arrow-circle-next.png

1189 ms

gtm.js

gtm.js

290 ms

25189408.js

25189408.js

794 ms

v2.js

v2.js

776 ms

webchat.js

webchat.js

930 ms

chat.js

chat.js

411 ms

certainly_popups_config.js

certainly_popups_config.js

892 ms

certainly_popups.js

certainly_popups.js

651 ms

GT-Walsheim-Medium.woff

GT-Walsheim-Medium.woff

72 ms

GT-Walsheim-Regular.woff

GT-Walsheim-Regular.woff

159 ms

GT-Walsheim-Light.woff

GT-Walsheim-Light.woff

69 ms

GT-Walsheim-Thin.woff

GT-Walsheim-Thin.woff

69 ms

GT-Walsheim-Ultra-Light.woff

GT-Walsheim-Ultra-Light.woff

158 ms

GT-Walsheim-Bold.woff

GT-Walsheim-Bold.woff

108 ms

GT-Walsheim-Black.woff

GT-Walsheim-Black.woff

156 ms

GT-Walsheim-Ultra-Bold.woff

GT-Walsheim-Ultra-Bold.woff

158 ms

0z9AI2qMkV4nGNgZkAGjAxoAAAAjgAF

0z9AI2qMkV4nGNgZkAGjAxoAAAAjgAF

3 ms

js

js

112 ms

analytics.js

analytics.js

108 ms

lftracker_v1_3P1w24dM5XGamY5n.js

lftracker_v1_3P1w24dM5XGamY5n.js

106 ms

destination

destination

267 ms

insight.min.js

insight.min.js

237 ms

hotjar-3886589.js

hotjar-3886589.js

275 ms

fbevents.js

fbevents.js

54 ms

492997072588496

492997072588496

182 ms

collect

collect

140 ms

collect

collect

110 ms

151 ms

modules.a4fd7e5489291affcf56.js

modules.a4fd7e5489291affcf56.js

146 ms

tr-rc.lfeeder.com

tr-rc.lfeeder.com

117 ms

collect

collect

49 ms

ga-audiences

ga-audiences

85 ms

fb.js

fb.js

452 ms

banner.js

banner.js

556 ms

collectedforms.js

collectedforms.js

488 ms

25189408.js

25189408.js

517 ms

27 ms

Accessibility Review

certainly.io accessibility score

81

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

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.

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 IDs are not unique

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

certainly.io 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

certainly.io SEO score

86

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

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 Certainly.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 Certainly.io 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

certainly.io

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