Tools & Wizards About Us
selloldgold.ejohri.com screenshot

Report Summary

  • 3

    Performance

    Renders faster than
    20% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 83% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

selloldgold.ejohri.com

Sell Old Gold Jewelry For Instant Cash At Best Rates | eJOHRI

Page Load Speed

6.8 sec in total

First Response

391 ms

Resources Loaded

5.7 sec

Page Rendered

803 ms

selloldgold.ejohri.com screenshot

About Website

Click here to check amazing Sell Old Gold EJOHRI content for India. Otherwise, check out these important facts you probably never knew about selloldgold.ejohri.com

Sell your unused old gold jewellery for cash at the best value and rates in India. ✓Instant Cash ✓Free Purity Testing ✓Best Value

Visit selloldgold.ejohri.com

Key Findings

We analyzed Selloldgold.ejohri.com page load time and found that the first response time was 391 ms and then it took 6.5 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

selloldgold.ejohri.com performance score

3

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value8.7 s

0/100

10%

LCP (Largest Contentful Paint)

Value19.1 s

0/100

25%

SI (Speed Index)

Value15.9 s

0/100

10%

TBT (Total Blocking Time)

Value1,830 ms

9/100

30%

CLS (Cumulative Layout Shift)

Value1.212

1/100

15%

TTI (Time to Interactive)

Value19.7 s

2/100

10%

Network Requests Diagram

selloldgold.ejohri.com

391 ms

selloldgold.ejohri.com

757 ms

js

171 ms

fbevents.js

84 ms

default

226 ms

Our browser made a total of 51 requests to load all elements on the main page. We found that 69% of them (35 requests) were addressed to the original Selloldgold.ejohri.com, 16% (8 requests) were made to Embed.tawk.to and 4% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Selloldgold.ejohri.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 170.8 kB (26%)

Content Size

653.3 kB

After Optimization

482.5 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Selloldgold.ejohri.com main page is 653.3 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. 60% of websites need less resources to load. Images take 326.8 kB which makes up the majority of the site volume.

HTML Optimization

-68%

Potential reduce by 110.2 kB

  • Original 163.2 kB
  • After minification 163.2 kB
  • After compression 53.0 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 110.2 kB or 68% of the original size.

Image Optimization

-4%

Potential reduce by 12.6 kB

  • Original 326.8 kB
  • After minification 314.2 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. Sell Old Gold EJOHRI images are well optimized though.

JavaScript Optimization

-29%

Potential reduce by 48.0 kB

  • Original 163.3 kB
  • After minification 163.3 kB
  • After compression 115.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 48.0 kB or 29% of the original size.

Requests Breakdown

Number of requests can be reduced by 38 (83%)

Requests Now

46

After Optimization

8

  • AJAX
  • Images
  • JavaScript

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

Network Requests Diagram

selloldgold.ejohri.com

selloldgold.ejohri.com

391 ms

selloldgold.ejohri.com

selloldgold.ejohri.com

757 ms

js

js

171 ms

fbevents.js

fbevents.js

84 ms

default

default

226 ms

runtime.f08bf52b3b0fc70fff48.js

runtime.f08bf52b3b0fc70fff48.js

223 ms

npm.babel.1222f4145d1127e16180.chunk.js

npm.babel.1222f4145d1127e16180.chunk.js

966 ms

npm.webpack.94424e57d226108a8439.chunk.js

npm.webpack.94424e57d226108a8439.chunk.js

665 ms

npm.react-app-polyfill.49af85bb15a26a702e91.chunk.js

npm.react-app-polyfill.49af85bb15a26a702e91.chunk.js

830 ms

npm.react-redux.44b4574e1b907dc70547.chunk.js

npm.react-redux.44b4574e1b907dc70547.chunk.js

833 ms

npm.redux-saga.757b19bf163633a2606a.chunk.js

npm.redux-saga.757b19bf163633a2606a.chunk.js

835 ms

npm.react-transition-group.1acda47978b5a16ac246.chunk.js

npm.react-transition-group.1acda47978b5a16ac246.chunk.js

836 ms

npm.react-router.ef890ab78b84ac95ea9d.chunk.js

npm.react-router.ef890ab78b84ac95ea9d.chunk.js

1038 ms

npm.react-router-dom.503ae64fc4a25f255d2f.chunk.js

npm.react-router-dom.503ae64fc4a25f255d2f.chunk.js

1013 ms

npm.loadable.c88fa00b183142afbd3a.chunk.js

npm.loadable.c88fa00b183142afbd3a.chunk.js

1017 ms

main.1b06825dc400cb4e93cb.chunk.js

main.1b06825dc400cb4e93cb.chunk.js

1950 ms

1094294867312675

1094294867312675

149 ms

js

js

128 ms

analytics.js

analytics.js

16 ms

collect

collect

14 ms

collect

collect

27 ms

ga-audiences

ga-audiences

109 ms

2bfaac59e271ae3670ffb295085bec7b.gif

2bfaac59e271ae3670ffb295085bec7b.gif

369 ms

0.c8e21e840f998a640323.chunk.js

0.c8e21e840f998a640323.chunk.js

369 ms

33.632002e76f9d7edb381d.chunk.js

33.632002e76f9d7edb381d.chunk.js

189 ms

78a4c5bf3c542cd4a1b5e4c3332fefc7.otf

78a4c5bf3c542cd4a1b5e4c3332fefc7.otf

935 ms

796e460a7d6c857ede54298a69d14ddf.otf

796e460a7d6c857ede54298a69d14ddf.otf

422 ms

3c9eb6f6bcbe603dbbb2c209f0cebbcc.otf

3c9eb6f6bcbe603dbbb2c209f0cebbcc.otf

743 ms

npm.react-slick.27fbc3a1f11e2aac8ac6.chunk.js

npm.react-slick.27fbc3a1f11e2aac8ac6.chunk.js

368 ms

npm.enquire.js.c564f2c8c606def73795.chunk.js

npm.enquire.js.c564f2c8c606def73795.chunk.js

185 ms

npm.json2mq.5e53f13d068d8161b0b4.chunk.js

npm.json2mq.5e53f13d068d8161b0b4.chunk.js

189 ms

npm.lodash.debounce.e44805f1c99aac410b5a.chunk.js

npm.lodash.debounce.e44805f1c99aac410b5a.chunk.js

186 ms

23.e2e163c1e3dac76f4585.chunk.js

23.e2e163c1e3dac76f4585.chunk.js

369 ms

npm.axios.60333c6d0a468e435d52.chunk.js

npm.axios.60333c6d0a468e435d52.chunk.js

420 ms

npm.process.ba38c796832829b32170.chunk.js

npm.process.ba38c796832829b32170.chunk.js

421 ms

21.e877d0a6fcac329cbb16.chunk.js

21.e877d0a6fcac329cbb16.chunk.js

1081 ms

25.556ca9eaaf2ca52fdc69.chunk.js

25.556ca9eaaf2ca52fdc69.chunk.js

552 ms

29.bec662eb10b49d1896e8.chunk.js

29.bec662eb10b49d1896e8.chunk.js

552 ms

31.9a7407f5d24617909cc5.chunk.js

31.9a7407f5d24617909cc5.chunk.js

572 ms

26.7bf0b31edde197c3c34c.chunk.js

26.7bf0b31edde197c3c34c.chunk.js

748 ms

27.2d4fdc534bd985402214.chunk.js

27.2d4fdc534bd985402214.chunk.js

709 ms

fab4afdf00d2b75b191373bafa84bed5.jpg

fab4afdf00d2b75b191373bafa84bed5.jpg

864 ms

db26f2328167475f001875a1936bdccb.png

db26f2328167475f001875a1936bdccb.png

189 ms

318c453ba7e71ff8c9a9d6645b81b844.png

318c453ba7e71ff8c9a9d6645b81b844.png

190 ms

twk-event-polyfill.js

twk-event-polyfill.js

58 ms

twk-main.js

twk-main.js

117 ms

twk-vendor.js

twk-vendor.js

160 ms

twk-chunk-vendors.js

twk-chunk-vendors.js

214 ms

twk-chunk-common.js

twk-chunk-common.js

187 ms

twk-runtime.js

twk-runtime.js

112 ms

twk-app.js

twk-app.js

110 ms

Accessibility Review

selloldgold.ejohri.com accessibility score

94

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.

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

selloldgold.ejohri.com 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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

selloldgold.ejohri.com SEO score

100

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 Selloldgold.ejohri.com 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 Selloldgold.ejohri.com 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

selloldgold.ejohri.com

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