Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 50% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 91

    SEO

    Google-friendlier than
    71% of websites

olocker.in

Olocker

Page Load Speed

12.5 sec in total

First Response

737 ms

Resources Loaded

10 sec

Page Rendered

1.8 sec

olocker.in screenshot

About Website

Click here to check amazing Olocker content for India. Otherwise, check out these important facts you probably never knew about olocker.in

About Us Empowering Retailers. Enriching Jewellery Buyers. Olocker is creating innovative solutions for jewellery owners and jewellery retailers. Our aim is: To assist retailers in acquiring & retain ...

Visit olocker.in

Key Findings

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

Performance Metrics

olocker.in performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.7 s

5/100

10%

LCP (Largest Contentful Paint)

Value19.8 s

0/100

25%

SI (Speed Index)

Value28.0 s

0/100

10%

TBT (Total Blocking Time)

Value1,630 ms

12/100

30%

CLS (Cumulative Layout Shift)

Value0.113

86/100

15%

TTI (Time to Interactive)

Value24.8 s

0/100

10%

Network Requests Diagram

olocker.in

737 ms

olocker.in

6034 ms

siteground-optimizer-combined-css-f29c0ef1b866d7e582eba1bf02b09fb7.css

1974 ms

font-awesome.min.css

33 ms

jquery.min.js

1012 ms

Our browser made a total of 65 requests to load all elements on the main page. We found that 62% of them (40 requests) were addressed to the original Olocker.in, 18% (12 requests) were made to Webmodel.glowffy.com and 15% (10 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (6 sec) belongs to the original domain Olocker.in.

Page Optimization Overview & Recommendations

Page size can be reduced by 439.1 kB (9%)

Content Size

4.7 MB

After Optimization

4.3 MB

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

HTML Optimization

-89%

Potential reduce by 266.8 kB

  • Original 299.1 kB
  • After minification 297.0 kB
  • After compression 32.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. 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 266.8 kB or 89% of the original size.

Image Optimization

-5%

Potential reduce by 170.8 kB

  • Original 3.7 MB
  • After minification 3.5 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. Olocker images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 36 B

  • Original 451.2 kB
  • After minification 451.2 kB
  • After compression 451.1 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

-1%

Potential reduce by 1.5 kB

  • Original 270.4 kB
  • After minification 270.4 kB
  • After compression 268.9 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. Olocker.in has all CSS files already compressed.

Requests Breakdown

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

Requests Now

38

After Optimization

33

The browser has sent 38 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Olocker. 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.

Accessibility Review

olocker.in accessibility score

80

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

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.

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

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

Best Practices

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

Missing source maps for large first-party JavaScript

SEO Factors

olocker.in SEO score

91

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

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

High

Tap targets are not sized appropriately

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 Olocker.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 Olocker.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 data is detected on the main page of Olocker. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: