Tools & Wizards About Us

Report Summary

  • 25

    Performance

    Renders faster than
    44% of other websites

  • 76

    Accessibility

    Visual factors better than
    that of 42% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

blog.verloop.io

Blog | Articles on Customer Support and Conversational AI - Verloop.io

Page Load Speed

2.3 sec in total

First Response

90 ms

Resources Loaded

1.7 sec

Page Rendered

552 ms

About Website

Click here to check amazing Blog Verloop content for India. Otherwise, check out these important facts you probably never knew about blog.verloop.io

The Verloop.io team shares insights, musings, tips and tricks and product launches around conversational AI and customer support automation.

Visit blog.verloop.io

Key Findings

We analyzed Blog.verloop.io page load time and found that the first response time was 90 ms and then it took 2.3 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

blog.verloop.io performance score

25

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.6 s

32/100

10%

LCP (Largest Contentful Paint)

Value9.8 s

0/100

25%

SI (Speed Index)

Value7.0 s

33/100

10%

TBT (Total Blocking Time)

Value1,600 ms

12/100

30%

CLS (Cumulative Layout Shift)

Value0.003

100/100

15%

TTI (Time to Interactive)

Value20.2 s

2/100

10%

Network Requests Diagram

blog.verloop.io

90 ms

392 ms

24c5k.css

37 ms

css2

60 ms

all.css

61 ms

Our browser made a total of 121 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Blog.verloop.io, 84% (102 requests) were made to Verloop.io and 3% (4 requests) were made to Code.jquery.com. The less responsive or slowest element that took the longest time to load (706 ms) relates to the external source Verloop.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 163.7 kB (12%)

Content Size

1.4 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Blog.verloop.io main page is 1.4 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. 65% of websites need less resources to load. Images take 869.5 kB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 151.1 kB

  • Original 172.4 kB
  • After minification 159.0 kB
  • After compression 21.3 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 151.1 kB or 88% of the original size.

Image Optimization

-1%

Potential reduce by 4.9 kB

  • Original 869.5 kB
  • After minification 864.6 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. Blog Verloop images are well optimized though.

JavaScript Optimization

-4%

Potential reduce by 5.3 kB

  • Original 129.5 kB
  • After minification 129.5 kB
  • After compression 124.3 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. This website has mostly compressed JavaScripts.

CSS Optimization

-1%

Potential reduce by 2.4 kB

  • Original 179.0 kB
  • After minification 179.0 kB
  • After compression 176.6 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. Blog.verloop.io has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 60 (52%)

Requests Now

115

After Optimization

55

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

blog.verloop.io 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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

High

Heading elements are not in a sequentially-descending order

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

blog.verloop.io best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

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

blog.verloop.io SEO score

79

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 Blog.verloop.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 Blog.verloop.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

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