Tools & Wizards About Us
datasense.in screenshot

Report Summary

  • 51

    Performance

    Renders faster than
    69% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

datasense.in

Datasense.in

Page Load Speed

2.2 sec in total

First Response

167 ms

Resources Loaded

1 sec

Page Rendered

962 ms

datasense.in screenshot

About Website

Visit datasense.in now to see the best up-to-date Datasense content and also check out these interesting facts you probably never knew about datasense.in

Visit datasense.in

Key Findings

We analyzed Datasense.in page load time and found that the first response time was 167 ms and then it took 2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

datasense.in performance score

51

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.5 s

1/100

10%

LCP (Largest Contentful Paint)

Value19.0 s

0/100

25%

SI (Speed Index)

Value7.5 s

27/100

10%

TBT (Total Blocking Time)

Value150 ms

95/100

30%

CLS (Cumulative Layout Shift)

Value0.032

100/100

15%

TTI (Time to Interactive)

Value7.6 s

46/100

10%

Network Requests Diagram

datasense.in

167 ms

bootstrap.min.css

143 ms

style.css

295 ms

font-awesome.css

108 ms

aos.css

43 ms

Our browser made a total of 57 requests to load all elements on the main page. We found that 93% of them (53 requests) were addressed to the original Datasense.in, 4% (2 requests) were made to Unpkg.com and 2% (1 request) were made to Cdnjs.cloudflare.com. The less responsive or slowest element that took the longest time to load (417 ms) belongs to the original domain Datasense.in.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.4 MB (24%)

Content Size

5.9 MB

After Optimization

4.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Datasense.in main page is 5.9 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. Images take 4.9 MB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 37.2 kB

  • Original 42.5 kB
  • After minification 22.4 kB
  • After compression 5.3 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 20.1 kB, which is 47% 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 37.2 kB or 88% of the original size.

Image Optimization

-10%

Potential reduce by 504.2 kB

  • Original 4.9 MB
  • After minification 4.4 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. Datasense images are well optimized though.

JavaScript Optimization

-70%

Potential reduce by 104.3 kB

  • Original 148.8 kB
  • After minification 141.2 kB
  • After compression 44.4 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 104.3 kB or 70% of the original size.

CSS Optimization

-93%

Potential reduce by 744.2 kB

  • Original 804.1 kB
  • After minification 678.1 kB
  • After compression 59.8 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. Datasense.in needs all CSS files to be minified and compressed as it can save up to 744.2 kB or 93% of the original size.

Requests Breakdown

Number of requests can be reduced by 5 (10%)

Requests Now

52

After Optimization

47

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

datasense.in

datasense.in

167 ms

bootstrap.min.css

bootstrap.min.css

143 ms

style.css

style.css

295 ms

font-awesome.css

font-awesome.css

108 ms

aos.css

aos.css

43 ms

jquery.min.js

jquery.min.js

163 ms

aos.js

aos.js

54 ms

bootstrap.min.js

bootstrap.min.js

116 ms

main.js

main.js

84 ms

script.js

script.js

128 ms

jquery.min.js

jquery.min.js

45 ms

vecteezy_using-mobile-smart-phone__31.jpg

vecteezy_using-mobile-smart-phone__31.jpg

98 ms

aerial.jpg

aerial.jpg

277 ms

logo2.png

logo2.png

83 ms

logo3.png

logo3.png

116 ms

4169215.png

4169215.png

81 ms

3428420.png

3428420.png

81 ms

4951160.png

4951160.png

82 ms

3764559.png

3764559.png

90 ms

3428418.png

3428418.png

96 ms

3428442.png

3428442.png

100 ms

3972398.png

3972398.png

97 ms

3805279.png

3805279.png

124 ms

7090837.png

7090837.png

135 ms

704187.png

704187.png

137 ms

1842315.png

1842315.png

138 ms

2500457.png

2500457.png

155 ms

1749067.png

1749067.png

158 ms

logo.svg

logo.svg

171 ms

InShot_20230712_011507272.jpg

InShot_20230712_011507272.jpg

187 ms

InShot_20230712_011543055.jpg

InShot_20230712_011543055.jpg

279 ms

billroth-hospital-logo.webp

billroth-hospital-logo.webp

201 ms

InShot_20230712_011705132.jpg

InShot_20230712_011705132.jpg

245 ms

InShot_20230712_011738150.jpg

InShot_20230712_011738150.jpg

291 ms

InShot_20230712_011802619.jpg

InShot_20230712_011802619.jpg

232 ms

Chennai-Corporation.png

Chennai-Corporation.png

286 ms

InShot_20230712_011953284.jpg

InShot_20230712_011953284.jpg

279 ms

InShot_20230712_012022540.jpg

InShot_20230712_012022540.jpg

347 ms

InShot_20230712_012107040.jpg

InShot_20230712_012107040.jpg

314 ms

InShot_20230712_012131522.jpg

InShot_20230712_012131522.jpg

355 ms

VVD.png

VVD.png

324 ms

InShot_20230712_012303430.jpg

InShot_20230712_012303430.jpg

386 ms

download.jpg

download.jpg

331 ms

InShot_20230712_012434355.jpg

InShot_20230712_012434355.jpg

353 ms

InShot_20230712_012507295.jpg

InShot_20230712_012507295.jpg

373 ms

InShot_20230712_012532638.jpg

InShot_20230712_012532638.jpg

392 ms

InShot_20230712_012552937.jpg

InShot_20230712_012552937.jpg

417 ms

InShot_20230712_012618442.jpg

InShot_20230712_012618442.jpg

322 ms

InShot_20230712_012644109.jpg

InShot_20230712_012644109.jpg

328 ms

InShot_20230712_012702297.jpg

InShot_20230712_012702297.jpg

342 ms

InShot_20230712_012722227.jpg

InShot_20230712_012722227.jpg

357 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

376 ms

FugazOne-Regular.woff

FugazOne-Regular.woff

350 ms

udupi.png

udupi.png

354 ms

673490.png

673490.png

363 ms

datasense.png

datasense.png

375 ms

now.png

now.png

380 ms

Accessibility Review

datasense.in accessibility score

78

Accessibility Issues

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

Buttons do not have an accessible name

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

datasense.in best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

datasense.in SEO score

92

Search Engine Optimization Advices

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 Datasense.in 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 Datasense.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

datasense.in

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