Tools & Wizards About Us
cimco.de screenshot

Report Summary

  • 21

    Performance

    Renders faster than
    39% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 74% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

cimco.de

CIMCO - Dein Partner für Elektroniker-Bedarf

Page Load Speed

5.1 sec in total

First Response

349 ms

Resources Loaded

4 sec

Page Rendered

752 ms

cimco.de screenshot

About Website

Welcome to cimco.de homepage info - get ready to check CIMCO best content for Germany right away, or after learning these important things about cimco.de

Mit unseren Werkzeugen führst du jede Elektro-Installation sicher durch. Jetzt mehr erfahren.

Visit cimco.de

Key Findings

We analyzed Cimco.de page load time and found that the first response time was 349 ms and then it took 4.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

cimco.de performance score

21

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

36/100

10%

LCP (Largest Contentful Paint)

Value19.0 s

0/100

25%

SI (Speed Index)

Value10.6 s

7/100

10%

TBT (Total Blocking Time)

Value2,150 ms

6/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value19.1 s

3/100

10%

Network Requests Diagram

cimco.de

349 ms

de

647 ms

c07f324d0af4885f.css

334 ms

2b8a5a231ec12339.css

322 ms

420b8a163ac866f7.css

404 ms

Our browser made a total of 61 requests to load all elements on the main page. We found that 89% of them (54 requests) were addressed to the original Cimco.de, 8% (5 requests) were made to Brick-e51d1516-15a3-4577-a8b5-d7ff13568a4c.brick-cdn.com and 2% (1 request) were made to Player.vimeo.com. The less responsive or slowest element that took the longest time to load (1.6 sec) relates to the external source I.vimeocdn.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 222.8 kB (5%)

Content Size

4.5 MB

After Optimization

4.3 MB

  • HTML
  • Images

In fact, the total size of Cimco.de main page is 4.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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 4.3 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 140.3 kB

  • Original 177.6 kB
  • After minification 176.4 kB
  • After compression 37.2 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 140.3 kB or 79% of the original size.

Image Optimization

-2%

Potential reduce by 82.4 kB

  • Original 4.3 MB
  • After minification 4.2 MB

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. CIMCO images are well optimized though.

Requests Breakdown

Number of requests can be reduced by 40 (74%)

Requests Now

54

After Optimization

14

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 54 CSS, Javascripts, AJAX and image requests in order to completely render the main page of CIMCO. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 36 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

cimco.de

cimco.de

349 ms

de

de

647 ms

c07f324d0af4885f.css

c07f324d0af4885f.css

334 ms

2b8a5a231ec12339.css

2b8a5a231ec12339.css

322 ms

420b8a163ac866f7.css

420b8a163ac866f7.css

404 ms

25c3c7f3f1b518fe.css

25c3c7f3f1b518fe.css

352 ms

0cba2fd1d464f3d1.css

0cba2fd1d464f3d1.css

361 ms

a8680bd48f02d5d7.css

a8680bd48f02d5d7.css

411 ms

fd9d1056-49a7fe382be1c29d.js

fd9d1056-49a7fe382be1c29d.js

499 ms

8069-3cfb7b6300d5c000.js

8069-3cfb7b6300d5c000.js

530 ms

main-app-bc3aa384848d6ae8.js

main-app-bc3aa384848d6ae8.js

453 ms

8792-761829ec8a51f4f9.js

8792-761829ec8a51f4f9.js

455 ms

1749-1f6de3a661507572.js

1749-1f6de3a661507572.js

494 ms

4170-6af437cb39a78dc4.js

4170-6af437cb39a78dc4.js

506 ms

8481-7ff33d870feb1096.js

8481-7ff33d870feb1096.js

719 ms

global-error-9ceb2501f4d13274.js

global-error-9ceb2501f4d13274.js

542 ms

8009-213462b0ec63758f.js

8009-213462b0ec63758f.js

617 ms

layout-b1a5fae4e518ea2b.js

layout-b1a5fae4e518ea2b.js

598 ms

8082-8eb57493ac52cccc.js

8082-8eb57493ac52cccc.js

712 ms

layout-4f891d069d16e9c9.js

layout-4f891d069d16e9c9.js

658 ms

4e6af11a-a5925b94f627ef2b.js

4e6af11a-a5925b94f627ef2b.js

659 ms

c15bf2b0-c1e67d7e14142851.js

c15bf2b0-c1e67d7e14142851.js

682 ms

3595-ab2d3ad1b6bbac64.js

3595-ab2d3ad1b6bbac64.js

778 ms

4775-217771be162e067a.js

4775-217771be162e067a.js

754 ms

7847-d650047d7906d088.js

7847-d650047d7906d088.js

754 ms

3716-8a4c3f4eb68eaa5f.js

3716-8a4c3f4eb68eaa5f.js

764 ms

8075-7828dfd353072cae.js

8075-7828dfd353072cae.js

795 ms

7120-ab4797eefccf4336.js

7120-ab4797eefccf4336.js

795 ms

4035-77bc1c542ffcfbc0.js

4035-77bc1c542ffcfbc0.js

851 ms

4739-e1cec552809c97a5.js

4739-e1cec552809c97a5.js

850 ms

3527-c9224f6bb78b128e.js

3527-c9224f6bb78b128e.js

851 ms

5975-a8dc1ade0b220bdd.js

5975-a8dc1ade0b220bdd.js

865 ms

9140-30281edd27152acc.js

9140-30281edd27152acc.js

877 ms

4704-169fed30349b30ee.js

4704-169fed30349b30ee.js

878 ms

5579-c62370d1577e5b09.js

5579-c62370d1577e5b09.js

933 ms

681-5372036eadde712e.js

681-5372036eadde712e.js

934 ms

9759-6a875f8e5fbc355e.js

9759-6a875f8e5fbc355e.js

933 ms

491-03cc84f201676dbb.js

491-03cc84f201676dbb.js

630 ms

1991-26d75ce092d58ebb.js

1991-26d75ce092d58ebb.js

624 ms

4635-ac91a95db587a0f1.js

4635-ac91a95db587a0f1.js

617 ms

page-1d78cf82d3c264aa.js

page-1d78cf82d3c264aa.js

659 ms

polyfills-c67a75d1b6f99dc8.js

polyfills-c67a75d1b6f99dc8.js

664 ms

webpack-97bd25e65492d322.js

webpack-97bd25e65492d322.js

614 ms

not-found-0417a075d238d618.js

not-found-0417a075d238d618.js

734 ms

923362270

923362270

249 ms

logo-light.svg

logo-light.svg

116 ms

pattern-nav.svg

pattern-nav.svg

119 ms

image

image

261 ms

footer.svg

footer.svg

113 ms

fa-light-300.91541f2e.ttf

fa-light-300.91541f2e.ttf

416 ms

fa-regular-400.764b12a3.ttf

fa-regular-400.764b12a3.ttf

453 ms

fa-solid-900.6812495e.ttf

fa-solid-900.6812495e.ttf

351 ms

fa-sharp-regular-400.7ae4d773.ttf

fa-sharp-regular-400.7ae4d773.ttf

659 ms

fa-brands-400.6a230855.ttf

fa-brands-400.6a230855.ttf

264 ms

MItarbeiter-am-Stromkasten.jpg

MItarbeiter-am-Stromkasten.jpg

241 ms

pattern.svg

pattern.svg

199 ms

Kabel-schneiden-Close-Up.jpg

Kabel-schneiden-Close-Up.jpg

350 ms

Datennetzwerktechnik.jpg

Datennetzwerktechnik.jpg

406 ms

Mitarbeiter-Photovoltaik.jpg

Mitarbeiter-Photovoltaik.jpg

405 ms

Arbeiten-unter-Spannung.jpg

Arbeiten-unter-Spannung.jpg

403 ms

1815388447-d1033a06d26e94890a45eb776ed4b4726a146fbe77be663fd9de75ba3ce24c82-d

1815388447-d1033a06d26e94890a45eb776ed4b4726a146fbe77be663fd9de75ba3ce24c82-d

1642 ms

Accessibility Review

cimco.de accessibility score

90

Accessibility Issues

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

High

Buttons do not have an accessible name

High

Links do not have a discernible name

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

cimco.de best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

cimco.de SEO score

85

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    DE

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Cimco.de can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Cimco.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.

Social Sharing Optimization

cimco.de

Open Graph description is not detected on the main page of CIMCO. 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: