4.2 sec in total
483 ms
3.6 sec
124 ms
Click here to check amazing Webfire content. Otherwise, check out these important facts you probably never knew about webfire.ch
FIREGROUP HOLDING AG in Switzerland: Technology holding for B2B software, digital transformation, creative marketing & startup investments.
Visit webfire.chWe analyzed Webfire.ch page load time and found that the first response time was 483 ms and then it took 3.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
webfire.ch performance score
name
value
score
weighting
Value7.6 s
0/100
10%
Value11.6 s
0/100
25%
Value10.6 s
7/100
10%
Value920 ms
30/100
30%
Value0
100/100
15%
Value12.9 s
13/100
10%
483 ms
310 ms
296 ms
410 ms
1115 ms
Our browser made a total of 40 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Webfire.ch, 68% (27 requests) were made to Firegroup.ch and 15% (6 requests) were made to . The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Firegroup.ch.
Page size can be reduced by 464.2 kB (30%)
1.5 MB
1.1 MB
In fact, the total size of Webfire.ch main page is 1.5 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. 45% of websites need less resources to load. HTML takes 877.6 kB which makes up the majority of the site volume.
Potential reduce by 328.4 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 328.4 kB or 37% of the original size.
Potential reduce by 6.5 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. Webfire images are well optimized though.
Potential reduce by 128.5 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 128.5 kB or 47% of the original size.
Potential reduce by 747 B
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. Webfire.ch has all CSS files already compressed.
Number of requests can be reduced by 19 (68%)
28
9
The browser has sent 28 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Webfire. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
webfire.ch
483 ms
leistungen.html
310 ms
leistungen.html
296 ms
leistungen.html
410 ms
leistungen
1115 ms
gtm.js
76 ms
slick.css
293 ms
slick-theme.css
293 ms
main.js
587 ms
main_async_begin.js
293 ms
uc.js
43 ms
js
59 ms
analytics.js
21 ms
validationEngine.jquery.css
110 ms
jquery.validationEngine-de.js
115 ms
jquery.validationEngine.js
196 ms
sw-main.js
114 ms
slick.min.js
116 ms
main_async_end.js
227 ms
close.png
227 ms
loading.gif
228 ms
prev.png
269 ms
next.png
288 ms
close.png
292 ms
firegroup_logo.svg
303 ms
emotion_pic_7.jpg
584 ms
EDVGwKVlcvWGTH9sp4P7GxZEMoW8k92RUf4dgcc8d4b3MG15DyZMs+H3TWekqWY5sXJwnD0mPSxmf3vC8wZPjb6X4DRkJQSI=
14 ms
jF5ZSPSVU3Ys8Xlinifm4Yk5HZRibPWkerk+nuDV+jXMsyyf8TPPLiR+kEGR3uMVwQmJWrgf5SfihmjYVCyu2bApjO0UcHfj4kjOoG8U92RUf4fgcM8d4b3MG95AxZMs+H3TOeWlqkY2PinS+6THpYyPb3je4Onxt1L+Alo9QTI=
13 ms
CCDIrnHK7wVNSphf5SfiBuiYFOxuHrDJj+1U8DdjYsjGcLQSu7JpP4OweKeO8J7mTe8hoonWfD7prfS1bKa2Li4SO6THpcyPr7heYMnx99K+Qvn+0EW
13 ms
lfIX16pBEg==
11 ms
H5Jc9LPDn8Worf2atB+g==
11 ms
tVPA3Y2LIxnC0EruyaT+DsHinjvCe5k3vIaKJ1nw+6a30tWymti4uEjukx6XMj6+4XmDJ8ffSvkL+ExBGg==
10 ms
fbevents.js
15 ms
kaffee.svg
123 ms
swiss.png
128 ms
refprev.png
160 ms
refnext.png
163 ms
loaderIconSmall.png
174 ms
fonts.css
196 ms
Material-Design-Iconic-Font.woff
98 ms
webfire.ch accessibility score
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.
webfire.ch 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
webfire.ch 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 uses legible font sizes
![]()
DE
![]()
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Webfire.ch 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 Webfire.ch 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.
webfire.ch
Open Graph description is not detected on the main page of Webfire. 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: