7.4 sec in total
1.1 sec
6 sec
323 ms
Visit nbs.rs now to see the best up-to-date Nbs content for Serbia and also check out these interesting facts you probably never knew about nbs.rs
У жељи да унапреди комуникацију са стручном јавношћу и грађанима Републике Србије, НБС на својим налозима на друштвеним мрежама објављује најважније садржаје и информације које су у вези с функцијама ...
Visit nbs.rsWe analyzed Nbs.rs page load time and found that the first response time was 1.1 sec and then it took 6.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
nbs.rs performance score
name
value
score
weighting
Value10.7 s
0/100
10%
Value15.6 s
0/100
25%
Value13.3 s
2/100
10%
Value200 ms
89/100
30%
Value0.001
100/100
15%
Value14.6 s
8/100
10%
1073 ms
811 ms
117 ms
43 ms
47 ms
Our browser made a total of 25 requests to load all elements on the main page. We found that 64% of them (16 requests) were addressed to the original Nbs.rs, 16% (4 requests) were made to Cdnjs.cloudflare.com and 8% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2.5 sec) belongs to the original domain Nbs.rs.
Page size can be reduced by 1.2 MB (43%)
2.7 MB
1.6 MB
In fact, the total size of Nbs.rs main page is 2.7 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.3 MB which makes up the majority of the site volume.
Potential reduce by 157.6 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 24.3 kB, which is 13% 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 157.6 kB or 86% of the original size.
Potential reduce by 19.2 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. Nbs images are well optimized though.
Potential reduce by 723.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 723.2 kB or 74% of the original size.
Potential reduce by 272.0 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. Nbs.rs needs all CSS files to be minified and compressed as it can save up to 272.0 kB or 88% of the original size.
Number of requests can be reduced by 4 (21%)
19
15
The browser has sent 19 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Nbs. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 5 to 1 for CSS and as a result speed up the page load time.
1073 ms
sitenew.css
811 ms
689c311ae2.js
117 ms
all.min.css
43 ms
css
47 ms
sitenew1.css
817 ms
newjs.js
2498 ms
css
20 ms
meni_foto.svg
1751 ms
ips_logo.svg
974 ms
header.jpg
486 ms
logo_e.svg
938 ms
czp.jpg
621 ms
dina3.jpg
384 ms
tvoj_novac2.jpg
1054 ms
ips.jpg
621 ms
logo_footer.svg
614 ms
6aez4K2oVqwIvtU2Gg.ttf
111 ms
6ae84K2oVqwItm4TCpAy3w.ttf
113 ms
fa-solid-900.ttf
88 ms
fa-regular-400.ttf
89 ms
kp3.jpg
641 ms
kp3s.jpg
656 ms
Indikativni_Kurs_20.html
646 ms
fa-brands-400.ttf
83 ms
nbs.rs accessibility score
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
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
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
<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
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
nbs.rs best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
Issues were logged in the Issues panel in Chrome Devtools
nbs.rs SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
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
Document uses legible font sizes
Tap targets are not sized appropriately
BS
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Nbs.rs can be misinterpreted by Google and other search engines. Our service has detected that 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 Nbs.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.
nbs.rs
Open Graph data is detected on the main page of Nbs. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: