Report Summary

  • 24

    Performance

    Renders faster than
    43% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 83% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

metafact.io

Fact-checking platform powered by science - Metafact

Page Load Speed

1.5 sec in total

First Response

369 ms

Resources Loaded

1.1 sec

Page Rendered

57 ms

metafact.io screenshot

About Website

Click here to check amazing Metafact content. Otherwise, check out these important facts you probably never knew about metafact.io

Metafact is a place to verify knowledge via the world’s top experts. It’s a platform to ask questions, learn the facts and share the truth.

Visit metafact.io

Key Findings

We analyzed Metafact.io page load time and found that the first response time was 369 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

metafact.io performance score

24

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.7 s

13/100

10%

LCP (Largest Contentful Paint)

Value11.7 s

0/100

25%

SI (Speed Index)

Value6.7 s

36/100

10%

TBT (Total Blocking Time)

Value2,060 ms

7/100

30%

CLS (Cumulative Layout Shift)

Value0.006

100/100

15%

TTI (Time to Interactive)

Value11.5 s

18/100

10%

Network Requests Diagram

metafact.io

369 ms

fbevents.js

44 ms

js

99 ms

raven.min.js

80 ms

5ac6371497b63ac789e73f565631fae2dd2c9bf9.js

100 ms

Our browser made a total of 14 requests to load all elements on the main page. We found that 36% of them (5 requests) were addressed to the original Metafact.io, 14% (2 requests) were made to My.hellobar.com and 7% (1 request) were made to Connect.facebook.net. The less responsive or slowest element that took the longest time to load (503 ms) belongs to the original domain Metafact.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 5 B (0%)

Content Size

95.2 kB

After Optimization

95.2 kB

In fact, the total size of Metafact.io main page is 95.2 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. 35% of websites need less resources to load. Javascripts take 89.4 kB which makes up the majority of the site volume.

HTML Optimization

-0%

Potential reduce by -8 B

  • Original 0 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. This web page is already compressed.

JavaScript Optimization

-0%

Potential reduce by 10 B

  • Original 89.4 kB
  • After minification 89.4 kB
  • After compression 89.4 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

-0%

Potential reduce by 3 B

  • Original 5.8 kB
  • After minification 5.8 kB
  • After compression 5.8 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. Metafact.io has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 8 (67%)

Requests Now

12

After Optimization

4

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

Accessibility Review

metafact.io accessibility score

94

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

ARIA progressbar elements do not have accessible names.

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

metafact.io best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

metafact.io SEO score

100

Search Engine Optimization Advices

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Metafact.io can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Metafact.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 description is not detected on the main page of Metafact. 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: