3.7 sec in total
442 ms
2.9 sec
279 ms
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.inWe 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.
factchecker.in performance score
name
value
score
weighting
Value5.3 s
7/100
10%
Value9.3 s
1/100
25%
Value11.8 s
4/100
10%
Value4,450 ms
0/100
30%
Value0.228
55/100
15%
Value19.1 s
3/100
10%
442 ms
1275 ms
111 ms
108 ms
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 size can be reduced by 281.1 kB (64%)
439.3 kB
158.2 kB
In fact, the total size of Factchecker.in main page is 439.3 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. Javascripts take 222.7 kB which makes up the majority of the site volume.
Potential reduce by 152.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.
Potential reduce by 6.1 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.
Potential reduce by 122.6 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 122.6 kB or 55% of the original size.
Number of requests can be reduced by 4 (33%)
12
8
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.
factchecker.in
442 ms
www.factchecker.in
1275 ms
js
111 ms
gtm.js
108 ms
adsbygoogle.js
48 ms
themespendinline.min.1b05d61e.css
235 ms
adsbyhocalwiretest.js
455 ms
cd-top-arrow.svg
383 ms
logo.png
424 ms
logo.png
598 ms
placeholder.jpg
647 ms
authorplaceholder.jpg
657 ms
patern-1.png
658 ms
sidekick-open.png
658 ms
hocalwirecommlightp1.min.38c2b3fd.js
792 ms
factchecker.in accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
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
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
List items (<li>) are not contained within <ul> or <ol> parent elements.
factchecker.in best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
factchecker.in SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
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.
factchecker.in
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: