Tools & Wizards About Us
apelio.ru screenshot

Report Summary

  • 49

    Performance

    Renders faster than
    67% of other websites

  • 76

    Accessibility

    Visual factors better than
    that of 42% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 89

    SEO

    Google-friendlier than
    66% of websites

apelio.ru

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

Page Load Speed

5.6 sec in total

First Response

806 ms

Resources Loaded

4.7 sec

Page Rendered

114 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 806 ms and then it took 4.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

apelio.ru performance score

49

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.3 s

3/100

10%

LCP (Largest Contentful Paint)

Value6.3 s

10/100

25%

SI (Speed Index)

Value9.0 s

14/100

10%

TBT (Total Blocking Time)

Value230 ms

86/100

30%

CLS (Cumulative Layout Shift)

Value0.034

100/100

15%

TTI (Time to Interactive)

Value8.9 s

35/100

10%

Network Requests Diagram

apelio.ru

806 ms

style.min.css

295 ms

main.css

589 ms

catcs.css

960 ms

all.css

30 ms

Our browser made a total of 48 requests to load all elements on the main page. We found that 85% of them (41 requests) were addressed to the original Apelio.ru, 6% (3 requests) were made to Use.fontawesome.com and 6% (3 requests) were made to Mc.yandex.com. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain Apelio.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 53.8 kB (14%)

Content Size

371.5 kB

After Optimization

317.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-83%

Potential reduce by 40.9 kB

  • Original 49.2 kB
  • After minification 30.9 kB
  • After compression 8.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.3 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 40.9 kB or 83% of the original size.

Image Optimization

-6%

Potential reduce by 3.9 kB

  • Original 68.4 kB
  • After minification 64.5 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

-1%

Potential reduce by 1.1 kB

  • Original 193.1 kB
  • After minification 193.1 kB
  • After compression 192.0 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

-13%

Potential reduce by 7.9 kB

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

Requests Breakdown

Number of requests can be reduced by 22 (61%)

Requests Now

36

After Optimization

14

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 36 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 8 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

apelio.ru

apelio.ru

806 ms

style.min.css

style.min.css

295 ms

main.css

main.css

589 ms

catcs.css

catcs.css

960 ms

all.css

all.css

30 ms

easyflex.css

easyflex.css

628 ms

price_style.css

price_style.css

706 ms

tabmain.css

tabmain.css

748 ms

mobmain.css

mobmain.css

788 ms

leaflet.css

leaflet.css

881 ms

opensans.css

opensans.css

921 ms

leaflet.js

leaflet.js

1299 ms

jquery-3.3.1.min.js

jquery-3.3.1.min.js

1346 ms

jquery.inputmask.bundle.min.js

jquery.inputmask.bundle.min.js

1396 ms

datepicker.min.css

datepicker.min.css

1173 ms

datepicker.min.js

datepicker.min.js

1215 ms

fns.js

fns.js

1252 ms

script.js

script.js

1533 ms

common.js

common.js

1534 ms

tag.js

tag.js

937 ms

placeholder.png

placeholder.png

372 ms

phone-call.png

phone-call.png

294 ms

logo.png

logo.png

412 ms

exhaust-pipe.png

exhaust-pipe.png

331 ms

oil_bag.png

oil_bag.png

451 ms

koleso.png

koleso.png

491 ms

autohimia.png

autohimia.png

587 ms

instrument.png

instrument.png

627 ms

electronic.png

electronic.png

670 ms

car_aksess.png

car_aksess.png

716 ms

home.png

home.png

756 ms

soccer-ball.png

soccer-ball.png

796 ms

inst_logo.png

inst_logo.png

880 ms

vk-logo.png

vk-logo.png

994 ms

pfdintextpror.ttf

pfdintextpror.ttf

2368 ms

GothamPro.woff

GothamPro.woff

908 ms

GothamPro-Light.woff

GothamPro-Light.woff

950 ms

GothamPro-Bold.woff

GothamPro-Bold.woff

1284 ms

fa-solid-900.woff

fa-solid-900.woff

14 ms

fa-regular-400.woff

fa-regular-400.woff

31 ms

opensansbold.woff

opensansbold.woff

1062 ms

opensansextrabold.woff

opensansextrabold.woff

1108 ms

opensanssemibold.woff

opensanssemibold.woff

1213 ms

opensans.woff

opensans.woff

1253 ms

opensanslight.woff

opensanslight.woff

1358 ms

advert.gif

advert.gif

731 ms

sync_cookie_image_decide

sync_cookie_image_decide

173 ms

1

1

143 ms

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

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

apelio.ru SEO score

89

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

    RU

  • 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 it matches the claimed language. 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

apelio.ru

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: