Tools & Wizards About Us
certainly.io screenshot

Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% 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

6.2 sec in total

First Response

923 ms

Resources Loaded

4.6 sec

Page Rendered

697 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 923 ms and then it took 5.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

certainly.io performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

19/100

10%

LCP (Largest Contentful Paint)

Value9.6 s

0/100

25%

SI (Speed Index)

Value7.6 s

26/100

10%

TBT (Total Blocking Time)

Value5,470 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.064

97/100

15%

TTI (Time to Interactive)

Value22.1 s

1/100

10%

Network Requests Diagram

certainly.io

923 ms

fonts.css

378 ms

certainly_popups.css

347 ms

polyfills-c67a75d1b6f99dc8.js

506 ms

webpack-e4439daf584fa4af.js

451 ms

Our browser made a total of 87 requests to load all elements on the main page. We found that 25% of them (22 requests) were addressed to the original Certainly.io, 38% (33 requests) were made to Img.plasmic.app and 15% (13 requests) were made to Site-assets.plasmic.app. The less responsive or slowest element that took the longest time to load (3.7 sec) relates to the external source Img.plasmic.app.

Page Optimization Overview & Recommendations

Page size can be reduced by 7.6 MB (27%)

Content Size

28.1 MB

After Optimization

20.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Certainly.io main page is 28.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. 55% of websites need less resources to load. Images take 26.0 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 1.4 MB

  • Original 1.7 MB
  • After minification 1.7 MB
  • After compression 337.8 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.4 MB or 80% of the original size.

Image Optimization

-24%

Potential reduce by 6.2 MB

  • Original 26.0 MB
  • After minification 19.8 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 6.2 MB or 24% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-17%

Potential reduce by 77.0 kB

  • Original 456.4 kB
  • After minification 456.4 kB
  • After compression 379.4 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 77.0 kB or 17% 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 19 (25%)

Requests Now

77

After Optimization

58

  • Images
  • JavaScript
  • CSS

The browser has sent 77 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 20 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

certainly.io

certainly.io

923 ms

fonts.css

fonts.css

378 ms

certainly_popups.css

certainly_popups.css

347 ms

polyfills-c67a75d1b6f99dc8.js

polyfills-c67a75d1b6f99dc8.js

506 ms

webpack-e4439daf584fa4af.js

webpack-e4439daf584fa4af.js

451 ms

framework-a0992c1421fb9c84.js

framework-a0992c1421fb9c84.js

583 ms

main-5108f608b760434e.js

main-5108f608b760434e.js

497 ms

_app-7b644fe3a6ab9623.js

_app-7b644fe3a6ab9623.js

800 ms

935-8adb2e3f62b872d5.js

935-8adb2e3f62b872d5.js

509 ms

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

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

616 ms

_buildManifest.js

_buildManifest.js

616 ms

_ssgManifest.js

_ssgManifest.js

616 ms

css2

css2

36 ms

UseCases_Navbar.svg

UseCases_Navbar.svg

609 ms

devices.svg

devices.svg

486 ms

integrate.svg

integrate.svg

495 ms

conversational-commerce.svg

conversational-commerce.svg

504 ms

shopify_icon_outline.svg

shopify_icon_outline.svg

803 ms

app_ecom.svg

app_ecom.svg

753 ms

img

img

678 ms

a7ac10518f57509fd6c570b65183e213.svg

a7ac10518f57509fd6c570b65183e213.svg

66 ms

d5676ff12e01eb61ed1efb63075bb8b7.svg

d5676ff12e01eb61ed1efb63075bb8b7.svg

52 ms

8b54406af11bd1ae494d87b1ff5ec59b.svg

8b54406af11bd1ae494d87b1ff5ec59b.svg

58 ms

96ac0393fa7191b710db94ddc89418d9.svg

96ac0393fa7191b710db94ddc89418d9.svg

60 ms

5fedc72252de62c08bbe661215192361.svg

5fedc72252de62c08bbe661215192361.svg

60 ms

c2c678f2035b48d208abb0524fdb61de.svg

c2c678f2035b48d208abb0524fdb61de.svg

59 ms

5d3f761b88faf4314c2886db7d281575.svg

5d3f761b88faf4314c2886db7d281575.svg

63 ms

345a48bb9fcf292b4c2041e13405b6c1.svg

345a48bb9fcf292b4c2041e13405b6c1.svg

362 ms

9b19e8d2b33690fa24ce7da27df14205.svg

9b19e8d2b33690fa24ce7da27df14205.svg

63 ms

be98351f6e3eb752399b76fac80671a0.svg

be98351f6e3eb752399b76fac80671a0.svg

61 ms

c83719bcb36630914df82d62c10588a4.svg

c83719bcb36630914df82d62c10588a4.svg

67 ms

9d29c1ea3cb1c113f6510284ad89c962.svg

9d29c1ea3cb1c113f6510284ad89c962.svg

68 ms

c44067d760704c4d677ba5ddc3064d12.svg

c44067d760704c4d677ba5ddc3064d12.svg

69 ms

img

img

1281 ms

img

img

1309 ms

img

img

1439 ms

img

img

1532 ms

img

img

1372 ms

img

img

1772 ms

img

img

1746 ms

img

img

1871 ms

img

img

1946 ms

img

img

2001 ms

img

img

2103 ms

img

img

2321 ms

img

img

2200 ms

img

img

2392 ms

img

img

2577 ms

img

img

3030 ms

img

img

2686 ms

img

img

2774 ms

img

img

2934 ms

img

img

2624 ms

img

img

3120 ms

img

img

3141 ms

img

img

3153 ms

img

img

3001 ms

img

img

2939 ms

img

img

3739 ms

img

img

3239 ms

img

img

3562 ms

img

img

3287 ms

img

img

3658 ms

img

img

3498 ms

img

img

3723 ms

arrow-circle-prev.png

arrow-circle-prev.png

476 ms

arrow-circle-next.png

arrow-circle-next.png

509 ms

GT-Walsheim-Regular.woff

GT-Walsheim-Regular.woff

326 ms

GT-Walsheim-Medium.woff

GT-Walsheim-Medium.woff

327 ms

GT-Walsheim-Light.woff

GT-Walsheim-Light.woff

297 ms

GT-Walsheim-Thin.woff

GT-Walsheim-Thin.woff

307 ms

GT-Walsheim-Ultra-Light.woff

GT-Walsheim-Ultra-Light.woff

325 ms

GT-Walsheim-Bold.woff

GT-Walsheim-Bold.woff

380 ms

GT-Walsheim-Black.woff

GT-Walsheim-Black.woff

390 ms

GT-Walsheim-Ultra-Bold.woff

GT-Walsheim-Ultra-Bold.woff

410 ms

0z9AI2qMkV4nGNgZkAGjAxoAAAAjgAF

0z9AI2qMkV4nGNgZkAGjAxoAAAAjgAF

1 ms

gtm.js

gtm.js

79 ms

25189408.js

25189408.js

444 ms

v2.js

v2.js

625 ms

webchat.js

webchat.js

330 ms

chat.js

chat.js

330 ms

certainly_popups_config.js

certainly_popups_config.js

2334 ms

certainly_popups.js

certainly_popups.js

393 ms

collectedforms.js

collectedforms.js

474 ms

banner.js

banner.js

464 ms

fb.js

fb.js

440 ms

25189408.js

25189408.js

492 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

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

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: