8.7 sec in total
1.3 sec
7.2 sec
195 ms
Click here to check amazing OTTO content for Austria. Otherwise, check out these important facts you probably never knew about otto.at
OTTO Immobilien ist Ihr erfahrener Immobilien-Dienstleister in Wien. Wir vermieten, verkaufen, verwalten, analysieren und bewerten Ihre Immobilie.
Visit otto.atWe analyzed Otto.at page load time and found that the first response time was 1.3 sec and then it took 7.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
otto.at performance score
name
value
score
weighting
Value3.1 s
47/100
10%
Value10.8 s
0/100
25%
Value5.7 s
51/100
10%
Value900 ms
31/100
30%
Value0.023
100/100
15%
Value11.4 s
19/100
10%
1290 ms
2703 ms
459 ms
369 ms
286 ms
Our browser made a total of 61 requests to load all elements on the main page. We found that 80% of them (49 requests) were addressed to the original Otto.at, 3% (2 requests) were made to Google-analytics.com and 3% (2 requests) were made to Gtrk.s3.amazonaws.com. The less responsive or slowest element that took the longest time to load (2.7 sec) belongs to the original domain Otto.at.
Page size can be reduced by 589.1 kB (43%)
1.4 MB
787.4 kB
In fact, the total size of Otto.at main page is 1.4 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. 30% of websites need less resources to load. Javascripts take 632.9 kB which makes up the majority of the site volume.
Potential reduce by 32.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 10.5 kB, which is 26% 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 32.8 kB or 81% of the original size.
Potential reduce by 34.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. OTTO images are well optimized though.
Potential reduce by 454.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 454.5 kB or 72% of the original size.
Potential reduce by 67.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. Otto.at needs all CSS files to be minified and compressed as it can save up to 67.2 kB or 83% of the original size.
Number of requests can be reduced by 29 (51%)
57
28
The browser has sent 57 CSS, Javascripts, AJAX and image requests in order to completely render the main page of OTTO. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 22 to 1 for JavaScripts and as a result speed up the page load time.
otto.at
1290 ms
www.otto.at
2703 ms
GetResource.ashx
459 ms
modernizr-2.6.2.min.js
369 ms
WebResource.axd
286 ms
ScriptResource.axd
588 ms
ScriptResource.axd
433 ms
jquery.min.js
28 ms
jquery-ui-1.9.2.custom.min.js
689 ms
hammer.min.js
305 ms
jquery.hammer.min.js
355 ms
jquery.cycle.min.js
579 ms
jquery.ui.touch-punch.min.js
480 ms
plugins.js
502 ms
commonHelper.js
479 ms
main.js
602 ms
jquery.dotdotdot-1.5.6-packed.js
604 ms
numeral.min.js
595 ms
underscore-min.js
604 ms
angular.min.js
897 ms
bulk-search.js
721 ms
GetFile.aspx
406 ms
top_objects_big_bg.png
404 ms
logo_bestemployer.png
373 ms
logo_euromoney.png
494 ms
logo_fmh.png
490 ms
logo_caesar.png
487 ms
logo_ima.png
600 ms
logo_imm.png
599 ms
logo_konsument.png
605 ms
logo_knight_frank.png
609 ms
logo_ovi.png
650 ms
logo_fiabci.png
708 ms
header_bg_img.jpg
585 ms
home_btn.png
605 ms
contactbox_btn_bg.png
605 ms
contactbox_btn_sprite.png
620 ms
contactbox_bottom.png
680 ms
otto-logo.png
737 ms
bubble_bottom_small.png
729 ms
search_icon.png
719 ms
btn_bg.png
754 ms
top_objects_big_bottom.png
740 ms
toggle_btn_sprite.png
845 ms
bubble_bottom.png
844 ms
gtm.js
62 ms
GetFile.aspx
1619 ms
GetFile.aspx
2260 ms
GetFile.aspx
974 ms
slideshow_indicator_sprite.png
439 ms
slideshow_nav_sprite.png
490 ms
conversion_async.js
16 ms
analytics.js
37 ms
6398.js
66 ms
64 ms
collect
13 ms
collect
77 ms
s
66 ms
u
54 ms
59 ms
ga-audiences
18 ms
otto.at accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
Form elements do not have associated labels
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.
otto.at 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
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
otto.at SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
DE
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Otto.at can be misinterpreted by Google and other search engines. Our service has detected that German 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 Otto.at 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.
otto.at
Open Graph description is not detected on the main page of OTTO. 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: