5.6 sec in total
456 ms
4.1 sec
985 ms
Welcome to express.hr homepage info - get ready to check Express best content for Croatia right away, or after learning these important things about express.hr
Saznajte dublju stranu priče. Otkrivamo što je ispod površine
Visit express.hrWe analyzed Express.hr page load time and found that the first response time was 456 ms and then it took 5.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
express.hr performance score
name
value
score
weighting
Value5.4 s
6/100
10%
Value8.6 s
1/100
25%
Value7.8 s
23/100
10%
Value2,220 ms
6/100
30%
Value0.371
29/100
15%
Value18.4 s
3/100
10%
456 ms
657 ms
227 ms
86 ms
115 ms
Our browser made a total of 87 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Express.hr, 71% (62 requests) were made to Express.24sata.hr and 9% (8 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (2.1 sec) relates to the external source Express.24sata.hr.
Page size can be reduced by 355.4 kB (14%)
2.6 MB
2.2 MB
In fact, the total size of Express.hr main page is 2.6 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 1.5 MB which makes up the majority of the site volume.
Potential reduce by 263.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. This page needs HTML code to be minified as it can gain 55.2 kB, which is 18% 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 263.5 kB or 87% of the original size.
Potential reduce by 43.7 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. Express images are well optimized though.
Potential reduce by 20.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. This website has mostly compressed JavaScripts.
Potential reduce by 27.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. Express.hr needs all CSS files to be minified and compressed as it can save up to 27.8 kB or 30% of the original size.
Number of requests can be reduced by 16 (21%)
76
60
The browser has sent 76 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Express. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and as a result speed up the page load time.
express.hr
456 ms
express.24sata.hr
657 ms
loader.js
227 ms
css
86 ms
grid.css
115 ms
styles.2ba19861407037db17dd.css
350 ms
jquery.min.js
78 ms
ima3.js
83 ms
modernizr.custom.92546.js
336 ms
picturePolyfill.js
337 ms
sfp.js
77 ms
defractal-0-33390743-8f60-42a1-92ce-56aa08a322c9.js
89 ms
gpt.js
95 ms
sa.min.js
79 ms
common.73390bce67e3386c765a.js
634 ms
homepage.65e1cde36bca3a5f0a23.js
344 ms
sdk.e8548266da084271f144a7c3fd92d67d0f32275c.js
9 ms
upScore.js
224 ms
gtm.js
222 ms
door.js
490 ms
displays.htm
302 ms
express-logo.svg
185 ms
a11feaea279052f40e90.jpeg
418 ms
1250fa52ebad7ca441d8.jpeg
185 ms
571aca28b417e8119e16.jpeg
183 ms
9106d1789b51ca99328c.jpeg
183 ms
1ba3cac55acaaac96c16.jpeg
419 ms
8dc11bf46ba768ac9334.jpeg
418 ms
bf777ef355054172a48a.jpeg
484 ms
cd2496ce1f7366b35481.jpeg
416 ms
f5a30cc7b59391a810f0.jpeg
418 ms
9249f9c7554e62fb50db.jpeg
548 ms
7ed6cf6f2dfac6573e62.jpeg
546 ms
e54503f7f66d5db396bb.jpeg
546 ms
b2822a9706c200eb5b0e.jpeg
547 ms
012eea3b846b945bd6f0.jpeg
638 ms
8d3f1e04b1d51f13df20.jpeg
566 ms
3f204f2dece5afb2c980.jpeg
632 ms
cadcc22417eef2f3c5a2.jpeg
633 ms
15197dbf583463e1677a.jpeg
635 ms
9c687c3099ea81918a36.jpeg
639 ms
11522631b3aa1d205f1f.png
676 ms
fedb3a70065a9ec999b7.png
743 ms
c7b7181cc6d97b48b1c7.jpeg
743 ms
b4cb791c97f7327fa8e8.jpeg
746 ms
3954aab2499b1c9430e7.png
750 ms
b1f181832588f5dc35fb.jpeg
752 ms
78b5d73f5e0d0df707ce.jpeg
786 ms
e40b756138da63e53ffa.jpeg
1003 ms
92f8d473618ad51c0d19.jpeg
1004 ms
177676cdd81a937e3773.jpeg
1004 ms
c0eb17dac1c48f22fce0.jpeg
1005 ms
48284cde1e0724802c1e.jpeg
1005 ms
4afcd298f7a42405a955.jpeg
1005 ms
fb1286ae29d418d540fb.jpeg
1006 ms
pubads_impl.js
160 ms
fbbcbc7bea538c54dd98.jpeg
878 ms
u-440qyriQwlOrhSvowK_l5-ciZJ.ttf
166 ms
u-4n0qyriQwlOrhSvowK_l52xwNZVsf_.ttf
167 ms
u-4n0qyriQwlOrhSvowK_l52_wFZVsf_.ttf
283 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtzpbCGPrQ.ttf
285 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtapbCGPrQ.ttf
349 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCGPrQ.ttf
348 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCGPrQ.ttf
349 ms
37f0f36d44e90f442568.ttf
829 ms
d654f16b1a878e9272cc.jpeg
829 ms
newsletter.jpg
830 ms
5ab2dfbec29ccdb9de56.jpeg
2141 ms
BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjo0oSmYWRm.ttf
298 ms
kolumne.svg
942 ms
24sata_desk.svg
712 ms
publitzer-logo.svg
713 ms
909669b530d8bc80c201.jpeg
1909 ms
xgemius.js
575 ms
track.js
522 ms
6d286e536719c9f3310b.jpeg
1710 ms
a6296e424863c31a212b.jpeg
1707 ms
1e8b1627910fac1dc228.jpeg
1707 ms
095d527cf130da699e44.jpeg
1709 ms
561411f6e4f830cd4f45.jpeg
1707 ms
5630ef59bedd44173cb8.jpeg
1708 ms
f2c1ebcb652bfc58493d.jpeg
1710 ms
ff0ffe9c7a1dc3df6343.jpeg
1693 ms
8a2f428238dd1db2f7f6.jpeg
1692 ms
d58a7f978382e8f8ad02.jpeg
1691 ms
718e50edfa6342dea43c.jpeg
1687 ms
ui-gdpr-hr-web.e8548266da084271f144a7c3fd92d67d0f32275c.js
61 ms
express.hr accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
Image elements do not have [alt] attributes
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Some elements have a [tabindex] value greater than 0
express.hr 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
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
express.hr SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
robots.txt is not valid
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
HR
HR
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Express.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 Express.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.
express.hr
Open Graph description is not detected on the main page of Express. 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: