Tools & Wizards About Us
njuskalo.hr screenshot

Report Summary

  • 18

    Performance

    Renders faster than
    34% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

njuskalo.hr

Njuskalo.hr oglasnik

Page Load Speed

4.3 sec in total

First Response

346 ms

Resources Loaded

3.4 sec

Page Rendered

500 ms

njuskalo.hr screenshot

About Website

Visit njuskalo.hr now to see the best up-to-date Njuskalo content for Croatia and also check out these interesting facts you probably never knew about njuskalo.hr

Oglasnik sa više od 500.000 posjeta dnevno i više od 10.000 novih oglasa svaki dan, Njuškalo - glavna njuška među oglasnicima.

Visit njuskalo.hr

Key Findings

We analyzed Njuskalo.hr page load time and found that the first response time was 346 ms and then it took 3.9 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

njuskalo.hr performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

29/100

10%

LCP (Largest Contentful Paint)

Value20.4 s

0/100

25%

SI (Speed Index)

Value17.9 s

0/100

10%

TBT (Total Blocking Time)

Value5,770 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.024

100/100

15%

TTI (Time to Interactive)

Value37.4 s

0/100

10%

Network Requests Diagram

njuskalo.hr

346 ms

www.njuskalo.hr

764 ms

loader.js

356 ms

aperture.js

27 ms

c802f79592.css

1697 ms

Our browser made a total of 42 requests to load all elements on the main page. We found that 7% of them (3 requests) were addressed to the original Njuskalo.hr, 71% (30 requests) were made to Static.njuskalo.hr and 7% (3 requests) were made to Sdk.privacy-center.org. The less responsive or slowest element that took the longest time to load (1.7 sec) relates to the external source Static.njuskalo.hr.

Page Optimization Overview & Recommendations

Page size can be reduced by 289.1 kB (60%)

Content Size

479.2 kB

After Optimization

190.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Njuskalo.hr main page is 479.2 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. 50% of websites need less resources to load. HTML takes 246.2 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 202.0 kB

  • Original 246.2 kB
  • After minification 242.2 kB
  • After compression 44.1 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 202.0 kB or 82% of the original size.

Image Optimization

-0%

Potential reduce by 115 B

  • Original 111.7 kB
  • After minification 111.6 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. Njuskalo images are well optimized though.

JavaScript Optimization

-12%

Potential reduce by 1.1 kB

  • Original 9.3 kB
  • After minification 9.3 kB
  • After compression 8.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 1.1 kB or 12% of the original size.

CSS Optimization

-77%

Potential reduce by 85.8 kB

  • Original 112.0 kB
  • After minification 111.8 kB
  • After compression 26.2 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. Njuskalo.hr needs all CSS files to be minified and compressed as it can save up to 85.8 kB or 77% of the original size.

Requests Breakdown

Number of requests can be reduced by 23 (58%)

Requests Now

40

After Optimization

17

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

njuskalo.hr

njuskalo.hr

346 ms

www.njuskalo.hr

www.njuskalo.hr

764 ms

loader.js

loader.js

356 ms

aperture.js

aperture.js

27 ms

c802f79592.css

c802f79592.css

1697 ms

3c10507b4e.css

3c10507b4e.css

1695 ms

e79371a488.css

e79371a488.css

1696 ms

2a1117a2c7.css

2a1117a2c7.css

1701 ms

bbb4d38d7e.css

bbb4d38d7e.css

1702 ms

83d9d10b02.css

83d9d10b02.css

1703 ms

f404dd9ee5.css

f404dd9ee5.css

1702 ms

4bb60be65c.css

4bb60be65c.css

1701 ms

74fbdb2882.css

74fbdb2882.css

1703 ms

bdc993a070.css

bdc993a070.css

1703 ms

ff1bbc7965.css

ff1bbc7965.css

1703 ms

veze_2f6b288ad4.js

veze_2f6b288ad4.js

1703 ms

piano-analytics.js

piano-analytics.js

26 ms

jsdata

jsdata

37 ms

jsdata

jsdata

33 ms

2ad2ed32c3.png

2ad2ed32c3.png

1675 ms

sdk.13baec1685caf5c6eeacde774570aa8c3314ba71.js

sdk.13baec1685caf5c6eeacde774570aa8c3314ba71.js

8 ms

ui-gdpr-hr-web.13baec1685caf5c6eeacde774570aa8c3314ba71.js

ui-gdpr-hr-web.13baec1685caf5c6eeacde774570aa8c3314ba71.js

867 ms

7184815e5e.png

7184815e5e.png

205 ms

gtm.js

gtm.js

91 ms

4161e35493.png

4161e35493.png

167 ms

efdd17d7e8.svg

efdd17d7e8.svg

166 ms

7f7f7d051b.svg

7f7f7d051b.svg

169 ms

dd1d4108fa.svg

dd1d4108fa.svg

169 ms

dec1412a39.svg

dec1412a39.svg

167 ms

9a0def077d.svg

9a0def077d.svg

265 ms

7e180e3953.svg

7e180e3953.svg

268 ms

3b9035a33a.svg

3b9035a33a.svg

267 ms

442817792b.svg

442817792b.svg

270 ms

fecc9b8290.png

fecc9b8290.png

270 ms

ebac6f52af.svg

ebac6f52af.svg

270 ms

e42cc746ab.svg

e42cc746ab.svg

303 ms

00fe4607e8.svg

00fe4607e8.svg

340 ms

dfbbfbbd7a.jpg

dfbbfbbd7a.jpg

453 ms

7c3d70c6f4.jpg

7c3d70c6f4.jpg

566 ms

7ebc671ac2.png

7ebc671ac2.png

326 ms

Njuskalo-logo-crni-slogan-thumb.png

Njuskalo-logo-crni-slogan-thumb.png

117 ms

tag.js

tag.js

68 ms

Accessibility Review

njuskalo.hr accessibility score

82

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

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

njuskalo.hr best practices score

83

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

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

njuskalo.hr SEO score

91

Search Engine Optimization Advices

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

    HR

  • Language Claimed

    HR

  • Encoding

    UTF-8

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

njuskalo.hr

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