Tools & Wizards About Us
elastic.run screenshot

Report Summary

  • 24

    Performance

    Renders faster than
    43% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

elastic.run

ElasticRun | B2B eCommerce platform for rural India

Page Load Speed

6.3 sec in total

First Response

394 ms

Resources Loaded

5 sec

Page Rendered

1 sec

elastic.run screenshot

About Website

Welcome to elastic.run homepage info - get ready to check Elastic best content for India right away, or after learning these important things about elastic.run

ElasticRun extends the reach of brand’s direct distribution networks to deep rural markets. It enables access to a set of net new stores and customers for the brands, which were not accessible through...

Visit elastic.run

Key Findings

We analyzed Elastic.run page load time and found that the first response time was 394 ms and then it took 6 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

elastic.run performance score

24

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

35/100

10%

LCP (Largest Contentful Paint)

Value13.0 s

0/100

25%

SI (Speed Index)

Value7.3 s

28/100

10%

TBT (Total Blocking Time)

Value1,170 ms

21/100

30%

CLS (Cumulative Layout Shift)

Value0.159

73/100

15%

TTI (Time to Interactive)

Value22.3 s

1/100

10%

Network Requests Diagram

elastic.run

394 ms

elastic.run

794 ms

bootstrap.min.css

198 ms

style.css

391 ms

owl.carousel.min.css

558 ms

Our browser made a total of 85 requests to load all elements on the main page. We found that 84% of them (71 requests) were addressed to the original Elastic.run, 8% (7 requests) were made to Youtube.com and 2% (2 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (2.7 sec) belongs to the original domain Elastic.run.

Page Optimization Overview & Recommendations

Page size can be reduced by 115.0 kB (11%)

Content Size

1.1 MB

After Optimization

953.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Elastic.run main page is 1.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. Images take 698.2 kB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 43.1 kB

  • Original 50.4 kB
  • After minification 31.8 kB
  • After compression 7.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 18.6 kB, which is 37% 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 43.1 kB or 85% of the original size.

Image Optimization

-10%

Potential reduce by 66.5 kB

  • Original 698.2 kB
  • After minification 631.7 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. Elastic images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 2.9 kB

  • Original 222.3 kB
  • After minification 222.0 kB
  • After compression 219.3 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.

CSS Optimization

-2%

Potential reduce by 2.4 kB

  • Original 97.3 kB
  • After minification 97.3 kB
  • After compression 94.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. Elastic.run has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 20 (26%)

Requests Now

77

After Optimization

57

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

elastic.run

elastic.run

394 ms

elastic.run

elastic.run

794 ms

bootstrap.min.css

bootstrap.min.css

198 ms

style.css

style.css

391 ms

owl.carousel.min.css

owl.carousel.min.css

558 ms

font-awesome.min.css

font-awesome.min.css

591 ms

style.css

style.css

603 ms

Elasticrun-logo-w.svg

Elasticrun-logo-w.svg

932 ms

Elasticrun-logo.svg

Elasticrun-logo.svg

950 ms

Union.svg

Union.svg

971 ms

close.svg

close.svg

788 ms

twitter.svg

twitter.svg

787 ms

in.svg

in.svg

793 ms

facebook.svg

facebook.svg

984 ms

instagram.svg

instagram.svg

987 ms

eCommerceplatform.svg

eCommerceplatform.svg

2132 ms

eCommerceplatformMobile.svg

eCommerceplatformMobile.svg

1857 ms

ElasticRunSolvedRural.svg

ElasticRunSolvedRural.svg

1901 ms

ElasticRunSolvedRuralMobile.svg

ElasticRunSolvedRuralMobile.svg

1928 ms

brand.svg

brand.svg

1181 ms

deepreach.svg

deepreach.svg

1184 ms

dataedge.svg

dataedge.svg

1389 ms

ElasticRunMap.svg

ElasticRunMap.svg

2188 ms

ElasticRunMapMobile.svg

ElasticRunMapMobile.svg

2366 ms

jquery.min.js

jquery.min.js

2047 ms

generic.js

generic.js

2088 ms

bootstrap.min.js

bootstrap.min.js

2121 ms

script.js

script.js

2234 ms

Beiersdorf_Logo.png

Beiersdorf_Logo.png

2277 ms

client3.svg

client3.svg

2314 ms

client11.svg

client11.svg

2323 ms

P_G.png

P_G.png

2358 ms

pepsico.png

pepsico.png

2563 ms

client5.svg

client5.svg

2723 ms

client12.svg

client12.svg

2664 ms

Perfetti_Van_Melle_logo.png

Perfetti_Van_Melle_logo.png

2693 ms

merico.png

merico.png

2694 ms

client15.svg

client15.svg

2694 ms

client10.svg

client10.svg

2670 ms

client14.svg

client14.svg

2334 ms

gohnson.png

gohnson.png

2170 ms

itc.png

itc.png

2190 ms

client2.svg

client2.svg

2304 ms

ubuntu-regular-webfont.woff

ubuntu-regular-webfont.woff

2185 ms

ubuntu-medium-webfont.woff

ubuntu-medium-webfont.woff

2183 ms

ubuntu-light-webfont.woff

ubuntu-light-webfont.woff

2177 ms

ubuntu-bold-webfont.woff

ubuntu-bold-webfont.woff

2084 ms

tata.png

tata.png

2067 ms

nestle.png

nestle.png

2132 ms

client4.svg

client4.svg

2133 ms

minitifi.png

minitifi.png

2124 ms

hul.svg

hul.svg

1981 ms

forbes-logo.png

forbes-logo.png

1991 ms

arrowRightWhite.svg

arrowRightWhite.svg

1783 ms

forbesImage.png

forbesImage.png

1419 ms

Bloomberg.png

Bloomberg.png

1378 ms

businessst.svg

businessst.svg

1362 ms

moneycontrol-logo.png

moneycontrol-logo.png

1309 ms

tech.svg

tech.svg

1291 ms

microsoft.svg

microsoft.svg

1246 ms

world.svg

world.svg

1295 ms

etrise.svg

etrise.svg

1294 ms

iframe_api

iframe_api

42 ms

vccircle2.svg

vccircle2.svg

1284 ms

www-widgetapi.js

www-widgetapi.js

5 ms

etrise2.svg

etrise2.svg

1284 ms

QfEhJvB3-e8

QfEhJvB3-e8

96 ms

Cision_PRN_Teal.png

Cision_PRN_Teal.png

1253 ms

arrowright.svg

arrowright.svg

1228 ms

thambnil.jpg

thambnil.jpg

1311 ms

possibilities.png

possibilities.png

1309 ms

www-player.css

www-player.css

7 ms

www-embed-player.js

www-embed-player.js

25 ms

base.js

base.js

47 ms

ad_status.js

ad_status.js

205 ms

UCY5Klx_0fJhMytIltuKLUwnjJON9GWedkq6jjIrpW0.js

UCY5Klx_0fJhMytIltuKLUwnjJON9GWedkq6jjIrpW0.js

170 ms

embed.js

embed.js

112 ms

hackathon2022.png

hackathon2022.png

1018 ms

microsoft.png

microsoft.png

1067 ms

closeicon.svg

closeicon.svg

1064 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

59 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

65 ms

id

id

20 ms

Create

Create

101 ms

GenerateIT

GenerateIT

21 ms

Accessibility Review

elastic.run accessibility score

88

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

elastic.run best practices score

92

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

Page has valid source maps

SEO Factors

elastic.run SEO score

85

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

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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 Elastic.run 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 Elastic.run 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

elastic.run

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