2.7 sec in total
259 ms
2.3 sec
146 ms
Welcome to fhz-forum.de homepage info - get ready to check FHZ Forum best content right away, or after learning these important things about fhz-forum.de
Forum und Produktests zum Thema Haussteueung mit ELV HomeMatic und FS20 / FHZ.
Visit fhz-forum.deWe analyzed Fhz-forum.de page load time and found that the first response time was 259 ms and then it took 2.4 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.
fhz-forum.de performance score
name
value
score
weighting
Value3.6 s
32/100
10%
Value4.1 s
47/100
25%
Value5.2 s
60/100
10%
Value880 ms
32/100
30%
Value0
100/100
15%
Value7.4 s
49/100
10%
259 ms
331 ms
106 ms
207 ms
206 ms
Our browser made a total of 53 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Fhz-forum.de, 25% (13 requests) were made to Homematic-forum.de and 19% (10 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (745 ms) relates to the external source Wms.assoc-amazon.de.
Page size can be reduced by 250.8 kB (53%)
475.2 kB
224.3 kB
In fact, the total size of Fhz-forum.de main page is 475.2 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. 50% of websites need less resources to load. Javascripts take 315.0 kB which makes up the majority of the site volume.
Potential reduce by 18.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 18.6 kB or 72% of the original size.
Potential reduce by 21.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. Obviously, FHZ Forum needs image optimization as it can save up to 21.8 kB or 19% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 193.7 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 193.7 kB or 61% of the original size.
Potential reduce by 16.7 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. Fhz-forum.de needs all CSS files to be minified and compressed as it can save up to 16.7 kB or 82% of the original size.
Number of requests can be reduced by 27 (56%)
48
21
The browser has sent 48 CSS, Javascripts, AJAX and image requests in order to completely render the main page of FHZ Forum. 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.
fhz-forum.de
259 ms
homematic-forum.de
331 ms
format.css
106 ms
format_navigation_fussnote_aktionsbox.css
207 ms
cookie-hinweis.js
206 ms
show_ads.js
5 ms
ga.js
39 ms
ca-pub-7367622604264680.js
62 ms
zrt_lookup.html
29 ms
show_ads_impl.js
59 ms
cse.js
28 ms
amazon_widget_cms.htm
110 ms
pix.gif
124 ms
ccu2_728x90.png
235 ms
Hintergrund-Kopfzeile.png
213 ms
HomeMatic-und-FHZ-Forum.png
211 ms
contronics-banner.png
211 ms
mediola-banner-links.gif
427 ms
ccu2_151x139.png
351 ms
HomeMatic-Zentrale-CCU2-4.png
426 ms
cse.js
131 ms
__utm.gif
44 ms
ads
130 ms
osd.js
13 ms
ads
203 ms
q
444 ms
ads
184 ms
jsapi
38 ms
default+de.css
3 ms
default.css
23 ms
default+de.I.js
23 ms
abg.js
52 ms
default.css
18 ms
async-ads.js
41 ms
google_custom_search_watermark.gif
38 ms
small-logo.png
38 ms
search_box_icon.png
36 ms
clear.png
37 ms
nav_logo114.png
38 ms
m_js_controller.js
9 ms
favicon
59 ms
s
30 ms
googlelogo_color_112x36dp.png
35 ms
favicon
31 ms
nessie_icon_tiamat_white.png
15 ms
x_button_blue2.png
16 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
10 ms
8002_7.js
745 ms
popup.js
83 ms
nifty.js
164 ms
colors.js
164 ms
activeview
12 ms
activeview
15 ms
fhz-forum.de accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
[role]s are not contained by their required parent element
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Some elements have a [tabindex] value greater than 0
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
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
List items (<li>) are not contained within <ul> or <ol> parent elements.
fhz-forum.de 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
fhz-forum.de SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
DE
DE
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fhz-forum.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 Fhz-forum.de 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.
fhz-forum.de
Open Graph description is not detected on the main page of FHZ Forum. 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: