8.1 sec in total
421 ms
3.8 sec
3.9 sec
Welcome to fr.de homepage info - get ready to check Fr best content for Germany right away, or after learning these important things about fr.de
Aktuelle Nachrichten aus Politik, Wirtschaft, Sport, Kultur und Frankfurt.
Visit fr.deWe analyzed Fr.de page load time and found that the first response time was 421 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.
fr.de performance score
name
value
score
weighting
Value9.4 s
0/100
10%
Value18.6 s
0/100
25%
Value25.5 s
0/100
10%
Value6,230 ms
0/100
30%
Value0.024
100/100
15%
Value40.7 s
0/100
10%
421 ms
695 ms
219 ms
330 ms
596 ms
Our browser made a total of 53 requests to load all elements on the main page. We found that 13% of them (7 requests) were addressed to the original Fr.de, 17% (9 requests) were made to Cdn.opencmp.net and 15% (8 requests) were made to Idcdn.de. The less responsive or slowest element that took the longest time to load (1 sec) relates to the external source Idcdn.de.
Page size can be reduced by 865.7 kB (75%)
1.2 MB
289.4 kB
In fact, the total size of Fr.de 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. 65% of websites need less resources to load. HTML takes 544.3 kB which makes up the majority of the site volume.
Potential reduce by 461.0 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 461.0 kB or 85% of the original size.
Potential reduce by 0 B
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. Fr images are well optimized though.
Potential reduce by 144.9 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 144.9 kB or 54% of the original size.
Potential reduce by 259.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. Fr.de needs all CSS files to be minified and compressed as it can save up to 259.9 kB or 86% of the original size.
Number of requests can be reduced by 25 (58%)
43
18
The browser has sent 43 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fr. 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 5 to 1 for CSS and as a result speed up the page load time.
fr.de
421 ms
www.fr.de
695 ms
prod_click.css
219 ms
270-23-grid.css
330 ms
58c64d04e45a1d2f02abc17b.js
596 ms
cmp-stub-latest.js
68 ms
trfAdSetup.js
42 ms
analytics.js
197 ms
smarttag.js
264 ms
gtm.js
253 ms
require.2.1.18.min.js
1036 ms
logo.png
422 ms
24179023-ein-helfer-der-johanniter-wartet-im-corona-testzentrum-am-flughafen-hannover-auf-den-naechsten-patienten-2uOLkF2DXga7.jpg
422 ms
logo75.png
931 ms
logo-sticky.png
933 ms
cmp-latest.js
158 ms
cmp-latest.css
176 ms
trf-id-frankfurt.js
155 ms
id-icons-m.woff
847 ms
linkid.js
62 ms
smarttag.js
40 ms
chartbeat.js
258 ms
index.js
182 ms
hit.xiti
651 ms
js
199 ms
settings.json
54 ms
hit.xiti
647 ms
ping
110 ms
style.css
44 ms
vendor-list-en.json
80 ms
AGSKWxWAqG4Lss9Zcm8E-NzstFCHADq65ePXqtYnM2Xtudzeu4IllEKz4k3vXH6k3LGFPgWodITdd-My5CzRQtqBTJU=
162 ms
collect
152 ms
collect
185 ms
collect
182 ms
translation-en.json
55 ms
AGSKWxX70Sr9DouLw4dyxYQodO9Vy74fb9fM4x_BTDCwF9fD2K7VXoYm8cXyt65VZhv5Ar45ITih88aUumRq2LQYrzo=
210 ms
collect
236 ms
collect
347 ms
apple-touch-icon-144x144-precomposed.png
206 ms
i
191 ms
Ubuntu-Regular.ttf
121 ms
Ubuntu-Medium.ttf
122 ms
hit.xiti
100 ms
webfont.js
20 ms
id.tm.js
153 ms
vendor-combined.js
224 ms
global-modules-combined.js
151 ms
iam.js
635 ms
css
36 ms
KFOlCnqEu92Fr1MmEU9fBBc-AMP6lQ.woff
19 ms
u-440qyriQwlOrhSvowK_l5-fCZKdeX3rg.woff
68 ms
u-4n0qyriQwlOrhSvowK_l52xwNZWMf8hPvhPQ.woff
69 ms
id.core.js
167 ms
fr.de 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.
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
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
fr.de best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
fr.de SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
DE
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fr.de can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and it matches the claimed language. Our system also found out that Fr.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.
fr.de
Open Graph data is detected on the main page of Fr. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: