Access ext.co.in. webthemez - starter-Responsive-Coming-Soon-Template

name

value

score

weighting

FCP (First Contentful Paint)

Value2.3 s

75/100

10%

LCP (Largest Contentful Paint)

Value2.3 s

93/100

25%

SI (Speed Index)

Value3.4 s

90/100

10%

TBT (Total Blocking Time)

Value140 ms

95/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value2.9 s

96/100

10%

ext.co.in

38 ms

ext.co.in

209 ms

bootstrap.min.css

147 ms

animate.css

100 ms

styles.css

123 ms

Our browser made a total of 29 requests to load all elements on the main page. We found that 76% of them (22 requests) were addressed to the original Ext.co.in, 17% (5 requests) were made to Fonts.gstatic.com and 7% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (283 ms) belongs to the original domain Ext.co.in.

Content Size

687.0 kB

After Optimization

675.3 kB

In fact, the total size of Ext.co.in main page is 687.0 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. 40% of websites need less resources to load. Images take 675.2 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 9.0 kB

Original 11.8 kB
After minification 10.3 kB
After compression 2.7 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. This page needs HTML code to be minified as it can gain 1.4 kB, which is 12% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 9.0 kB or 77% of the original size.

Image Optimization

-0%

Potential reduce by 2.6 kB

Original 675.2 kB
After minification 672.6 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. Ext images are well optimized though.

Requests Now

After Optimization

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

Accessibility Issues

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

These items highlight common accessibility best practices.

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

High

Serves images with low resolution

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

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

Image elements do not have [alt] attributes

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/).

High

Document uses legible font sizes

Language and Encoding

Language Detected

LA
Language Claimed

EN
Encoding

UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ext.co.in can be misinterpreted by Google and other search engines. Our service has detected that Latin is used on the page, and it does not match the claimed English language. Our system also found out that Ext.co.in 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 Ext. 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: