Tools & Wizards About Us

Report Summary

  • 10

    Performance

    Renders faster than
    23% of other websites

  • 92

    Accessibility

    Visual factors better than
    that of 78% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

factchecker.in

FactChecker.in is India's first dedicated Fact Check initiative.

Page Load Speed

3.7 sec in total

First Response

442 ms

Resources Loaded

2.9 sec

Page Rendered

279 ms

About Website

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

FactChecker.in is India's first dedicated Fact Check initiative.

Visit factchecker.in

Key Findings

We analyzed Factchecker.in page load time and found that the first response time was 442 ms and then it took 3.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

factchecker.in performance score

10

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.3 s

7/100

10%

LCP (Largest Contentful Paint)

Value9.3 s

1/100

25%

SI (Speed Index)

Value11.8 s

4/100

10%

TBT (Total Blocking Time)

Value4,450 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.228

55/100

15%

TTI (Time to Interactive)

Value19.1 s

3/100

10%

Network Requests Diagram

factchecker.in

442 ms

www.factchecker.in

1275 ms

js

111 ms

gtm.js

108 ms

adsbygoogle.js

48 ms

Our browser made a total of 15 requests to load all elements on the main page. We found that 80% of them (12 requests) were addressed to the original Factchecker.in, 13% (2 requests) were made to Googletagmanager.com and 7% (1 request) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Factchecker.in.

Page Optimization Overview & Recommendations

Page size can be reduced by 158.6 kB (50%)

Content Size

318.4 kB

After Optimization

159.8 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Factchecker.in main page is 318.4 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. Only 10% of websites need less resources to load. HTML takes 191.0 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 152.5 kB

  • Original 191.0 kB
  • After minification 188.9 kB
  • After compression 38.5 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 152.5 kB or 80% of the original size.

Image Optimization

-24%

Potential reduce by 6.1 kB

  • Original 25.6 kB
  • After minification 19.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. Obviously, Fact Checker needs image optimization as it can save up to 6.1 kB 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

-0%

Potential reduce by 63 B

  • Original 101.8 kB
  • After minification 101.8 kB
  • After compression 101.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.

Requests Breakdown

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

Requests Now

12

After Optimization

8

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

factchecker.in accessibility score

92

Accessibility Issues

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

Links do not have a discernible name

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

factchecker.in best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

factchecker.in SEO score

91

Search Engine Optimization Advices

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

High

Tap targets are not sized appropriately

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