1.1 sec in total
104 ms
765 ms
246 ms
Visit enzian.org now to see the best up-to-date Enzian content for United States and also check out these interesting facts you probably never knew about enzian.org
Enzian Theater Orlando Fl
Visit enzian.orgWe analyzed Enzian.org page load time and found that the first response time was 104 ms and then it took 1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.
enzian.org performance score
name
value
score
weighting
Value4.3 s
17/100
10%
Value21.6 s
0/100
25%
Value7.5 s
26/100
10%
Value710 ms
42/100
30%
Value0.519
15/100
15%
Value16.8 s
5/100
10%
104 ms
329 ms
10 ms
6 ms
14 ms
Our browser made a total of 50 requests to load all elements on the main page. We found that 82% of them (41 requests) were addressed to the original Enzian.org, 4% (2 requests) were made to Google-analytics.com and 4% (2 requests) were made to S.ytimg.com. The less responsive or slowest element that took the longest time to load (329 ms) belongs to the original domain Enzian.org.
Page size can be reduced by 491.8 kB (41%)
1.2 MB
709.6 kB
In fact, the total size of Enzian.org main page is 1.2 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. 45% of websites need less resources to load. Images take 572.0 kB which makes up the majority of the site volume.
Potential reduce by 13.5 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 2.8 kB, which is 16% 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 13.5 kB or 76% of the original size.
Potential reduce by 30.2 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. Enzian images are well optimized though.
Potential reduce by 217.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 217.8 kB or 65% of the original size.
Potential reduce by 230.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. Enzian.org needs all CSS files to be minified and compressed as it can save up to 230.3 kB or 83% of the original size.
Number of requests can be reduced by 20 (43%)
46
26
The browser has sent 46 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Enzian. 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 as a result speed up the page load time.
enzian.org
104 ms
www.enzian.org
329 ms
main.css
10 ms
jquery.fancybox.css
6 ms
jquery-1.3.2.min.js
14 ms
jquery.tools.min.js
7 ms
jquery.easing.1.3.js
11 ms
jquery.fancybox-1.2.1.pack.js
11 ms
misc.js
11 ms
r4JJvfrkH3M
103 ms
analytics.js
38 ms
dropShadowBG.jpg
21 ms
treeTopper.jpg
21 ms
btn-enzian-forever.gif
25 ms
navBG.png
21 ms
n_Film.gif
21 ms
n_Food.gif
22 ms
n_Friends.gif
22 ms
n_Festivals.gif
22 ms
n_About.gif
24 ms
g_logo_old.gif
23 ms
contentBG_home.jpg
25 ms
btn_play.png
25 ms
where-to-invade-next-3.jpg
28 ms
45-Years-xlarge.jpg
29 ms
SHORTSHD_OSCAR_2016.jpg
31 ms
RSTF_color-fulllogo-01_255_182.png
27 ms
brazil-1985_255_157_90.jpg
25 ms
the_quiet_man_255_157_90.jpg
29 ms
dasboot_255_157_90.jpg
29 ms
join-our-mailing-list.png
30 ms
calendar.gif
31 ms
g-callout-forever.jpg
34 ms
package-tile-for-Enzian-site.jpg
33 ms
eden_lunch_sml-web-grahic.jpg
36 ms
g_edenBar_green.gif
34 ms
s_facebook.gif
35 ms
s_twitter.gif
36 ms
s_instagram.gif
38 ms
s_youtube.gif
40 ms
g-accessible1.png
39 ms
g-accessible2.png
40 ms
bg_footer.jpg
41 ms
collect
13 ms
www-embed-player-vflZsBgOl.css
67 ms
www-embed-player.js
86 ms
yrK4EqpSRdoujKQmsJoZ5WaLgeULvcWnibQMQSxOOnM.js
43 ms
ad_status.js
40 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
79 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
91 ms
enzian.org 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 IDs are not unique
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
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
List items (<li>) are not contained within <ul> or <ol> parent elements.
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.
enzian.org 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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
enzian.org 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 Enzian.org 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 Enzian.org 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.
enzian.org
Open Graph description is not detected on the main page of Enzian. 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: