2.5 sec in total
225 ms
1.9 sec
348 ms
Welcome to freetz.com homepage info - get ready to check Freetz best content right away, or after learning these important things about freetz.com
Das Restaurant Freetz in Unterschleißheim bei München bietet Ihnen köstliche Mediterranèe und internationale Spezialitäten.
Visit freetz.comWe analyzed Freetz.com page load time and found that the first response time was 225 ms and then it took 2.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
freetz.com performance score
name
value
score
weighting
Value0.8 s
100/100
10%
Value0.8 s
100/100
25%
Value0.8 s
100/100
10%
Value10 ms
100/100
30%
Value0.313
37/100
15%
Value1.8 s
100/100
10%
225 ms
97 ms
184 ms
191 ms
189 ms
Our browser made a total of 71 requests to load all elements on the main page. We found that 89% of them (63 requests) were addressed to the original Freetz.com, 4% (3 requests) were made to Booking-widget.shore-cdn.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (808 ms) belongs to the original domain Freetz.com.
Page size can be reduced by 70.3 kB (4%)
1.8 MB
1.7 MB
In fact, the total size of Freetz.com main page is 1.8 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. 40% of websites need less resources to load. Images take 1.6 MB which makes up the majority of the site volume.
Potential reduce by 26.6 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 4.4 kB, which is 13% 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 26.6 kB or 79% of the original size.
Potential reduce by 10.3 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. Freetz images are well optimized though.
Potential reduce by 30.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 30.0 kB or 19% of the original size.
Potential reduce by 3.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. Freetz.com needs all CSS files to be minified and compressed as it can save up to 3.5 kB or 53% of the original size.
Number of requests can be reduced by 20 (34%)
59
39
The browser has sent 59 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Freetz. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
freetz.com
225 ms
fonts
97 ms
fonts
184 ms
fonts
191 ms
google.js
189 ms
jquery-1.4.2.js
391 ms
style.css
192 ms
jquery.mousewheel-3.0.4.pack.js
198 ms
jquery.fancybox-1.3.4.pack.js
274 ms
jquery.fancybox-1.3.4.css
284 ms
style.css
284 ms
collapse.js
286 ms
jquery-ui.min.js
501 ms
jquery.effects.fade.js
365 ms
jquery.effects.slide.js
379 ms
slideshow.js
379 ms
jquery.cycle.js
384 ms
jquery.fullscreenr.js
455 ms
imagefade.js
472 ms
jquery.scrollTo-min.js
475 ms
mainstyle.css
479 ms
menu.js
485 ms
loading.js
386 ms
jquery.cycle.all.latest.js
548 ms
474 ms
390 ms
387 ms
production-loading.js
423 ms
ga.js
24 ms
background_kezdo.jpg
96 ms
background_kezdo_02.jpg
97 ms
bg-1.jpg
298 ms
freetz.png
97 ms
home.png
95 ms
menu_tren.png
92 ms
speisekarte.png
183 ms
bilder.png
189 ms
partyservice.png
189 ms
partner.png
191 ms
vissza_nyil.png
191 ms
12515-250x300.gif
272 ms
hotel-alarun.jpg
284 ms
ajax_loader.gif
284 ms
01.jpg
286 ms
02.jpg
287 ms
03.jpg
362 ms
04.jpg
377 ms
10.jpg
378 ms
11.jpg
380 ms
12.jpg
382 ms
13.jpg
395 ms
14.jpg
453 ms
15.jpg
473 ms
16.jpg
473 ms
20.jpg
475 ms
21.jpg
478 ms
vonal.png
493 ms
takeaway.png
542 ms
embed
239 ms
newsletter.html
566 ms
__utm.gif
15 ms
menu_hatter.jpg
531 ms
telefon.png
533 ms
bg-3.jpg
632 ms
bg-4.jpg
466 ms
bg-5.jpg
675 ms
bg-6.jpg
808 ms
bg-7.jpg
759 ms
js
59 ms
application.css
5 ms
application.css
3 ms
freetz.com 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.
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.
freetz.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
Page has valid source maps
freetz.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
N/A
EN
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Freetz.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Freetz.com main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
freetz.com
Open Graph description is not detected on the main page of Freetz. 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: