Tools & Wizards About Us
freshstatus.io screenshot

Report Summary

  • 29

    Performance

    Renders faster than
    49% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

freshstatus.io

Status page Powered by Freshstatus

Page Load Speed

742 ms in total

First Response

8 ms

Resources Loaded

379 ms

Page Rendered

355 ms

freshstatus.io screenshot

About Website

Visit freshstatus.io now to see the best up-to-date Freshstatus content for India and also check out these interesting facts you probably never knew about freshstatus.io

Status page Powered by Freshstatus

Visit freshstatus.io

Key Findings

We analyzed Freshstatus.io page load time and found that the first response time was 8 ms and then it took 734 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

freshstatus.io performance score

29

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

57/100

10%

LCP (Largest Contentful Paint)

Value4.7 s

32/100

25%

SI (Speed Index)

Value11.9 s

4/100

10%

TBT (Total Blocking Time)

Value5,860 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value28.5 s

0/100

10%

Network Requests Diagram

statuspage

8 ms

5 ms

58 ms

polyfills-c67a75d1b6f99dc8.js

57 ms

webpack-915604806c02f8ff.js

84 ms

Our browser made a total of 28 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Freshstatus.io, 11% (3 requests) were made to Dam.freshworks.com and 4% (1 request) were made to Cdn-ukwest.onetrust.com. The less responsive or slowest element that took the longest time to load (174 ms) relates to the external source Freshworks.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 264.9 kB (57%)

Content Size

463.2 kB

After Optimization

198.3 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Freshstatus.io main page is 463.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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. HTML takes 308.7 kB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 264.9 kB

  • Original 308.7 kB
  • After minification 308.7 kB
  • After compression 43.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 264.9 kB or 86% of the original size.

Image Optimization

-5%

Potential reduce by 39 B

  • Original 718 B
  • After minification 679 B

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. Freshstatus images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 33 B

  • Original 153.8 kB
  • After minification 153.8 kB
  • After compression 153.8 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 15 (79%)

Requests Now

19

After Optimization

4

  • Images
  • JavaScript

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

Network Requests Diagram

statuspage

statuspage

8 ms

5 ms

58 ms

polyfills-c67a75d1b6f99dc8.js

polyfills-c67a75d1b6f99dc8.js

57 ms

webpack-915604806c02f8ff.js

webpack-915604806c02f8ff.js

84 ms

framework-7751730b10fa0f74.js

framework-7751730b10fa0f74.js

82 ms

main-220db4dea5af5d87.js

main-220db4dea5af5d87.js

80 ms

_app-97d61a5096e153df.js

_app-97d61a5096e153df.js

82 ms

fec483df-c8cf40203e53dd6e.js

fec483df-c8cf40203e53dd6e.js

128 ms

698-1e6eb040020c97b7.js

698-1e6eb040020c97b7.js

128 ms

694-5ffacf7d29b1ab05.js

694-5ffacf7d29b1ab05.js

137 ms

924-d33691dbdef065b8.js

924-d33691dbdef065b8.js

150 ms

210-aa829cacc62978db.js

210-aa829cacc62978db.js

140 ms

%5B%5B...slug%5D%5D-91290b955cc22538.js

%5B%5B...slug%5D%5D-91290b955cc22538.js

140 ms

_buildManifest.js

_buildManifest.js

174 ms

_ssgManifest.js

_ssgManifest.js

172 ms

headerLogoLight.webp

headerLogoLight.webp

136 ms

Incident-management-Hero.webp

Incident-management-Hero.webp

140 ms

rainbow_line.png

rainbow_line.png

140 ms

otSDKStub.js

otSDKStub.js

134 ms

freshworks.js

freshworks.js

136 ms

E-v1.js

E-v1.js

75 ms

v30-400.woff

v30-400.woff

29 ms

v30-500.woff

v30-500.woff

29 ms

v30-300.woff

v30-300.woff

29 ms

v30-100.woff

v30-100.woff

29 ms

v30-700.woff

v30-700.woff

29 ms

v30-900.woff

v30-900.woff

42 ms

Accessibility Review

freshstatus.io accessibility score

98

Accessibility Issues

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

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

Page has valid source maps

SEO Factors

freshstatus.io SEO score

93

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

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 Freshstatus.io 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 Freshstatus.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

freshstatus.io

Open Graph data is detected on the main page of Freshstatus. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: