Report Summary

  • 37

    Performance

    Renders faster than
    57% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 85

    SEO

    Google-friendlier than
    56% of websites

fastsearch.com

Microsoft SharePoint Online - Collaboration Software | Microsoft 365

Page Load Speed

3.5 sec in total

First Response

118 ms

Resources Loaded

3.2 sec

Page Rendered

234 ms

fastsearch.com screenshot

About Website

Welcome to fastsearch.com homepage info - get ready to check Fastsearch best content right away, or after learning these important things about fastsearch.com

Share, organize, and discover information with Microsoft SharePoint. Learn about SharePoint Online, OneDrive for Business, and Apps for SharePoint.

Visit fastsearch.com

Key Findings

We analyzed Fastsearch.com page load time and found that the first response time was 118 ms and then it took 3.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

fastsearch.com performance score

37

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value11.4 s

0/100

10%

LCP (Largest Contentful Paint)

Value15.1 s

0/100

25%

SI (Speed Index)

Value14.1 s

1/100

10%

TBT (Total Blocking Time)

Value340 ms

74/100

30%

CLS (Cumulative Layout Shift)

Value0.004

100/100

15%

TTI (Time to Interactive)

Value21.5 s

1/100

10%

Network Requests Diagram

fastsearch.com

118 ms

sharepoint

158 ms

sharepoint.microsoft.com

157 ms

sharepoint

154 ms

sharepoint

214 ms

Our browser made a total of 105 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Fastsearch.com, 36% (38 requests) were made to C.s-microsoft.com and 10% (10 requests) were made to Facebook.com. The less responsive or slowest element that took the longest time to load (516 ms) relates to the external source C.s-microsoft.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 858.1 kB (59%)

Content Size

1.5 MB

After Optimization

597.2 kB

In fact, the total size of Fastsearch.com main page is 1.5 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 40% of websites need less resources to load. Javascripts take 535.6 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 109.8 kB

  • Original 134.9 kB
  • After minification 134.5 kB
  • After compression 25.1 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 109.8 kB or 81% of the original size.

Image Optimization

-6%

Potential reduce by 16.9 kB

  • Original 279.2 kB
  • After minification 262.3 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. Fastsearch images are well optimized though.

JavaScript Optimization

-61%

Potential reduce by 324.3 kB

  • Original 535.6 kB
  • After minification 518.6 kB
  • After compression 211.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 324.3 kB or 61% of the original size.

CSS Optimization

-81%

Potential reduce by 407.2 kB

  • Original 505.7 kB
  • After minification 369.5 kB
  • After compression 98.5 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. Fastsearch.com needs all CSS files to be minified and compressed as it can save up to 407.2 kB or 81% of the original size.

Requests Breakdown

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

Requests Now

95

After Optimization

34

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

Accessibility Review

fastsearch.com accessibility score

98

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Some elements have a [tabindex] value greater than 0

Best Practices

fastsearch.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

High

Missing source maps for large first-party JavaScript

SEO Factors

fastsearch.com SEO score

85

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

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 Fastsearch.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 Fastsearch.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 description is not detected on the main page of Fastsearch. 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: