Access freshworks.io. Web and mobile app design and development

Report Summary

About Website

Welcome to freshworks.io homepage info - get ready to check Freshworks best content for India right away, or after learning these important things about freshworks.io

Best-in-class web and mobile app design and development by EY Design Studio. Scalable, end-to-end digital solutions for all industry verticals.

Visit freshworks.io

name

value

score

weighting

FCP (First Contentful Paint)

Value7.2 s

1/100

10%

LCP (Largest Contentful Paint)

Value22.1 s

0/100

25%

SI (Speed Index)

Value7.2 s

30/100

10%

TBT (Total Blocking Time)

Value380 ms

70/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value43.8 s

0/100

10%

freshworks.io

95 ms

studio.ca.ey.com

237 ms

610fb59623c06fd8.css

209 ms

ceeaadeea43dd306.css

182 ms

3917e5a045bf040f.css

208 ms

Our browser made a total of 129 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Freshworks.io, 54% (70 requests) were made to Fonts.gstatic.com and 26% (33 requests) were made to Studio.ca.ey.com. The less responsive or slowest element that took the longest time to load (631 ms) relates to the external source Studio.ca.ey.com.

Content Size

5.1 MB

After Optimization

2.4 MB

In fact, the total size of Freshworks.io main page is 5.1 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. Only a small number of websites need less resources to load. Javascripts take 2.3 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 66.4 kB

Original 80.9 kB
After minification 80.9 kB
After compression 14.6 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 66.4 kB or 82% of the original size.

Image Optimization

-18%

Potential reduce by 373.1 kB

Original 2.1 MB
After minification 1.7 MB

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, Freshworks needs image optimization as it can save up to 373.1 kB or 18% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-72%

Potential reduce by 1.7 MB

Original 2.3 MB
After minification 2.3 MB
After compression 629.0 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 1.7 MB or 72% of the original size.

CSS Optimization

-88%

Potential reduce by 553.3 kB

Original 630.9 kB
After minification 625.8 kB
After compression 77.6 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. Freshworks.io needs all CSS files to be minified and compressed as it can save up to 553.3 kB or 88% of the original size.

Requests Now

119

After Optimization

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

Accessibility Issues

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.

High

Document doesn't have a <title> element

These are opportunities to improve the interpretation of your content by users in different locales.

High

<html> element does not have a [lang] attribute

Areas of Improvement

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

High

Issues were logged in the Issues panel in Chrome Devtools

Search Engine Optimization Advices

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

High

Document doesn't have a <title> element

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

freshworks.io

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

Report Summary

Performance

Accessibility

Best Practices

SEO

Web and mobile app design and development | EY Design Studio

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)