Tools & Wizards About Us
dimex.ws screenshot

Report Summary

  • 29

    Performance

    Renders faster than
    49% of other websites

  • 49

    Accessibility

    Visual factors better than
    that of 20% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 80

    SEO

    Google-friendlier than
    42% of websites

dimex.ws

Курьерская служба доставки Даймэкс | Экспресс доставка по России, СНГ, миру

Page Load Speed

4 sec in total

First Response

352 ms

Resources Loaded

3.1 sec

Page Rendered

508 ms

dimex.ws screenshot

About Website

Visit dimex.ws now to see the best up-to-date Dimex content for Kazakhstan and also check out these interesting facts you probably never knew about dimex.ws

Экспресс доставка грузов и документов для интернет-магазинов, организаций и частных лиц по России, СНГ и зарубеж. Посчитать стоимость доставки, оформить заказ онлайн, заказать звонок в курьерскую служ...

Visit dimex.ws

Key Findings

We analyzed Dimex.ws page load time and found that the first response time was 352 ms and then it took 3.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

dimex.ws performance score

29

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.8 s

5/100

10%

LCP (Largest Contentful Paint)

Value7.7 s

3/100

25%

SI (Speed Index)

Value7.2 s

30/100

10%

TBT (Total Blocking Time)

Value750 ms

39/100

30%

CLS (Cumulative Layout Shift)

Value0.156

74/100

15%

TTI (Time to Interactive)

Value10.8 s

22/100

10%

Network Requests Diagram

dimex.ws

352 ms

dimex.ws

826 ms

bootstrap.min.css

240 ms

all.css

346 ms

animated-slider.css

357 ms

Our browser made a total of 70 requests to load all elements on the main page. We found that 81% of them (57 requests) were addressed to the original Dimex.ws, 6% (4 requests) were made to Cdn.jsdelivr.net and 3% (2 requests) were made to Calc.dimex.ws. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Dimex.ws.

Page Optimization Overview & Recommendations

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

Content Size

2.1 MB

After Optimization

1.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Dimex.ws main page is 2.1 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 1.7 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 70.7 kB

  • Original 85.1 kB
  • After minification 75.1 kB
  • After compression 14.4 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 10.0 kB, which is 12% 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 70.7 kB or 83% of the original size.

Image Optimization

-10%

Potential reduce by 166.2 kB

  • Original 1.7 MB
  • After minification 1.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. Dimex images are well optimized though.

JavaScript Optimization

-17%

Potential reduce by 48.1 kB

  • Original 286.4 kB
  • After minification 286.4 kB
  • After compression 238.2 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.1 kB or 17% of the original size.

CSS Optimization

-6%

Potential reduce by 3.8 kB

  • Original 63.3 kB
  • After minification 63.3 kB
  • After compression 59.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. Dimex.ws has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 31 (50%)

Requests Now

62

After Optimization

31

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

dimex.ws

dimex.ws

352 ms

dimex.ws

dimex.ws

826 ms

bootstrap.min.css

bootstrap.min.css

240 ms

all.css

all.css

346 ms

animated-slider.css

animated-slider.css

357 ms

gijgo.min.css

gijgo.min.css

359 ms

jquery-ui.css

jquery-ui.css

363 ms

select2.min.css

select2.min.css

365 ms

jquery.fancybox.min.css

jquery.fancybox.min.css

367 ms

style.css

style.css

461 ms

jquery-3.3.1.min.js

jquery-3.3.1.min.js

595 ms

bootstrap.min.js

bootstrap.min.js

477 ms

jquery.sequence-min.js

jquery.sequence-min.js

475 ms

jquery.fancybox.min.js

jquery.fancybox.min.js

614 ms

gijgo.min.js

gijgo.min.js

482 ms

messages.ru-ru.js

messages.ru-ru.js

575 ms

select2.full.min.js

select2.full.min.js

714 ms

ru.js

ru.js

625 ms

jquery.autocomplete.min.js

jquery.autocomplete.min.js

626 ms

jquery-ui.js

jquery-ui.js

929 ms

s3Capcha.js

s3Capcha.js

711 ms

custom.js

custom.js

713 ms

watch.js

watch.js

0 ms

banner_mob_av.jpg

banner_mob_av.jpg

827 ms

banner_mob_mn.jpg

banner_mob_mn.jpg

707 ms

bgt2.png

bgt2.png

237 ms

bgt.png

bgt.png

136 ms

logo.png

logo.png

137 ms

2326_297.png

2326_297.png

137 ms

2326_295.png

2326_295.png

139 ms

2327_295.png

2327_295.png

137 ms

2326_205.png

2326_205.png

233 ms

2327_205.png

2327_205.png

240 ms

2326_203.png

2326_203.png

238 ms

2327_203.png

2327_203.png

240 ms

1.png

1.png

952 ms

rus.png

rus.png

348 ms

abh.png

abh.png

354 ms

arm.png

arm.png

356 ms

bel.png

bel.png

356 ms

geo.png

geo.png

357 ms

est.png

est.png

463 ms

kaz.png

kaz.png

472 ms

kir.png

kir.png

595 ms

ukr.png

ukr.png

473 ms

uzb.png

uzb.png

474 ms

min.php

min.php

553 ms

bgt3.png

bgt3.png

564 ms

shadow1.png

shadow1.png

567 ms

2321_300.png

2321_300.png

804 ms

2321_297.png

2321_297.png

689 ms

2321_295.png

2321_295.png

794 ms

2321_205.jpg

2321_205.jpg

921 ms

2321_203.jpg

2321_203.jpg

926 ms

bgt4.png

bgt4.png

807 ms

bgb.png

bgb.png

867 ms

fa-solid-900.woff

fa-solid-900.woff

1012 ms

fa-regular-400.woff

fa-regular-400.woff

886 ms

ga.js

ga.js

38 ms

fbevents.js

fbevents.js

61 ms

fa-brands-400.woff

fa-brands-400.woff

964 ms

__utm.gif

__utm.gif

55 ms

collect

collect

29 ms

ga-audiences

ga-audiences

82 ms

bootstrap.min.css

bootstrap.min.css

30 ms

jquery.min.js

jquery.min.js

47 ms

popper.min.js

popper.min.js

55 ms

bootstrap.min.js

bootstrap.min.js

59 ms

bootstrap-autocomplete.min.js

bootstrap-autocomplete.min.js

59 ms

calc_min.js

calc_min.js

119 ms

Accessibility Review

dimex.ws accessibility score

49

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

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.

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 IDs are not unique

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

dimex.ws 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

Missing source maps for large first-party JavaScript

SEO Factors

dimex.ws SEO score

80

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

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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 Dimex.ws 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 Dimex.ws 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

dimex.ws

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