Tools & Wizards About Us
darex.rs screenshot

Report Summary

  • 0

    Performance

  • 69

    Accessibility

    Visual factors better than
    that of 34% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

darex.rs

Darex

Page Load Speed

4.5 sec in total

First Response

525 ms

Resources Loaded

3.5 sec

Page Rendered

499 ms

darex.rs screenshot

About Website

Welcome to darex.rs homepage info - get ready to check Darex best content for Serbia right away, or after learning these important things about darex.rs

Bavimo se proizvodnjom i prodajom nameštaja po meri, gotovih elemenata za namestaj, prodajom okova i pločastih materijala za namestaj.

Visit darex.rs

Key Findings

We analyzed Darex.rs page load time and found that the first response time was 525 ms and then it took 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

darex.rs performance score

0

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

23/100

10%

LCP (Largest Contentful Paint)

Value0

0/100

25%

SI (Speed Index)

Value10.4 s

8/100

10%

TBT (Total Blocking Time)

Value230 ms

86/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value13.9 s

10/100

10%

Network Requests Diagram

darex.rs

525 ms

darex.rs

744 ms

darex_landing_theme_compiled.css

349 ms

darex_theme_bootstrap_compiled.js

800 ms

darex_views_compiled.js

408 ms

Our browser made a total of 35 requests to load all elements on the main page. We found that 83% of them (29 requests) were addressed to the original Darex.rs, 9% (3 requests) were made to Google-analytics.com and 6% (2 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Darex.rs.

Page Optimization Overview & Recommendations

Page size can be reduced by 355.5 kB (19%)

Content Size

1.9 MB

After Optimization

1.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Darex.rs main page is 1.9 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. 50% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 126.8 kB

  • Original 159.1 kB
  • After minification 140.1 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. This page needs HTML code to be minified as it can gain 19.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 126.8 kB or 80% of the original size.

Image Optimization

-1%

Potential reduce by 9.4 kB

  • Original 1.1 MB
  • After minification 1.0 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. Darex images are well optimized though.

JavaScript Optimization

-40%

Potential reduce by 219.3 kB

  • Original 551.1 kB
  • After minification 546.3 kB
  • After compression 331.8 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 219.3 kB or 40% of the original size.

CSS Optimization

-0%

Potential reduce by 0 B

  • Original 149.3 kB
  • After minification 149.3 kB
  • After compression 149.3 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. Darex.rs has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 11 (42%)

Requests Now

26

After Optimization

15

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

darex.rs

darex.rs

525 ms

darex.rs

darex.rs

744 ms

darex_landing_theme_compiled.css

darex_landing_theme_compiled.css

349 ms

darex_theme_bootstrap_compiled.js

darex_theme_bootstrap_compiled.js

800 ms

darex_views_compiled.js

darex_views_compiled.js

408 ms

translations

translations

624 ms

routing

routing

685 ms

newsletter_js_compiled.js

newsletter_js_compiled.js

406 ms

darex_theme_landing_compiled.js

darex_theme_landing_compiled.js

463 ms

analytics_google_jquery_pub_sub_js_compiled.js

analytics_google_jquery_pub_sub_js_compiled.js

460 ms

analytics.js

analytics.js

28 ms

B2B-SR-72.png

B2B-SR-72.png

124 ms

B2B-MNE-72.png

B2B-MNE-72.png

124 ms

Egger-Kolekcija-24%2B.jpg

Egger-Kolekcija-24%2B.jpg

382 ms

Cleaf-1.webp

Cleaf-1.webp

556 ms

Yildiz%20oi.webp

Yildiz%20oi.webp

566 ms

Yil-MDF-Akt.jpg

Yil-MDF-Akt.jpg

549 ms

darex-logo.svg

darex-logo.svg

227 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

364 ms

Roboto-Regular.ttf

Roboto-Regular.ttf

652 ms

ec.js

ec.js

6 ms

KaushanScript-Regular.ttf

KaushanScript-Regular.ttf

502 ms

Montserrat-Regular.ttf

Montserrat-Regular.ttf

501 ms

Oswald-Regular.ttf

Oswald-Regular.ttf

588 ms

Oswald-Light.ttf

Oswald-Light.ttf

705 ms

iframe_api

iframe_api

54 ms

darex-upravna-zgrada.jpg

darex-upravna-zgrada.jpg

1295 ms

Walkway-Condensed.ttf

Walkway-Condensed.ttf

593 ms

5a040798b60c4.jpeg

5a040798b60c4.jpeg

594 ms

okov.jpg

okov.jpg

595 ms

kant-trake.jpg

kant-trake.jpg

651 ms

nas-partner.jpg

nas-partner.jpg

863 ms

www-widgetapi.js

www-widgetapi.js

58 ms

collect

collect

76 ms

js

js

63 ms

Accessibility Review

darex.rs accessibility score

69

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

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

High

Heading elements are not in a sequentially-descending order

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

darex.rs best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

darex.rs SEO score

83

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

    SR

  • Language Claimed

    SR

  • Encoding

    UTF-8

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

darex.rs

Open Graph data is detected on the main page of Darex. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: