13.8 sec in total
501 ms
12.6 sec
730 ms
Click here to check amazing Grafenegg content for Austria. Otherwise, check out these important facts you probably never knew about grafenegg.com
Einzigartiges Ambiente, märchenfaftes Schloss, idyllischer Park – Grafenegg: Kulisse für unvergessliche Konzerte inmitten der Natur.
Visit grafenegg.comWe analyzed Grafenegg.com page load time and found that the first response time was 501 ms and then it took 13.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
grafenegg.com performance score
name
value
score
weighting
Value7.1 s
1/100
10%
Value12.4 s
0/100
25%
Value13.4 s
2/100
10%
Value1,140 ms
22/100
30%
Value0.477
18/100
15%
Value29.6 s
0/100
10%
501 ms
8684 ms
314 ms
210 ms
212 ms
Our browser made a total of 95 requests to load all elements on the main page. We found that 95% of them (90 requests) were addressed to the original Grafenegg.com, 3% (3 requests) were made to Google-analytics.com and 1% (1 request) were made to Stats.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (8.7 sec) belongs to the original domain Grafenegg.com.
Page size can be reduced by 357.0 kB (23%)
1.6 MB
1.2 MB
In fact, the total size of Grafenegg.com main page is 1.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. 60% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 310.1 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 107.4 kB, which is 32% 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 310.1 kB or 94% of the original size.
Potential reduce by 14.9 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. Grafenegg images are well optimized though.
Potential reduce by 32.0 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 32.0 kB or 60% of the original size.
Number of requests can be reduced by 15 (17%)
86
71
The browser has sent 86 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Grafenegg. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
grafenegg.com
501 ms
en
8684 ms
base-cachekey-9a6077e853d8ddb96d5df20f8f5cda7a.css
314 ms
resourceplone.app.jquerytools.dateinput-cachekey-1d115bbc08b01795a8289f4a8ac50ed8.css
210 ms
collage-cachekey-3dc4c0621ccf76c96a67099d7d93a989.css
212 ms
resourcecollective.blogging.staticblogging-cachekey-ad9ddb25dcb75a142ed50e19d498e034.css
213 ms
resourcenoeku-audio-cachekey-7c1d0698160da3721655e88d9119766d.css
213 ms
themewireframebower_componentsbootstrapdistcssbootstrap.min-cachekey-f6de33e61615f1a9cee0fc8e150f8509.css
523 ms
themewireframebower_componentsflexsliderflexslider-cachekey-effe8bdd967409810fac44cd279f9cd7.css
630 ms
resourcenoeku.grafeneggtheme.fontsfonts-cachekey-13ccf3fe2b3d81c2c42d954cd7cf4626.css
539 ms
resourceplone.app.jquery-cachekey-4784132ab9a51ad45f23ced5f31c3914.js
738 ms
nodeutilities-cachekey-ed2dbac8e7976aa7803aac003d8d89b9.js
515 ms
themewireframebower_componentsjquery-uiuiminifiedwidget.min-cachekey-8199a0e84c30b5094c631309ee4a046c.js
729 ms
themewireframebower_componentsjquery-uiuiminifiedi18ndatepicker-en-GB.min-cachekey-948bf9c83c8a35cc1c2163f69b9c290c.js
620 ms
themewireframestaticjsvendorjquery.customSelect-cachekey-096804bf93ef04219e3827843572f8e7.js
625 ms
themewireframestaticjsmorphingButton-cachekey-4634e94b9643a874a70f3e3824d18092.js
848 ms
jsi18n
129 ms
the-line.png
261 ms
grafenegg-logo-2-en.png
265 ms
logo.png
268 ms
image_preview
266 ms
image_preview
261 ms
image_preview
262 ms
image_preview
416 ms
image_preview
264 ms
image_preview
283 ms
image_preview
335 ms
image_preview
336 ms
image_preview
334 ms
image_preview
358 ms
image_preview
399 ms
image_preview
439 ms
image_preview
443 ms
image_preview
436 ms
image_preview
455 ms
image_preview
486 ms
image_preview
520 ms
image_preview
541 ms
image_preview
542 ms
image_preview
546 ms
image_preview
558 ms
image_preview
590 ms
image_preview
623 ms
image_preview
644 ms
image_preview
645 ms
image_preview
647 ms
image_preview
663 ms
image_preview
694 ms
image_preview
726 ms
image_preview
748 ms
image_preview
749 ms
cart-info
755 ms
ko152.woff
829 ms
analytics.js
167 ms
ko154.woff
742 ms
glyphicons-halflings-regular.woff
572 ms
image_preview
636 ms
image_preview
637 ms
image_preview
638 ms
image_mini
738 ms
ko354.woff
835 ms
ecommerce.js
9 ms
collect
16 ms
glyphicons-social-regular.woff
721 ms
collect
99 ms
flexslider-icon.woff
670 ms
image_mini
670 ms
image_mini
746 ms
image_mini
708 ms
image_mini
825 ms
image_mini
693 ms
image_preview
669 ms
image_preview
789 ms
image_preview
786 ms
image_preview
778 ms
image_preview
747 ms
image_preview
716 ms
image_preview
694 ms
image_preview
705 ms
image_preview
723 ms
image_preview
716 ms
noe-kultur.png
700 ms
h1-bg.png
670 ms
spinner.gif
676 ms
white.gif
707 ms
flexslider-control-nav-background-active.png
727 ms
flexslider-control-nav-background.png
716 ms
bg_direction_nav_big.png
700 ms
ui-bg_glass_75_ffffff_1x400.png
672 ms
image_hero
777 ms
image_hero
1019 ms
image_hero
807 ms
image_hero
938 ms
image_hero
811 ms
widgets.js
137 ms
grafenegg.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
[aria-hidden="true"] elements contain focusable descendents
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
[aria-*] attributes do not have valid values
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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
grafenegg.com 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
Page has valid source maps
grafenegg.com SEO score
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
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Grafenegg.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 Grafenegg.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.
grafenegg.com
Open Graph description is not detected on the main page of Grafenegg. 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: