Access wlw.hr. WLW

Report Summary

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

34/100

10%

LCP (Largest Contentful Paint)

Value3.5 s

63/100

25%

SI (Speed Index)

Value5.2 s

59/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value3.5 s

92/100

10%

wlw.hr

262 ms

www.wlw.hr

741 ms

dashicons.min.css

370 ms

buttons.min.css

290 ms

forms.min.css

259 ms

Our browser made a total of 8 requests to load all elements on the main page. We found that all of those requests were addressed to Wlw.hr and no external sources were called. The less responsive or slowest element that took the longest time to load (741 ms) belongs to the original domain Wlw.hr.

Content Size

49.5 kB

After Optimization

47.5 kB

In fact, the total size of Wlw.hr main page is 49.5 kB. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only a small number of websites need less resources to load. CSS take 46.6 kB which makes up the majority of the site volume.

HTML Optimization

-66%

Potential reduce by 1.9 kB

Original 2.9 kB
After minification 2.8 kB
After compression 991 B

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 1.9 kB or 66% of the original size.

CSS Optimization

-0%

Potential reduce by 43 B

Original 46.6 kB
After minification 46.6 kB
After compression 46.5 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. Wlw.hr has all CSS files already compressed.

Requests Now

After Optimization

The browser has sent 6 CSS, Javascripts, AJAX and image requests in order to completely render the main page of WLW. 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.

Areas of Improvement

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

Low

Detected JavaScript libraries

Search Engine Optimization Advices

To appear in search results, crawlers need access to your app.

High

Page is blocked from indexing

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/).

High

Document uses legible font sizes

Language and Encoding

Language Detected

EN
Language Claimed

HR
Encoding

UTF-8

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

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