2.5 sec in total
177 ms
2 sec
268 ms
Welcome to eboxx.at homepage info - get ready to check Eboxx best content for Austria right away, or after learning these important things about eboxx.at
xoo design web solutions Österreich: Webdesign, CMS, mobile-friendly Websites, Onlineshop B2B & B2C, responsive Newsletter, eboxx® Homepage-Baukasten
Visit eboxx.atWe analyzed Eboxx.at page load time and found that the first response time was 177 ms and then it took 2.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
eboxx.at performance score
name
value
score
weighting
Value3.5 s
34/100
10%
Value3.9 s
52/100
25%
Value9.6 s
11/100
10%
Value340 ms
74/100
30%
Value0.025
100/100
15%
Value5.5 s
70/100
10%
177 ms
41 ms
101 ms
198 ms
199 ms
Our browser made a total of 61 requests to load all elements on the main page. We found that 57% of them (35 requests) were addressed to the original Eboxx.at, 13% (8 requests) were made to Apis.google.com and 8% (5 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (907 ms) belongs to the original domain Eboxx.at.
Page size can be reduced by 795.1 kB (70%)
1.1 MB
334.2 kB
In fact, the total size of Eboxx.at main page is 1.1 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. 55% of websites need less resources to load. Javascripts take 868.0 kB which makes up the majority of the site volume.
Potential reduce by 47.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 47.7 kB or 69% of the original size.
Potential reduce by 2.6 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. Obviously, Eboxx needs image optimization as it can save up to 2.6 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 597.3 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 597.3 kB or 69% of the original size.
Potential reduce by 147.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. Eboxx.at needs all CSS files to be minified and compressed as it can save up to 147.5 kB or 87% of the original size.
Number of requests can be reduced by 38 (70%)
54
16
The browser has sent 54 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Eboxx. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 34 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
eboxx-gastro
177 ms
animate.min.css
41 ms
nyroModal_xoo.css
101 ms
eboxx-frontend-framework-classes_34769.css
198 ms
font-awesome.min.css
199 ms
css
48 ms
style_142312.EBCB0503.css
204 ms
core_v2_26361.js
211 ms
jquery-1.6.4.min.js
312 ms
jquery-ui-1.8.23.custom.min.js
423 ms
jquery.nyroModal-1.5.0.min.js
295 ms
touchdevice_34051.js
296 ms
form-control_26362.js
303 ms
jquery-ui-i18n.js
308 ms
webfont.js
60 ms
translation_26363.js
393 ms
session_timeout_26364.js
394 ms
jquery.toggleevent.js
403 ms
swfobject.js
405 ms
jquery_48744.xoo.js
406 ms
eboxx-device_71373.js
489 ms
eboxx-events_48751.js
490 ms
formErrorPopup_31214.js
503 ms
text-element-vertical-align_36980.js
504 ms
item_100098.link-width.js
505 ms
main_26445.js
519 ms
xwkCreatorExtension_48259.js
587 ms
tracker_105620.js
587 ms
addthis_widget.js
29 ms
ODelI1aHBYDBqgeIAH2zlNzbP97U9sKh0jjxbPbfOKg.ttf
10 ms
toadOcfmlt9b38dHJxOBGMw1o1eFRj7wYC6JbISqOjY.ttf
13 ms
toadOcfmlt9b38dHJxOBGEMbjGELOEJD5J8DUmxkO-A.ttf
16 ms
toadOcfmlt9b38dHJxOBGNNE-IuDiR70wI4zXaKqWCM.ttf
17 ms
toadOcfmlt9b38dHJxOBGLsbIrGiHa6JIepkyt5c0A0.ttf
16 ms
afe1_8039c0c57d.png
106 ms
menu_seperator_26437.png
109 ms
home_inactive_26435.png
107 ms
shadow_header_26433.png
106 ms
120d8_292ceea240.gif
907 ms
Logo.png
107 ms
shadow_footer_26434.png
231 ms
search_button_inactive_26439.png
232 ms
analytics.js
51 ms
popOutMenu.js
155 ms
megamenu.js
156 ms
300lo.json
55 ms
plusone.js
49 ms
sh.8e5f85691f9aaa082472a194.html
36 ms
collect
24 ms
collect
63 ms
cb=gapi.loaded_0
34 ms
cb=gapi.loaded_1
32 ms
fastbutton
101 ms
postmessageRelay
62 ms
cb=gapi.loaded_0
19 ms
cb=gapi.loaded_1
14 ms
3193398744-postmessagerelay.js
20 ms
rpc:shindig_random.js
35 ms
pixel
26 ms
pixel
21 ms
cb=gapi.loaded_0
3 ms
eboxx.at 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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Links do not have a discernible name
eboxx.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
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
eboxx.at SEO score
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 Eboxx.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 Eboxx.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.
eboxx.at
Open Graph description is not detected on the main page of Eboxx. 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: