Report Summary

  • 48

    Performance

    Renders faster than
    66% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 49% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

runo.in

Runo - Best Outbound Call Center CRM with auto dialer for Telecalling

Page Load Speed

1.2 sec in total

First Response

9 ms

Resources Loaded

805 ms

Page Rendered

400 ms

runo.in screenshot

About Website

Click here to check amazing Runo content for India. Otherwise, check out these important facts you probably never knew about runo.in

Runo Call Management App to manage calls at SIM level. Get Call Tracking for outbound sales calls with in built CRM. Try the best telecaller app for Free

Visit runo.in

Key Findings

We analyzed Runo.in page load time and found that the first response time was 9 ms and then it took 1.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.

Performance Metrics

runo.in performance score

48

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.4 s

97/100

10%

LCP (Largest Contentful Paint)

Value4.8 s

30/100

25%

SI (Speed Index)

Value3.1 s

93/100

10%

TBT (Total Blocking Time)

Value600 ms

50/100

30%

CLS (Cumulative Layout Shift)

Value0.472

18/100

15%

TTI (Time to Interactive)

Value8.4 s

38/100

10%

Network Requests Diagram

runo.in

9 ms

runo.in

19 ms

fonts.css

3 ms

bootstrap.min.css

5 ms

style.css

12 ms

Our browser made a total of 75 requests to load all elements on the main page. We found that 93% of them (70 requests) were addressed to the original Runo.in, 1% (1 request) were made to Popupsmart.com and 1% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (457 ms) relates to the external source Toolbox.marketingtools.apple.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 61.1 kB (9%)

Content Size

688.7 kB

After Optimization

627.7 kB

In fact, the total size of Runo.in main page is 688.7 kB. 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 543.2 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 32.2 kB

  • Original 38.4 kB
  • After minification 22.4 kB
  • After compression 6.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. This page needs HTML code to be minified as it can gain 16.0 kB, which is 42% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 32.2 kB or 84% of the original size.

Image Optimization

-5%

Potential reduce by 27.0 kB

  • Original 543.2 kB
  • After minification 516.2 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. Runo images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 62 B

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

CSS Optimization

-5%

Potential reduce by 1.8 kB

  • Original 35.4 kB
  • After minification 35.4 kB
  • After compression 33.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. Runo.in has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 21 (33%)

Requests Now

63

After Optimization

42

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

Accessibility Review

runo.in accessibility score

80

Accessibility Issues

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

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

Image elements do not have [alt] attributes

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

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

runo.in best practices score

83

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

SEO Factors

runo.in 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

Image elements do not have [alt] attributes

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 Runo.in 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 Runo.in 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 Runo. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: