4.7 sec in total
328 ms
3.5 sec
857 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 328 ms and then it took 4.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
express.hr performance score
name
value
score
weighting
Value7.5 s
1/100
10%
Value7.6 s
4/100
25%
Value11.7 s
5/100
10%
Value3,310 ms
2/100
30%
Value0.452
20/100
15%
Value19.4 s
3/100
10%
328 ms
587 ms
209 ms
319 ms
215 ms
Our browser made a total of 140 requests to load all elements on the main page. We found that 66% of them (93 requests) were addressed to the original Express.hr, 4% (5 requests) were made to Tpc.googlesyndication.com and 3% (4 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Express.hr.
Page size can be reduced by 769.3 kB (33%)
2.3 MB
1.5 MB
In fact, the total size of Express.hr main page is 2.3 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. 80% 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.1 MB which makes up the majority of the site volume.
Potential reduce by 185.7 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 185.7 kB or 77% of the original size.
Potential reduce by 18.5 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 440.8 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 440.8 kB or 55% of the original size.
Potential reduce by 124.3 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 124.3 kB or 87% of the original size.
Number of requests can be reduced by 33 (28%)
119
86
The browser has sent 119 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 29 to 1 for JavaScripts and as a result speed up the page load time.
express.hr
328 ms
www.express.hr
587 ms
grid.min.css
209 ms
style.min.css
319 ms
modernizr-2.8.3.min.js
215 ms
ad_helper.js
215 ms
xtcore.js
215 ms
jquery.min.js
35 ms
script.min.js
413 ms
jwplayer.js
320 ms
cookie_warning.js
232 ms
css
23 ms
cookie_warning.js
183 ms
analytics.js
24 ms
xgemius.js
348 ms
fbds.js
180 ms
door.js
268 ms
st.js
330 ms
gpt.js
23 ms
collect
97 ms
pubads_impl_81.js
8 ms
container.html
72 ms
1630d063e0ea01ebe3d6ddd90dced035.jpg
114 ms
9d83a2b42421fdd62cb0a42c2856a915.jpg
114 ms
07d63ba9b66d59d3706acf5aa9c87184.jpg
422 ms
4dc00179e85c5b89d96aaea4e8529514.jpg
226 ms
197b5923f706b56b487cf73d7e488d48.jpg
223 ms
bf666768d49bd972e8a09d08b4b7cfa8.jpg
115 ms
0f687ac927692547e019d1bf7e1a185c.jpg
224 ms
44376c20124e82ad83b3afc5bea1af3b.jpg
223 ms
a1dacf3778c6c28622ccf474908b910c.jpg
225 ms
3f1ad8942e1d849589b9c3b98fbfa840.jpg
319 ms
bee3c723c4a0a329bfc0516c55e8e7ca.jpg
320 ms
38aab9bb6dcafae0207b4997e83e811b.jpg
320 ms
02754aa9ae1a9e3a92456dc94df7611c.jpg
318 ms
9b2f34aa0abe8c359a7bc8d1661ab5df.jpg
323 ms
dc75b143b18ba8e603428f3bb2bd2949.jpg
423 ms
997210232955a526405991ad2ed9c790.jpg
428 ms
4c455fb260d051e4eae900d0d21fff2b.jpg
424 ms
31873faf8bad3a76ad55f8ce2aecccdf.jpg
424 ms
025735b5c310600b6074477fb51b5e9c.jpg
428 ms
c55c306454b7abce5698f97618b32b0e.jpg
541 ms
9d003b6fa3430fe64029c52d112ed83c.jpg
614 ms
9f3ab16c933ba090e98c84a797a4c82f.jpg
614 ms
c5806ea858976a7cbc22cb315b6f65bc.jpg
699 ms
2f4ac5ec2f08ffe7a254ccb9f324c914.jpg
611 ms
2b28a85d7c2c7552f73f38b986f6b3b0.jpg
612 ms
1ef004e2a2ff66298f8728c1e5cdc3a2.jpg
697 ms
f17a335ef41d8c6016246eb30ba7f127.jpg
697 ms
eec045773defa7b35ae3dfc4fb75e41b.jpg
756 ms
bacc0bed7180bdd5239b0b9cd5e83037.jpg
696 ms
4c18cf2db7193dadcf4758d5b04dfa4a.jpg
696 ms
a6efdbf18a7f63a3a8390e81bac9e858.jpg
811 ms
1661b67072e44b6c25163373f13449ec.jpg
810 ms
4aef4bb9be64c88fcbf1b35e8556d717.jpg
809 ms
bea372615dae362a3f4101b8bdcf0fe3.jpg
806 ms
84739ddd379ecfe8179122a6018ffdee.jpg
808 ms
collect
79 ms
f59022774f760688ad0d34afec53eba6.jpg
997 ms
ads
385 ms
FiraSans-Light.woff
1047 ms
FiraSans-Medium.woff
952 ms
5M21SdFLkD52QavfmHs6cA.ttf
32 ms
Pru33qjShpZSmG3z6VYwnaCWcynf_cDxXwCLxiixG1c.ttf
58 ms
97uahxiqZRoncBaCEI3aW6CWcynf_cDxXwCLxiixG1c.ttf
79 ms
9_7S_tWeGDh5Pq3u05RVkqCWcynf_cDxXwCLxiixG1c.ttf
79 ms
FiraSans-Bold.woff
1278 ms
75 ms
ga-audiences
77 ms
hit.gif
232 ms
FiraSans-Heavy.woff
1174 ms
FiraSans-Ultra.woff
936 ms
express.woff
835 ms
FiraSans-BookItalic.woff
1174 ms
FiraSans-Book.woff
1165 ms
hit.xiti
200 ms
events
117 ms
fpdata.js
117 ms
lsget.html
434 ms
30d31e67fd51a83240145867a4de0dce.jpg
1078 ms
04c280ca15090d7e5ea3ead61b35e9a9.jpg
1077 ms
fb1760eed420f332b45ed017349ec067.jpg
1079 ms
384e0ca440fd2c745312b06b86adb9ca.jpg
1218 ms
d06f868055ad70a6d84d58fb5db110b8.jpg
1076 ms
2c3d1f48c3d2db58bacf133793f6e7d9.jpg
982 ms
5eefa9e39c151f87fbde0a338234229d.jpg
976 ms
1809fe5c1a69284e4cf1ea573e57b315.jpg
1099 ms
expansion_embed.js
40 ms
17739011640194700865
177 ms
abg.js
201 ms
m_js_controller.js
211 ms
googlelogo_color_112x36dp.png
100 ms
sprite_footer-logos.png
986 ms
osd.js
75 ms
da81dd761e56c196318ac6f9d19352a7.jpg
926 ms
c2a0ec60927f62df65d11fd415bb96b1.jpg
926 ms
bb9e3d3956b91c574a77d4cb4fd1f975.jpg
927 ms
792412276f0ae5536dce441b945dc659.jpg
939 ms
3af35b3e955e0b046eac7bf2c0628deb.jpg
1034 ms
833cc533e9b6069fefb274ebc9502ddd.jpg
1033 ms
060f5e699039e917b4e6938105497304.jpg
1033 ms
track.js
952 ms
FiraSans-LightItalic.woff
998 ms
FiraSans-Italic.woff
1072 ms
FiraSans-MediumItalic.woff
1150 ms
ads
49 ms
3fe03978ab6424b4cc9b555d288a5df9.jpg
982 ms
s
58 ms
x_button_blue2.png
30 ms
24_mobiteli01_L_340x1050px.html
386 ms
24_mobiteli01_R_340x1050px.html
385 ms
1ba52b192ef5527b4ae83c58e45684dc.jpg
921 ms
ads
53 ms
itracker.gif
249 ms
a7daa155c16d9376f002666f8dbefd90.jpg
945 ms
160800b31e1e40caf76308d0138b020f.jpg
1038 ms
e032c7e178460ef43e30dca75d5bf5de.jpg
1039 ms
c503c04324ebae2870f7f804a837957e.jpg
1038 ms
688f8a3b04f168ddffc867ee70990c9a.jpg
1037 ms
script.v32.js
313 ms
rexdot.js
123 ms
runtime.js
186 ms
028da71c73eca69641209ebf65809342.jpg
872 ms
14d5fefd648f9cebd3f183957d46fdfc.jpg
872 ms
0ca3874a618a585d79bf6b164a5dd6ee.jpg
867 ms
740e063554f90d437ffc44183aeffa06.jpg
780 ms
89dd62ccf3fc8c7700e6ba4d699e398e.jpg
769 ms
SiteEvent.dotmetrics
302 ms
7976d980993254d621bc45af5437a7a2.jpg
559 ms
3ccc93be44782750739123ebd1a8d9e2.jpg
621 ms
c95db9250a4da5af54c73e622a80b4ed.jpg
607 ms
063164a3a50b73340f4e38fb552862ae.jpg
647 ms
dc10e73e7176f1598b5dce98d52153b9.jpg
647 ms
0a92854f9b137fe695af833838798835.jpg
649 ms
c2febb8223c74e98905e929c47a0d533.jpg
669 ms
916b35b66d0e825464580e4c67199e3f.jpg
710 ms
nr-885.min.js
33 ms
28 ms
ui
24 ms
7caed2fa7a
52 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
Registers an unload listener
Detected JavaScript libraries
Page has valid source maps
Issues were logged in the Issues panel in Chrome Devtools
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
EN
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 does not match the claimed English 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: