5.1 sec in total
345 ms
4.3 sec
504 ms
Visit oe4.com now to see the best up-to-date Oe 4 content for Austria and also check out these interesting facts you probably never knew about oe4.com
Log into Facebook to start sharing and connecting with your friends, family, and people you know.
Visit oe4.comWe analyzed Oe4.com page load time and found that the first response time was 345 ms and then it took 4.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
oe4.com performance score
name
value
score
weighting
Value4.1 s
20/100
10%
Value4.4 s
40/100
25%
Value4.1 s
78/100
10%
Value0 ms
100/100
30%
Value0.026
100/100
15%
Value4.1 s
86/100
10%
345 ms
1073 ms
223 ms
31 ms
16 ms
Our browser made a total of 195 requests to load all elements on the main page. We found that 19% of them (38 requests) were addressed to the original Oe4.com, 9% (18 requests) were made to Rtb-csync.smartadserver.com and 9% (18 requests) were made to Tpc.googlesyndication.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Oe4.com.
Page size can be reduced by 445.8 kB (24%)
1.9 MB
1.4 MB
In fact, the total size of Oe4.com main page is 1.9 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. 70% of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 40.8 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 8.8 kB, which is 17% 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 40.8 kB or 81% of the original size.
Potential reduce by 32.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. Oe 4 images are well optimized though.
Potential reduce by 189.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 189.5 kB or 60% of the original size.
Potential reduce by 183.1 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. Oe4.com needs all CSS files to be minified and compressed as it can save up to 183.1 kB or 86% of the original size.
Number of requests can be reduced by 122 (71%)
171
49
The browser has sent 171 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Oe 4. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 39 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
oe4.com
345 ms
www.oe4.com
1073 ms
bootstrap.css
223 ms
css
31 ms
font-awesome.css
16 ms
style.css
217 ms
datepicker3.css
208 ms
jquery.stickyHeaders.css
243 ms
jquery-2.1.1.min.js
19 ms
bootstrap.min.js
17 ms
bootstrap-datepicker.js
282 ms
jquery.stickyHeaders.js
281 ms
bootstrap-datepicker.de.js
304 ms
postscribe.min.js
305 ms
adition.js
288 ms
PageLoader.js
317 ms
ContentManager.js
318 ms
jquery.touchSwipe.min.js
319 ms
jquery.Slider.js
321 ms
frontend.js
397 ms
facebook.js
398 ms
config.js
173 ms
gw.js
178 ms
smart.js
162 ms
sdk.js
184 ms
logo-backend.gif
132 ms
social-facebook.png
133 ms
social-instagram.png
134 ms
oe4-pic0047.home.0x39x1200x764.jpg
838 ms
oe4-pic0019.home.328x66x861x548.jpg
287 ms
oe4-pic0005.home.2x25x1198x764.jpg
837 ms
oe4-pic0021.home.102x20x945x602.jpg
464 ms
oe4-pic0003.home.43x27x972x619.jpg
470 ms
133706-1003836048.itemEvent.jpg
529 ms
083739-1356582462.itemEvent.jpg
581 ms
211932-1828014959.itemEvent.jpg
468 ms
001253-1400549839.itemEvent.jpg
530 ms
215950-1549997274.itemEvent.jpg
645 ms
151016-1088740494.itemEvent.jpg
849 ms
033921-184606730.itemEvent.jpg
653 ms
012202-593138198.itemEvent.jpg
938 ms
uid.html
137 ms
pql
18 ms
mainbox-arrow.png
810 ms
mainbox-divider.png
845 ms
box-dark-bg.png
925 ms
banderole-events.png
928 ms
C6HYlRF50SGJq1XyXj04z9Od4RnLmtUrdSQkDmC5b8k.woff
143 ms
-g5pDUSRgvxvOl5u-a_WHw.woff
144 ms
DXI1ORHCpsQm3Vp6mXoaTXhCUOGz7vYGh680lGh-uXM.woff
144 ms
fontawesome-webfont.woff
18 ms
searchbox-bg.png
819 ms
background-rightbar.png
820 ms
ac
267 ms
595517023.js
264 ms
ga.js
78 ms
__utm.gif
64 ms
64 ms
show0.asp
89 ms
show0.asp
203 ms
show0.asp
206 ms
show0.asp
201 ms
show0.asp
200 ms
aip
201 ms
aip
197 ms
aip
403 ms
collect
73 ms
xd_arbiter.php
134 ms
xd_arbiter.php
440 ms
CookieSync.html
13 ms
cn
311 ms
jsinfo.asp
309 ms
quant.js
16 ms
CookieSync.min.js
15 ms
sync
16 ms
pixel.htm
45 ms
usermatch
28 ms
pixelpush
25 ms
p68r
197 ms
generic
28 ms
pixel
195 ms
usermatch
53 ms
183 ms
generic
53 ms
184 ms
pixel;r=711152657;a=p-T1nhLcmCjVzQS;fpan=1;fpa=P0-864731361-1458133721247;ns=1;ce=1;cm=;je=0;sr=1024x768x32;enc=n;dst=0;et=1458133721246;tzo=-180;ref=http%3A%2F%2Fwww.oe4.com%2F;url=http%3A%2F%2Fcdn1.smartadserver.com%2Fdiff%2Frtb%2Fcsync%2FCookieSync.html%3Fnwid%3D1003%26dcid%3D4;ogl=
76 ms
ddc.htm
106 ms
gr
104 ms
casale
98 ms
cs
143 ms
194 ms
casale
125 ms
193 ms
pixel
184 ms
pixel.gif
377 ms
show_ads.js
130 ms
cn
261 ms
cn
361 ms
cn
357 ms
cn
360 ms
169 ms
169 ms
204 ms
Pug
168 ms
rtset
189 ms
rum
172 ms
u.php
172 ms
um
334 ms
pixel
166 ms
190 ms
rum
172 ms
pixel
483 ms
pixel
172 ms
crum
157 ms
crum
711 ms
crum
250 ms
ca-pub-5921205025042567.js
556 ms
zrt_lookup.html
560 ms
show_ads_impl.js
313 ms
bd
506 ms
match
367 ms
tap.php
352 ms
sd
178 ms
merge
176 ms
xrefid.xgi
348 ms
mapuser
168 ms
crum
335 ms
pixel
338 ms
sync
338 ms
lr.gif
328 ms
211 ms
274 ms
sync
266 ms
usermatch
263 ms
pixelpush
184 ms
generic
180 ms
pixel;r=56855315;a=p-T1nhLcmCjVzQS;fpan=0;fpa=P0-864731361-1458133721247;ns=1;ce=1;cm=;je=0;sr=1024x768x32;enc=n;dst=0;et=1458133721614;tzo=-180;ref=http%3A%2F%2Fwww.oe4.com%2F;url=http%3A%2F%2Fcdn1.smartadserver.com%2Fdiff%2Frtb%2Fcsync%2FCookieSync.html%3Fnwid%3D1003%26dcid%3D4;ogl=
267 ms
pixel;r=1086896984;a=p-T1nhLcmCjVzQS;fpan=0;fpa=P0-864731361-1458133721247;ns=1;ce=1;cm=;je=0;sr=1024x768x32;enc=n;dst=0;et=1458133721626;tzo=-180;ref=http%3A%2F%2Fwww.oe4.com%2F;url=http%3A%2F%2Fcdn1.smartadserver.com%2Fdiff%2Frtb%2Fcsync%2FCookieSync.html%3Fnwid%3D1003%26dcid%3D4;ogl=
260 ms
pixel;r=1028075734;a=p-T1nhLcmCjVzQS;fpan=0;fpa=P0-864731361-1458133721247;ns=1;ce=1;cm=;je=0;sr=1024x768x32;enc=n;dst=0;et=1458133721630;tzo=-180;ref=http%3A%2F%2Fwww.oe4.com%2F;url=http%3A%2F%2Fcdn1.smartadserver.com%2Fdiff%2Frtb%2Fcsync%2FCookieSync.html%3Fnwid%3D1003%26dcid%3D4;ogl=
258 ms
pixel;r=2100990122;a=p-T1nhLcmCjVzQS;fpan=0;fpa=P0-864731361-1458133721247;ns=1;ce=1;cm=;je=0;sr=1024x768x32;enc=n;dst=0;et=1458133721634;tzo=-180;ref=http%3A%2F%2Fwww.oe4.com%2F;url=http%3A%2F%2Fcdn1.smartadserver.com%2Fdiff%2Frtb%2Fcsync%2FCookieSync.html%3Fnwid%3D1003%26dcid%3D4;ogl=
254 ms
bd
311 ms
pixel.gif
342 ms
crum
191 ms
221 ms
Vula2cAoJWAAAaG7gkQAAABE%26637
335 ms
GenericUserSync.ashx
272 ms
235 ms
233 ms
ads
468 ms
157 ms
154 ms
153 ms
159 ms
osd.js
162 ms
ads
416 ms
NAX4487806012560695974
191 ms
ads
320 ms
107 ms
m
128 ms
rum
85 ms
rum
161 ms
rum
67 ms
rum
144 ms
rum
148 ms
crum
22 ms
abg.js
78 ms
googlelogo_color_112x36dp.png
325 ms
xcitedoppeltspasscad300x250.html
160 ms
m_js_controller.js
145 ms
13969150408891013210
306 ms
16039671711083240943
211 ms
s
70 ms
push
141 ms
redir.html
223 ms
x_button_blue2.png
81 ms
redir.html
245 ms
exitapi-impl.js
130 ms
addata.js
128 ms
edge.6.0.0.min.js
137 ms
m
157 ms
xcitedoppeltspasscad300x250_edge.js
37 ms
blank.png
35 ms
iframe.html
43 ms
xcitedoppeltspasscad300x250_edge.js
26 ms
fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js
73 ms
pixel
51 ms
iframe.html
86 ms
bg.jpg
75 ms
title.png
47 ms
device.png
107 ms
info.png
107 ms
stoerer.png
109 ms
btn.png
108 ms
xd_arbiter.php
108 ms
ui
28 ms
oe4.com 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-*] attributes do not match their roles
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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.
oe4.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Browser errors were logged to the console
oe4.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Page is blocked from indexing
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
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Oe4.com can be misinterpreted by Google and other search engines. Our service has detected that English 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 Oe4.com 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.
oe4.com
Open Graph description is not detected on the main page of Oe 4. 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: