Tools & Wizards About Us

Report Summary

  • 59

    Performance

    Renders faster than
    75% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 69% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 93

    SEO

    Google-friendlier than
    84% of websites

factual.com

Unlocking Powerful Consumer Connections with Location | FSQ

Page Load Speed

346 ms in total

First Response

25 ms

Resources Loaded

260 ms

Page Rendered

61 ms

About Website

Welcome to factual.com homepage info - get ready to check Factual best content for India right away, or after learning these important things about factual.com

Foursquare provides businesses with the opportunity to list on City Guide, & consumers can search for places they love.

Visit factual.com

Key Findings

We analyzed Factual.com page load time and found that the first response time was 25 ms and then it took 321 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

factual.com performance score

59

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.6 s

65/100

10%

LCP (Largest Contentful Paint)

Value6.8 s

7/100

25%

SI (Speed Index)

Value4.3 s

76/100

10%

TBT (Total Blocking Time)

Value320 ms

76/100

30%

CLS (Cumulative Layout Shift)

Value0.025

100/100

15%

TTI (Time to Interactive)

Value7.4 s

49/100

10%

Network Requests Diagram

foursquare.com

25 ms

gtm.js

140 ms

10 ms

27 ms

39 ms

Our browser made a total of 19 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Factual.com, 16% (3 requests) were made to Cdn.cookielaw.org and 5% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (140 ms) relates to the external source Googletagmanager.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 104.3 kB (12%)

Content Size

888.9 kB

After Optimization

784.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Factual.com main page is 888.9 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. 60% of websites need less resources to load. Images take 638.7 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 48.7 kB

  • Original 62.5 kB
  • After minification 61.3 kB
  • After compression 13.8 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 48.7 kB or 78% of the original size.

Image Optimization

-9%

Potential reduce by 54.9 kB

  • Original 638.7 kB
  • After minification 583.9 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. Factual images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 696 B

  • Original 174.0 kB
  • After minification 174.0 kB
  • After compression 173.3 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 55 B

  • Original 13.7 kB
  • After minification 13.7 kB
  • After compression 13.7 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. Factual.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 9 (64%)

Requests Now

14

After Optimization

5

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 14 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Factual. 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 4 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

Accessibility Review

factual.com accessibility score

88

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.

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

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

factual.com 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

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

factual.com SEO score

93

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

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