3.4 sec in total
541 ms
2.7 sec
159 ms
Welcome to fonflatter.de homepage info - get ready to check Fonflatter best content for Germany right away, or after learning these important things about fonflatter.de
Fred, eine stets zuversichtliche, einfallsreiche, zumeist aber alberne und etwas naive Fledermaus, flattert bereits seit 2005 täglich durch das weltweite Netz
Visit fonflatter.deWe analyzed Fonflatter.de page load time and found that the first response time was 541 ms and then it took 2.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
fonflatter.de performance score
name
value
score
weighting
Value3.9 s
25/100
10%
Value6.1 s
12/100
25%
Value5.9 s
47/100
10%
Value990 ms
28/100
30%
Value0.233
53/100
15%
Value7.7 s
45/100
10%
541 ms
286 ms
496 ms
201 ms
199 ms
Our browser made a total of 51 requests to load all elements on the main page. We found that 90% of them (46 requests) were addressed to the original Fonflatter.de, 4% (2 requests) were made to Static.xx.fbcdn.net and 2% (1 request) were made to Static.twoday.net. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Fonflatter.de.
Page size can be reduced by 128.2 kB (42%)
306.8 kB
178.6 kB
In fact, the total size of Fonflatter.de main page is 306.8 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 15% of websites need less resources to load. Images take 152.6 kB which makes up the majority of the site volume.
Potential reduce by 24.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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 24.6 kB or 81% of the original size.
Potential reduce by 22.6 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. Obviously, Fonflatter needs image optimization as it can save up to 22.6 kB or 15% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 78.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 78.0 kB or 65% of the original size.
Potential reduce by 3.1 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. Fonflatter.de needs all CSS files to be minified and compressed as it can save up to 3.1 kB or 73% of the original size.
Number of requests can be reduced by 13 (26%)
50
37
The browser has sent 50 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fonflatter. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 6 to 1 for JavaScripts and as a result speed up the page load time.
www.fonflatter.de
541 ms
wp-emoji-release.min.js
286 ms
jquery.js
496 ms
jquery-migrate.min.js
201 ms
style.css
199 ms
facebook_like.js
188 ms
click.js
203 ms
wunschzettel.png
313 ms
header.jpg
189 ms
header_over.jpg
196 ms
zehn_10s.png
294 ms
menu_shop.png
199 ms
menu_geschenke.png
199 ms
menu_post.png
203 ms
rss.png
387 ms
w3c-xhtml1.1.png
394 ms
w3c-css2.1.png
397 ms
cynthia-test.png
396 ms
fred_2016-03-16_s.png
497 ms
transkript_btn.gif
488 ms
zufall.gif
582 ms
fred_freu.png
593 ms
fred_grins.png
592 ms
stein.png
595 ms
fred_pfeifen.gif
688 ms
fred_hoe.png
695 ms
1.gif
777 ms
Maulwurf.png
780 ms
fischmitglas.png
794 ms
fred_boese.png
795 ms
fred_genau.png
885 ms
fred_muede.png
894 ms
fred_neutral.png
972 ms
fred_schlaf.gif
983 ms
fred_sobri.png
994 ms
fred_traurig.png
990 ms
fred_uff.png
1082 ms
fred_wink.gif
1096 ms
fred_zunge.png
1167 ms
fred_zwinker.png
1184 ms
herz.png
1187 ms
kaefer_ups.png
1192 ms
keks.png
1277 ms
schnecke.png
1280 ms
80x15.png
39 ms
like.php
53 ms
q0KzV8g0NEh.js
17 ms
LVx-xkvaJ0b.png
12 ms
spinne.png
1187 ms
wurm.png
1192 ms
wurm_fluecht.png
1193 ms
fonflatter.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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
fonflatter.de best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
fonflatter.de 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 doesn't use legible font sizes
Tap targets are not sized appropriately
N/A
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fonflatter.de 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 German. Our system also found out that Fonflatter.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.
fonflatter.de
Open Graph description is not detected on the main page of Fonflatter. 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: