Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 76

    Accessibility

    Visual factors better than
    that of 43% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 87

    SEO

    Google-friendlier than
    66% of websites

apelio.ru

Автозапчасти, запчасти для иномарок оптом и в розницу

Page Load Speed

4.9 sec in total

First Response

518 ms

Resources Loaded

4.1 sec

Page Rendered

260 ms

apelio.ru screenshot

About Website

Welcome to apelio.ru homepage info - get ready to check Apelio best content for Russia right away, or after learning these important things about apelio.ru

Запчасти для грузовых и легковых иномарок в г.Рязани, самые низкие цены в городе, кратчайшие сроки доставки, оптовые поставки автозапчастей

Visit apelio.ru

Key Findings

We analyzed Apelio.ru page load time and found that the first response time was 518 ms and then it took 4.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

apelio.ru performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value10.5 s

0/100

10%

LCP (Largest Contentful Paint)

Value10.5 s

0/100

25%

SI (Speed Index)

Value15.8 s

0/100

10%

TBT (Total Blocking Time)

Value3,480 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.076

95/100

15%

TTI (Time to Interactive)

Value14.7 s

8/100

10%

Network Requests Diagram

apelio.ru

518 ms

styles.css

1857 ms

as.js

394 ms

example.css

393 ms

jquery.min.js

562 ms

Our browser made a total of 50 requests to load all elements on the main page. We found that 62% of them (31 requests) were addressed to the original Apelio.ru, 22% (11 requests) were made to Vk.com and 8% (4 requests) were made to Top-fwz1.mail.ru. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Apelio.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 371.1 kB (66%)

Content Size

560.6 kB

After Optimization

189.5 kB

In fact, the total size of Apelio.ru main page is 560.6 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. 30% of websites need less resources to load. Javascripts take 336.1 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 26.2 kB

  • Original 34.2 kB
  • After minification 31.5 kB
  • After compression 8.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 26.2 kB or 77% of the original size.

Image Optimization

-9%

Potential reduce by 6.1 kB

  • Original 71.2 kB
  • After minification 65.1 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. Apelio images are well optimized though.

JavaScript Optimization

-70%

Potential reduce by 236.8 kB

  • Original 336.1 kB
  • After minification 277.4 kB
  • After compression 99.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 236.8 kB or 70% of the original size.

CSS Optimization

-86%

Potential reduce by 102.0 kB

  • Original 119.1 kB
  • After minification 94.7 kB
  • After compression 17.1 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. Apelio.ru needs all CSS files to be minified and compressed as it can save up to 102.0 kB or 86% of the original size.

Requests Breakdown

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

Requests Now

47

After Optimization

21

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

Accessibility Review

apelio.ru accessibility score

76

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

Best Practices

apelio.ru best practices score

67

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

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

apelio.ru SEO score

87

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    RU

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Apelio.ru can be misinterpreted by Google and other search engines. Our service has detected that Russian is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Apelio.ru 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 Apelio. 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: