Tools & Wizards About Us
protecfire.de screenshot

Report Summary

  • 11

    Performance

    Renders faster than
    24% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 98

    SEO

    Google-friendlier than
    92% of websites

protecfire.de

Automatic Fire Suppression Systems - Protecfire

Page Load Speed

8 sec in total

First Response

378 ms

Resources Loaded

6.7 sec

Page Rendered

1 sec

protecfire.de screenshot

About Website

Welcome to protecfire.de homepage info - get ready to check Protecfire best content right away, or after learning these important things about protecfire.de

Protecfire manufactures fire suppression systems for Vehicles, Kitchens, Wind Turbines, Electric Cabinets, Heavy Industries, and other sectors

Visit protecfire.de

Key Findings

We analyzed Protecfire.de page load time and found that the first response time was 378 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.

Performance Metrics

protecfire.de performance score

11

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.1 s

1/100

10%

LCP (Largest Contentful Paint)

Value14.6 s

0/100

25%

SI (Speed Index)

Value20.9 s

0/100

10%

TBT (Total Blocking Time)

Value16,110 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.163

72/100

15%

TTI (Time to Interactive)

Value27.3 s

0/100

10%

Network Requests Diagram

protecfire.de

378 ms

www.protecfire.de

866 ms

wp-emoji-release.min.js

202 ms

select2.min.css

336 ms

iconfonts.css

374 ms

Our browser made a total of 123 requests to load all elements on the main page. We found that 99% of them (122 requests) were addressed to the original Protecfire.de, 1% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Protecfire.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 409.3 kB (49%)

Content Size

836.7 kB

After Optimization

427.4 kB

  • HTML
  • Images

In fact, the total size of Protecfire.de main page is 836.7 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. 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. HTML takes 439.0 kB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 386.0 kB

  • Original 439.0 kB
  • After minification 432.8 kB
  • After compression 53.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 386.0 kB or 88% of the original size.

Image Optimization

-6%

Potential reduce by 23.3 kB

  • Original 397.7 kB
  • After minification 374.4 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. Protecfire images are well optimized though.

Requests Breakdown

Number of requests can be reduced by 85 (75%)

Requests Now

114

After Optimization

29

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

protecfire.de

protecfire.de

378 ms

www.protecfire.de

www.protecfire.de

866 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

202 ms

select2.min.css

select2.min.css

336 ms

iconfonts.css

iconfonts.css

374 ms

frontend.min.css

frontend.min.css

618 ms

tooltip.css

tooltip.css

370 ms

tooltipster-sideTip-shadow.min.css

tooltipster-sideTip-shadow.min.css

420 ms

featherlight.css

featherlight.css

389 ms

lity.min.css

lity.min.css

456 ms

mec-general-calendar.css

mec-general-calendar.css

500 ms

bootstrap.min.css

bootstrap.min.css

526 ms

font-sizes.min.css

font-sizes.min.css

530 ms

style.min.css

style.min.css

552 ms

cookie-law-info-public.css

cookie-law-info-public.css

577 ms

cookie-law-info-gdpr.css

cookie-law-info-gdpr.css

647 ms

job-listings.css

job-listings.css

651 ms

trp-language-switcher.css

trp-language-switcher.css

649 ms

style.min.css

style.min.css

680 ms

hestia-google-font-roboto-condensed.css

hestia-google-font-roboto-condensed.css

701 ms

themify-icons.min.css

themify-icons.min.css

746 ms

dflip.min.css

dflip.min.css

747 ms

elementor-icons.min.css

elementor-icons.min.css

782 ms

frontend-lite.min.css

frontend-lite.min.css

774 ms

frontend-lite.min.css

frontend-lite.min.css

801 ms

all.min.css

all.min.css

823 ms

v4-shims.min.css

v4-shims.min.css

862 ms

google-fonts-1.css

google-fonts-1.css

895 ms

fontawesome.min.css

fontawesome.min.css

901 ms

solid.min.css

solid.min.css

922 ms

regular.min.css

regular.min.css

949 ms

jquery.min.js

jquery.min.js

1111 ms

jquery-migrate.min.js

jquery-migrate.min.js

1109 ms

mec-general-calendar.js

mec-general-calendar.js

1245 ms

frontend.js

frontend.js

1130 ms

events.js

events.js

1131 ms

js

js

60 ms

widget-nav-menu.min.css

widget-nav-menu.min.css

1089 ms

widget-icon-box.min.css

widget-icon-box.min.css

1013 ms

owl.carousel.min.css

owl.carousel.min.css

933 ms

owl.theme.min.css

owl.theme.min.css

899 ms

cookie-law-info-table.css

cookie-law-info-table.css

881 ms

widgets-1664528493.css

widgets-1664528493.css

999 ms

animations.min.css

animations.min.css

1052 ms

cookie-law-info-public.js

cookie-law-info-public.js

1012 ms

cookie-law-info-ccpa.js

cookie-law-info-ccpa.js

958 ms

aos.min.js

aos.min.js

938 ms

v4-shims.min.js

v4-shims.min.js

938 ms

core.min.js

core.min.js

909 ms

datepicker.min.js

datepicker.min.js

973 ms

jquery.typewatch.js

jquery.typewatch.js

887 ms

featherlight.js

featherlight.js

902 ms

select2.full.min.js

select2.full.min.js

1004 ms

tooltip.js

tooltip.js

918 ms

lity.min.js

lity.min.js

841 ms

colorbrightness.min.js

colorbrightness.min.js

950 ms

owl.carousel.min.js

owl.carousel.min.js

918 ms

comment-reply.min.js

comment-reply.min.js

909 ms

bootstrap.min.js

bootstrap.min.js

887 ms

script.min.js

script.min.js

905 ms

dflip.min.js

dflip.min.js

1123 ms

jquery.smartmenus.min.js

jquery.smartmenus.min.js

989 ms

webpack-pro.runtime.min.js

webpack-pro.runtime.min.js

908 ms

webpack.runtime.min.js

webpack.runtime.min.js

909 ms

frontend-modules.min.js

frontend-modules.min.js

950 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

935 ms

wp-polyfill.min.js

wp-polyfill.min.js

1019 ms

hooks.min.js

hooks.min.js

830 ms

i18n.min.js

i18n.min.js

856 ms

frontend.min.js

frontend.min.js

1083 ms

waypoints.min.js

waypoints.min.js

1063 ms

frontend.min.js

frontend.min.js

1062 ms

elements-handlers.min.js

elements-handlers.min.js

955 ms

jquery.sticky.min.js

jquery.sticky.min.js

955 ms

underscore.min.js

underscore.min.js

955 ms

wp-util.min.js

wp-util.min.js

959 ms

frontend.min.js

frontend.min.js

959 ms

lazyload.min.js

lazyload.min.js

853 ms

matomo.js

matomo.js

885 ms

protecfire-fire-protection-for-windturbine.webp

protecfire-fire-protection-for-windturbine.webp

1035 ms

colors-bar@4x.png

colors-bar@4x.png

884 ms

all-tanks-protecfire2.294.webp

all-tanks-protecfire2.294.webp

1036 ms

mining-sector.webp

mining-sector.webp

887 ms

bus-sector.webp

bus-sector.webp

842 ms

wind-sector.webp

wind-sector.webp

894 ms

roboto-condensed-normal-300.woff

roboto-condensed-normal-300.woff

874 ms

roboto-condensed-normal-400.woff

roboto-condensed-normal-400.woff

965 ms

roboto-condensed-normal-700.woff

roboto-condensed-normal-700.woff

949 ms

fa-brands-400.woff

fa-brands-400.woff

1052 ms

fa-solid-900.woff

fa-solid-900.woff

1089 ms

fa-regular-400.woff

fa-regular-400.woff

963 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

1067 ms

kitchen-sector.webp

kitchen-sector.webp

954 ms

marine-sector.webp

marine-sector.webp

986 ms

defense-sector.webp

defense-sector.webp

1016 ms

circle.svg

circle.svg

1028 ms

qr-code-vcard-protecfire-GmbH.png

qr-code-vcard-protecfire-GmbH.png

241 ms

en_GB.png

en_GB.png

167 ms

de_DE.png

de_DE.png

177 ms

es_ES.png

es_ES.png

184 ms

pt_PT.png

pt_PT.png

242 ms

fr_FR.png

fr_FR.png

255 ms

ru_RU.png

ru_RU.png

255 ms

tr_TR.png

tr_TR.png

256 ms

pl_PL.png

pl_PL.png

304 ms

sv_SE.png

sv_SE.png

307 ms

logo-o-protecfire-white.png

logo-o-protecfire-white.png

377 ms

icon-sector-mining@10x.webp

icon-sector-mining@10x.webp

383 ms

icon-sector-bus@10x.webp

icon-sector-bus@10x.webp

385 ms

icon-sector-wind@10x.webp

icon-sector-wind@10x.webp

374 ms

icon-sector-kitchens@10x.webp

icon-sector-kitchens@10x.webp

431 ms

icon-sector-nautical@10x.webp

icon-sector-nautical@10x.webp

441 ms

icon-sector-others@10x.webp

icon-sector-others@10x.webp

496 ms

vds-Stifterverband-madeingermany2.webp

vds-Stifterverband-madeingermany2.webp

495 ms

jobpost-protecfire2hiring.webp

jobpost-protecfire2hiring.webp

519 ms

punch-campaign-reel-quadrado.webp

punch-campaign-reel-quadrado.webp

534 ms

miningturkey.png

miningturkey.png

553 ms

certificacions-protecfire-1024x206.png

certificacions-protecfire-1024x206.png

565 ms

cert-VdS@8x.png

cert-VdS@8x.png

630 ms

Seal-of-approval-by-Stifterverband.png

Seal-of-approval-by-Stifterverband.png

852 ms

logo-cookieyes.svg

logo-cookieyes.svg

642 ms

matomo.php

matomo.php

1470 ms

screen-logo-protecfire-2021@4x.png

screen-logo-protecfire-2021@4x.png

321 ms

Accessibility Review

protecfire.de accessibility score

81

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

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

High

Heading elements are not in a sequentially-descending order

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

High

ARIA IDs are not unique

Best Practices

protecfire.de best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

protecfire.de SEO score

98

Search Engine Optimization Advices

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Protecfire.de can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Protecfire.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

protecfire.de

Open Graph data is detected on the main page of Protecfire. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: