8.5 sec in total
873 ms
7.3 sec
361 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 873 ms and then it took 7.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
freetz.com performance score
name
value
score
weighting
Value1.0 s
100/100
10%
Value2.1 s
96/100
25%
Value1.7 s
100/100
10%
Value800 ms
36/100
30%
Value0.308
38/100
15%
Value3.9 s
89/100
10%
873 ms
23 ms
34 ms
45 ms
217 ms
Our browser made a total of 70 requests to load all elements on the main page. We found that 89% of them (62 requests) were addressed to the original Freetz.com, 4% (3 requests) were made to Fonts.googleapis.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.7 sec) relates to the external source Shore-booking-service-production.s3.amazonaws.com.
Page size can be reduced by 522.7 kB (23%)
2.3 MB
1.7 MB
In fact, the total size of Freetz.com main page is 2.3 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. 20% of websites need less resources to load. Images take 1.6 MB which makes up the majority of the site volume.
Potential reduce by 90.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. This page needs HTML code to be minified as it can gain 23.0 kB, which is 23% 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 90.7 kB or 90% of the original size.
Potential reduce by 11.8 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 394.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 394.8 kB or 76% of the original size.
Potential reduce by 25.4 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 25.4 kB or 91% of the original size.
Number of requests can be reduced by 22 (34%)
65
43
The browser has sent 65 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 17 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
freetz.com
873 ms
css
23 ms
css
34 ms
css
45 ms
google.js
217 ms
jquery-1.4.2.js
928 ms
style.css
441 ms
jquery.mousewheel-3.0.4.pack.js
227 ms
jquery.fancybox-1.3.4.pack.js
442 ms
jquery.fancybox-1.3.4.css
538 ms
style.css
439 ms
collapse.js
665 ms
jquery-ui.min.js
1421 ms
jquery.effects.fade.js
665 ms
jquery.effects.slide.js
743 ms
slideshow.js
750 ms
jquery.cycle.js
1296 ms
jquery.fullscreenr.js
879 ms
imagefade.js
958 ms
jquery.scrollTo-min.js
965 ms
mainstyle.css
997 ms
menu.js
1042 ms
ga.js
9 ms
__utm.gif
12 ms
loading.js
416 ms
jquery.cycle.all.latest.js
984 ms
background_kezdo.jpg
222 ms
background_kezdo_02.jpg
224 ms
bg-1.jpg
1090 ms
newsletter.html
215 ms
menu_hatter.jpg
218 ms
freetz.png
375 ms
home.png
413 ms
menu_tren.png
415 ms
speisekarte.png
418 ms
bilder.png
433 ms
partyservice.png
587 ms
partner.png
633 ms
vissza_nyil.png
634 ms
12515-250x300.gif
741 ms
Weingraf.jpg
651 ms
hotel-alarun.jpg
802 ms
ido-fashion.jpg
845 ms
ajax_loader.gif
855 ms
01.jpg
869 ms
02.jpg
956 ms
03.jpg
1023 ms
04.jpg
1064 ms
10.jpg
1069 ms
11.jpg
1085 ms
12.jpg
1171 ms
13.jpg
1233 ms
14.jpg
1283 ms
15.jpg
1279 ms
16.jpg
1287 ms
20.jpg
1308 ms
21.jpg
1386 ms
vonal.png
1454 ms
foodback.jpg
1602 ms
vissza_nyil2.png
1497 ms
vonal2.png
1503 ms
Irdbc4ASuUoWDjd_Wc3md0un70UYZGE2JplEpmG_-Ls.ttf
9 ms
tageskarte.png
1562 ms
telefon.png
1414 ms
bg-3.jpg
2235 ms
bg-4.jpg
2418 ms
bg-5.jpg
2405 ms
bg-6.jpg
2451 ms
bg-7.jpg
2412 ms
application-f0cc8c03d889d0ca074b5d27dbf6dd97.css
2664 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: