Report Summary

  • 29

    Performance

    Renders faster than
    49% of other websites

  • 67

    Accessibility

    Visual factors better than
    that of 32% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

alikor.com

Алькор • Бриллианты России • Ювелирная Фабрика

Page Load Speed

2.6 sec in total

First Response

443 ms

Resources Loaded

2 sec

Page Rendered

164 ms

About Website

Welcome to alikor.com homepage info - get ready to check Alikor best content for Russia right away, or after learning these important things about alikor.com

Официальный сайт костромской ювелирной фабрики «Алькор». Вся информация о производителе, коллекциях, украшениях, контактах

Visit alikor.com

Key Findings

We analyzed Alikor.com page load time and found that the first response time was 443 ms and then it took 2.1 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

alikor.com performance score

29

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.1 s

3/100

10%

LCP (Largest Contentful Paint)

Value8.2 s

2/100

25%

SI (Speed Index)

Value12.7 s

3/100

10%

TBT (Total Blocking Time)

Value340 ms

74/100

30%

CLS (Cumulative Layout Shift)

Value0.434

22/100

15%

TTI (Time to Interactive)

Value9.8 s

28/100

10%

Network Requests Diagram

alikor.com

443 ms

base.css

139 ms

error.css

286 ms

base.css

154 ms

error.css

152 ms

Our browser made a total of 8 requests to load all elements on the main page. We found that all of those requests were addressed to Alikor.com and no external sources were called. The less responsive or slowest element that took the longest time to load (953 ms) belongs to the original domain Alikor.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 14.3 kB (12%)

Content Size

123.4 kB

After Optimization

109.1 kB

In fact, the total size of Alikor.com main page is 123.4 kB. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only a small number of websites need less resources to load. Images take 104.9 kB which makes up the majority of the site volume.

HTML Optimization

-52%

Potential reduce by 877 B

  • Original 1.7 kB
  • After minification 1.6 kB
  • After compression 821 B

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 877 B or 52% of the original size.

Image Optimization

-0%

Potential reduce by 30 B

  • Original 104.9 kB
  • After minification 104.9 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. Alikor images are well optimized though.

CSS Optimization

-80%

Potential reduce by 13.4 kB

  • Original 16.8 kB
  • After minification 10.9 kB
  • After compression 3.4 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. Alikor.com needs all CSS files to be minified and compressed as it can save up to 13.4 kB or 80% of the original size.

Requests Breakdown

Number of requests can be reduced by 4 (57%)

Requests Now

7

After Optimization

3

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

Accessibility Review

alikor.com accessibility score

67

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

[aria-*] attributes do not have valid values

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.

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

Links do not have a discernible name

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

List items (<li>) are not contained within <ul> or <ol> parent elements.

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

alikor.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

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

Page has valid source maps

SEO Factors

alikor.com SEO score

86

Search Engine Optimization Advices

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

    RU

  • Language Claimed

    RU

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Alikor.com can be misinterpreted by Google and other search engines. Our service has detected that Russian is used on the page, and it matches the claimed language. Our system also found out that Alikor.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

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