Tools & Wizards About Us
voco.in screenshot

Report Summary

  • 93

    Performance

    Renders faster than
    92% of other websites

  • 58

    Accessibility

    Visual factors better than
    that of 25% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

voco.in

Voco.in

Page Load Speed

476 ms in total

First Response

173 ms

Resources Loaded

203 ms

Page Rendered

100 ms

voco.in screenshot

About Website

Visit voco.in now to see the best up-to-date Voco content for India and also check out these interesting facts you probably never knew about voco.in

Visit voco.in

Key Findings

We analyzed Voco.in page load time and found that the first response time was 173 ms and then it took 303 ms to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.

Performance Metrics

voco.in performance score

93

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.4 s

70/100

10%

LCP (Largest Contentful Paint)

Value2.4 s

91/100

25%

SI (Speed Index)

Value3.7 s

86/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.032

100/100

15%

TTI (Time to Interactive)

Value2.4 s

98/100

10%

Network Requests Diagram

voco.in

173 ms

analytics.js

7 ms

Our browser made a total of 2 requests to load all elements on the main page. We found that 50% of them (1 request) were addressed to the original Voco.in, 50% (1 request) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (173 ms) belongs to the original domain Voco.in.

Page Optimization Overview & Recommendations

Page size can be reduced by 32.5 kB (60%)

Content Size

54.2 kB

After Optimization

21.7 kB

  • HTML
  • JavaScript

In fact, the total size of Voco.in main page is 54.2 kB. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only 5% of websites need less resources to load. Javascripts take 52.9 kB which makes up the majority of the site volume.

HTML Optimization

-41%

Potential reduce by 516 B

  • Original 1.3 kB
  • After minification 1.3 kB
  • After compression 746 B

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 516 B or 41% of the original size.

JavaScript Optimization

-60%

Potential reduce by 32.0 kB

  • Original 52.9 kB
  • After minification 52.9 kB
  • After compression 20.9 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 32.0 kB or 60% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

1

After Optimization

1

  • JavaScript

The browser has sent 1 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Voco. According to our analytics all requests are already optimized.

Network Requests Diagram

voco.in

voco.in

173 ms

analytics.js

analytics.js

7 ms

Accessibility Review

voco.in accessibility score

58

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.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

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

SEO Factors

voco.in SEO score

83

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

robots.txt is not valid

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

    N/A

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Voco.in can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Voco.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

voco.in

Open Graph description is not detected on the main page of Voco. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: