7.1 sec in total
1.9 sec
4.9 sec
352 ms
Click here to check amazing Frannz content. Otherwise, check out these important facts you probably never knew about frannz.de
Der frannz Club im Herzen der Kulturbrauerei im Prenzlauer Berg mit Biergarten und Restaurant bietet Partys, Konzerte, Lesungen, Cocktails und warme Speisen
Visit frannz.deWe analyzed Frannz.de page load time and found that the first response time was 1.9 sec and then it took 5.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
frannz.de performance score
name
value
score
weighting
Value4.1 s
21/100
10%
Value12.2 s
0/100
25%
Value7.9 s
23/100
10%
Value270 ms
82/100
30%
Value0.034
100/100
15%
Value12.6 s
14/100
10%
1907 ms
340 ms
21 ms
337 ms
80 ms
Our browser made a total of 69 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Frannz.de, 49% (34 requests) were made to Frannz.com and 17% (12 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Frannz.de.
Page size can be reduced by 420.0 kB (19%)
2.2 MB
1.8 MB
In fact, the total size of Frannz.de main page is 2.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. 50% of websites need less resources to load. Images take 1.8 MB which makes up the majority of the site volume.
Potential reduce by 34.8 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 10.6 kB, which is 25% 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 34.8 kB or 81% of the original size.
Potential reduce by 136.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. Frannz images are well optimized though.
Potential reduce by 192.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 192.0 kB or 61% of the original size.
Potential reduce by 56.9 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. Frannz.de needs all CSS files to be minified and compressed as it can save up to 56.9 kB or 83% of the original size.
Number of requests can be reduced by 38 (56%)
68
30
The browser has sent 68 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Frannz. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 22 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
frannz.de
1907 ms
style.css
340 ms
jquery-ui.css
21 ms
thickbox.css
337 ms
jquery-1.5.2.min.js
80 ms
6621fbd6-77f9-449c-8e74-6f2dc3acd05b.js
65 ms
jquery-ui.min.js
44 ms
ui.selectmenu.js
321 ms
colorbox.css
322 ms
jquery.colorbox.js
320 ms
styles.css
325 ms
jquery.fancybox-1.3.4.css
419 ms
jquery.js
525 ms
jquery-migrate.min.js
432 ms
jquery.fancybox-1.3.4.js
430 ms
front.js
430 ms
all.js
268 ms
jquery.form.min.js
435 ms
scripts.js
509 ms
wp-embed.min.js
558 ms
wp-emoji-release.min.js
180 ms
ga.js
16 ms
background_repeat.png
361 ms
aktionsbox_back.png
362 ms
frannz_logo.png
363 ms
2016-03-18_Cl_2_0.84278900_1456840557.jpg
659 ms
__utm.gif
263 ms
2016-03-21_Cl_0_0.52637500_1448663746.jpg
427 ms
2015-01-18_Bi_0_0.47986900_1419688619.jpg
512 ms
white_circle_arrow.png
266 ms
top_shadow.png
268 ms
list_arrow_circle_white.png
269 ms
small_row_back.png
267 ms
btn_more.jpg
265 ms
row_line_repeat.png
268 ms
social_icons.png
269 ms
frannz_footer_logo.png
269 ms
large_back.png
1437 ms
ping
140 ms
188 ms
overlay.png
93 ms
controls.png
105 ms
border.png
117 ms
loading_background.png
96 ms
loading.gif
95 ms
likebox.php
294 ms
Graphics.woff
269 ms
xd_arbiter.php
225 ms
xd_arbiter.php
432 ms
like.php
140 ms
qeKvIRsJabD.js
726 ms
LVx-xkvaJ0b.png
788 ms
410ucuAGgaJ.css
813 ms
tSbl8xBI27R.css
883 ms
q68gy-v_YMF.js
1016 ms
FJmpeSpHpjS.js
1012 ms
0wM5s1Khldu.js
889 ms
1bNoFZUdlYZ.js
887 ms
12009698_10153258889677893_519708976285936384_n.jpg
287 ms
268622_10151054544092893_1293601663_n.jpg
355 ms
1451452_438676536238245_2082101486_n.jpg
426 ms
11034202_793339610702193_6176527711562543213_n.jpg
548 ms
248631_10200179876368863_2098064095_n.jpg
521 ms
12814811_545937268917002_2505810114999306867_n.jpg
487 ms
wL6VQj7Ab77.png
76 ms
s7jcwEQH7Sx.png
76 ms
white_circle_arrow_over.png
93 ms
I6-MnjEovm5.js
73 ms
pQrUxxo5oQp.js
136 ms
frannz.de accessibility score
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
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
frannz.de best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
frannz.de 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
DE
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Frannz.de 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 Frannz.de 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.
frannz.de
Open Graph data is detected on the main page of Frannz. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: