Tools & Wizards About Us
econorm.in screenshot

Report Summary

  • 25

    Performance

    Renders faster than
    44% of other websites

  • 92

    Accessibility

    Visual factors better than
    that of 78% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

econorm.in

sboulardii – CNCM i-745 – Un site utilisant WordPress

Page Load Speed

3.5 sec in total

First Response

169 ms

Resources Loaded

2.9 sec

Page Rendered

369 ms

econorm.in screenshot

About Website

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

Visit econorm.in

Key Findings

We analyzed Econorm.in page load time and found that the first response time was 169 ms and then it took 3.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

econorm.in performance score

25

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.0 s

9/100

10%

LCP (Largest Contentful Paint)

Value5.3 s

21/100

25%

SI (Speed Index)

Value11.9 s

4/100

10%

TBT (Total Blocking Time)

Value2,010 ms

7/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value11.9 s

16/100

10%

Network Requests Diagram

econorm.in

169 ms

econorm.in

321 ms

601 ms

style.min.css

159 ms

index.css

239 ms

Our browser made a total of 46 requests to load all elements on the main page. We found that 4% of them (2 requests) were addressed to the original Econorm.in, 72% (33 requests) were made to Saccharomycesboulardii.com and 9% (4 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (799 ms) relates to the external source Saccharomycesboulardii.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 118.6 kB (4%)

Content Size

3.1 MB

After Optimization

2.9 MB

  • HTML
  • Images

In fact, the total size of Econorm.in main page is 3.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. 70% of websites need less resources to load. Images take 2.9 MB which makes up the majority of the site volume.

HTML Optimization

-89%

Potential reduce by 95.9 kB

  • Original 108.1 kB
  • After minification 60.7 kB
  • After compression 12.2 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 47.4 kB, which is 44% 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 95.9 kB or 89% of the original size.

Image Optimization

-1%

Potential reduce by 22.7 kB

  • Original 2.9 MB
  • After minification 2.9 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. Econorm images are well optimized though.

Requests Breakdown

Number of requests can be reduced by 21 (54%)

Requests Now

39

After Optimization

18

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

econorm.in

econorm.in

169 ms

econorm.in

econorm.in

321 ms

601 ms

style.min.css

style.min.css

159 ms

index.css

index.css

239 ms

style.css

style.css

403 ms

mapbox-gl.css

mapbox-gl.css

13 ms

clipboard.min.js

clipboard.min.js

167 ms

swiper.min.js

swiper.min.js

255 ms

preloadjs.min.js

preloadjs.min.js

325 ms

gsap.min.js

gsap.min.js

325 ms

MorphSVGPlugin.min.js

MorphSVGPlugin.min.js

243 ms

ScrollToPlugin.min.js

ScrollToPlugin.min.js

247 ms

mapbox-gl.js

mapbox-gl.js

8 ms

modernizr-3.6.0.min.js

modernizr-3.6.0.min.js

325 ms

TweenMax-1.20.3.min.js

TweenMax-1.20.3.min.js

463 ms

hammer-2.0.8.min.js

hammer-2.0.8.min.js

337 ms

Slame.js

Slame.js

463 ms

vendor.min.js

vendor.min.js

462 ms

jquery.js

jquery.js

621 ms

custom.min.js

custom.min.js

462 ms

css

css

38 ms

loader.js

loader.js

314 ms

gtm.js

gtm.js

216 ms

logo-saccharomyces.png

logo-saccharomyces.png

215 ms

logo-sboulardii.png

logo-sboulardii.png

311 ms

logo-cncm.png

logo-cncm.png

311 ms

arrow-down-dark-secondary.png

arrow-down-dark-secondary.png

275 ms

global.jpg

global.jpg

275 ms

PICTO-FAQ-medium.png

PICTO-FAQ-medium.png

274 ms

PICTO-Contact-Medium-1-1.png

PICTO-Contact-Medium-1-1.png

383 ms

flag.png

flag.png

383 ms

arrow-down.png

arrow-down.png

381 ms

arrow-next.png

arrow-next.png

380 ms

whatissb.jpg

whatissb.jpg

799 ms

whatissb_M-e1592398000284.jpg

whatissb_M-e1592398000284.jpg

796 ms

therapeutic_area.jpg

therapeutic_area.jpg

799 ms

therapeutic_area_M-e1592398872915.jpg

therapeutic_area_M-e1592398872915.jpg

796 ms

probiotics.jpg

probiotics.jpg

799 ms

probiotics_M-e1592399400615.jpg

probiotics_M-e1592399400615.jpg

796 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aXx-p7K4GLs.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aXx-p7K4GLs.woff

270 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aXx-p7K4GLs.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aXx-p7K4GLs.woff

276 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aXx-p7K4GLs.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aXx-p7K4GLs.woff

276 ms

JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq5Z9WXh0oJC8MLnrtQ.woff

JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq5Z9WXh0oJC8MLnrtQ.woff

225 ms

sdk.a87f6fcd5e15a6232584fb43b37012b231121cda.js

sdk.a87f6fcd5e15a6232584fb43b37012b231121cda.js

24 ms

ui-gdpr-en-web.a87f6fcd5e15a6232584fb43b37012b231121cda.js

ui-gdpr-en-web.a87f6fcd5e15a6232584fb43b37012b231121cda.js

329 ms

Accessibility Review

econorm.in accessibility score

92

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

Best Practices

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

econorm.in SEO score

93

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

econorm.in

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