Tools & Wizards About Us
re.rs screenshot

Report Summary

  • 18

    Performance

    Renders faster than
    34% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 62% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 91

    SEO

    Google-friendlier than
    71% of websites

re.rs

RE.RS Firme Srbija | Poslovni Imenik i Adresar Srbije | Registrator

Page Load Speed

1.2 sec in total

First Response

217 ms

Resources Loaded

854 ms

Page Rendered

172 ms

re.rs screenshot

About Website

Visit re.rs now to see the best up-to-date RE content for Serbia and also check out these interesting facts you probably never knew about re.rs

Poslovni Imenik Srbije | Adresar firmi i kompanija u Beogradu, Novom Sadu, Nišu i u celoj Srbiji. Direktorijum i katalog, Firme Srbija.

Visit re.rs

Key Findings

We analyzed Re.rs page load time and found that the first response time was 217 ms and then it took 1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.

Performance Metrics

re.rs performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.8 s

2/100

10%

LCP (Largest Contentful Paint)

Value15.3 s

0/100

25%

SI (Speed Index)

Value16.3 s

0/100

10%

TBT (Total Blocking Time)

Value1,750 ms

10/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value19.3 s

2/100

10%

Network Requests Diagram

re.rs

217 ms

reset.css

193 ms

main.css

191 ms

style.css

201 ms

loopedslider.js

198 ms

Our browser made a total of 21 requests to load all elements on the main page. We found that 95% of them (20 requests) were addressed to the original Re.rs, 5% (1 request) were made to Embed.tawk.to. The less responsive or slowest element that took the longest time to load (423 ms) belongs to the original domain Re.rs.

Page Optimization Overview & Recommendations

Page size can be reduced by 325.6 kB (59%)

Content Size

555.3 kB

After Optimization

229.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Re.rs main page is 555.3 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. Only 10% of websites need less resources to load. Javascripts take 384.7 kB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 16.9 kB

  • Original 19.4 kB
  • After minification 18.1 kB
  • After compression 2.5 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 16.9 kB or 87% of the original size.

Image Optimization

-2%

Potential reduce by 3.0 kB

  • Original 137.4 kB
  • After minification 134.4 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. RE images are well optimized though.

JavaScript Optimization

-77%

Potential reduce by 294.7 kB

  • Original 384.7 kB
  • After minification 384.7 kB
  • After compression 90.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 294.7 kB or 77% of the original size.

CSS Optimization

-80%

Potential reduce by 11.0 kB

  • Original 13.8 kB
  • After minification 10.5 kB
  • After compression 2.8 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. Re.rs needs all CSS files to be minified and compressed as it can save up to 11.0 kB or 80% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

18

After Optimization

18

  • Images
  • JavaScript
  • CSS

The browser has sent 18 CSS, Javascripts, AJAX and image requests in order to completely render the main page of RE. According to our analytics all requests are already optimized.

Network Requests Diagram

re.rs

re.rs

217 ms

reset.css

reset.css

193 ms

main.css

main.css

191 ms

style.css

style.css

201 ms

loopedslider.js

loopedslider.js

198 ms

jquery-1.3.2.min.js

jquery-1.3.2.min.js

199 ms

default

default

365 ms

bg.gif

bg.gif

97 ms

logo.png

logo.png

200 ms

nav-l.gif

nav-l.gif

123 ms

nav-r.gif

nav-r.gif

114 ms

box-001.png

box-001.png

421 ms

box-01-ribbon.gif

box-01-ribbon.gif

192 ms

box-01-button.png

box-01-button.png

211 ms

box-01-twitter.gif

box-01-twitter.gif

203 ms

box-02-top.gif

box-02-top.gif

217 ms

box-02.gif

box-02.gif

281 ms

image-01.jpg

image-01.jpg

418 ms

btn-more.gif

btn-more.gif

318 ms

image-02.jpg

image-02.jpg

423 ms

box-02-bottom.gif

box-02-bottom.gif

323 ms

Accessibility Review

re.rs accessibility score

86

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

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

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

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

re.rs best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

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

re.rs SEO score

91

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

    SR

  • Language Claimed

    SR

  • Encoding

    UTF-8″

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Re.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 Re.rs main page’s claimed encoding is utf-8″. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

re.rs

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