3.9 sec in total
347 ms
3.1 sec
404 ms
Visit fcc.de now to see the best up-to-date FCC content and also check out these interesting facts you probably never knew about fcc.de
SAP Consulting u. Hosting für den Mittelstand in Nürnberg vom Spezialisten ISO Professional Services, der ehemaligen Faber-Castell Consulting (FCC)
Visit fcc.deWe analyzed Fcc.de page load time and found that the first response time was 347 ms and then it took 3.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
fcc.de performance score
name
value
score
weighting
Value5.5 s
6/100
10%
Value9.9 s
0/100
25%
Value6.9 s
33/100
10%
Value230 ms
86/100
30%
Value0.062
97/100
15%
Value9.0 s
34/100
10%
347 ms
346 ms
1381 ms
26 ms
39 ms
Our browser made a total of 35 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Fcc.de, 66% (23 requests) were made to Iso-gruppe.com and 14% (5 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.4 sec) relates to the external source Iso-gruppe.com.
Page size can be reduced by 326.1 kB (26%)
1.3 MB
950.3 kB
In fact, the total size of Fcc.de main page is 1.3 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. 40% of websites need less resources to load. Images take 848.4 kB which makes up the majority of the site volume.
Potential reduce by 97.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. This page needs HTML code to be minified as it can gain 38.4 kB, which is 35% 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 97.0 kB or 89% of the original size.
Potential reduce by 1.9 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. FCC images are well optimized though.
Potential reduce by 102.1 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 102.1 kB or 60% of the original size.
Potential reduce by 125.0 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. Fcc.de needs all CSS files to be minified and compressed as it can save up to 125.0 kB or 83% of the original size.
Number of requests can be reduced by 6 (23%)
26
20
The browser has sent 26 CSS, Javascripts, AJAX and image requests in order to completely render the main page of FCC. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 4 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
fcc.de
347 ms
iso-professional-services.html
346 ms
iso-professional-services.html
1381 ms
css
26 ms
css
39 ms
style.all.min_446f48bcc415a8d08bd5af40d6cbcdb4.css
276 ms
logo-ips.png
104 ms
ips.jpg
220 ms
datenqualitaet.jpg
551 ms
hosting.jpg
460 ms
sap-consulting.jpg
460 ms
managed-services.jpg
551 ms
sap-partner.png
189 ms
iso.slider_b109af5f057c73905d0a6b82f3fbae0d.js
203 ms
Innovationspreis-dq.png
237 ms
teaser-data-governance-materialstamm.jpg
937 ms
regiolux.png
329 ms
landis-gyr.png
422 ms
viessmann.png
478 ms
cws-boco.png
479 ms
faber-castell.png
513 ms
jungheinrich.png
566 ms
cJZKeOuBrn4kERxqtaUH3SZ2oysoEQEeKwjgmXLRnTc.ttf
23 ms
MTP_ySUJH_bn48VBG8sNSpS3E-kSBmtLoNJPDtbj2Pk.ttf
24 ms
k3k702ZOKiLJc3WVjuplzJS3E-kSBmtLoNJPDtbj2Pk.ttf
24 ms
7XUFZ5tgS-tD6QamInJTcbFJZbTbly0V4A-kMlrADXE.ttf
24 ms
anMUvcNT0H1YN4FII8wprxgm6d0i0FjSmyQ0ElZwmAs.ttf
24 ms
isoicons.woff
566 ms
lib.foot.min_cc4ee85d26fce6e1b4257e50e81b9a6c.js
636 ms
dc.js
60 ms
logo-ips.svg
94 ms
inpage_linkid.js
5 ms
__utm.gif
12 ms
print_57cf6b2778e4dd096dccfacede1fcf8f.css
95 ms
__utm.gif
11 ms
fcc.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
Image elements do not have [alt] attributes
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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.
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.
fcc.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
fcc.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
N/A
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fcc.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 Fcc.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.
fcc.de
Open Graph description is not detected on the main page of FCC. 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: