Tools & Wizards About Us

Report Summary

  • 25

    Performance

    Renders faster than
    44% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

nt.rs

NT Company DOO - Online Shop - Xwave, Xled, Oukitel, 4print

Page Load Speed

5.8 sec in total

First Response

316 ms

Resources Loaded

4.4 sec

Page Rendered

1 sec

About Website

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

Online Shop NT Company DOO - Prodaja brendova Xwave, Xled, Oukitel, Xprint, 4print, Xstand, Alphastar, Alpha

Visit nt.rs

Key Findings

We analyzed Nt.rs page load time and found that the first response time was 316 ms and then it took 5.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

nt.rs performance score

25

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.1 s

1/100

10%

LCP (Largest Contentful Paint)

Value15.5 s

0/100

25%

SI (Speed Index)

Value11.8 s

4/100

10%

TBT (Total Blocking Time)

Value890 ms

32/100

30%

CLS (Cumulative Layout Shift)

Value0.044

99/100

15%

TTI (Time to Interactive)

Value17.7 s

4/100

10%

Network Requests Diagram

nt.rs

316 ms

nt.rs

1997 ms

3.3.1_jquery.min.js

478 ms

bootstrap.min.css

570 ms

bootstrap.min.js

381 ms

Our browser made a total of 126 requests to load all elements on the main page. We found that 93% of them (117 requests) were addressed to the original Nt.rs, 5% (6 requests) were made to Fonts.gstatic.com and 1% (1 request) were made to Cdnjs.cloudflare.com. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Nt.rs.

Page Optimization Overview & Recommendations

Page size can be reduced by 749.1 kB (25%)

Content Size

3.0 MB

After Optimization

2.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-93%

Potential reduce by 269.9 kB

  • Original 288.7 kB
  • After minification 193.7 kB
  • After compression 18.8 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 95.0 kB, which is 33% 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 269.9 kB or 93% of the original size.

Image Optimization

-3%

Potential reduce by 62.8 kB

  • Original 2.1 MB
  • After minification 2.1 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. NT images are well optimized though.

JavaScript Optimization

-71%

Potential reduce by 174.3 kB

  • Original 244.8 kB
  • After minification 237.8 kB
  • After compression 70.5 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 174.3 kB or 71% of the original size.

CSS Optimization

-83%

Potential reduce by 242.2 kB

  • Original 292.0 kB
  • After minification 259.3 kB
  • After compression 49.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. Nt.rs needs all CSS files to be minified and compressed as it can save up to 242.2 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 19 (17%)

Requests Now

115

After Optimization

96

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

nt.rs accessibility score

81

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

Heading elements are not in a sequentially-descending order

Best Practices

nt.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

SEO Factors

nt.rs SEO score

92

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

    HR

  • Language Claimed

    SR

  • Encoding

    UTF-8

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

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