Tools & Wizards About Us
sep.de screenshot

Report Summary

  • 8

    Performance

    Renders faster than
    22% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 49% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

sep.de

SEP - The Data Protection Company

Page Load Speed

3.8 sec in total

First Response

316 ms

Resources Loaded

2.9 sec

Page Rendered

522 ms

sep.de screenshot

About Website

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

SEP sesam backup and recovery solution for virtual and physical environments protects companies and organizations from small to large enterprises.

Visit sep.de

Key Findings

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

Performance Metrics

sep.de performance score

8

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

52/100

10%

LCP (Largest Contentful Paint)

Value12.5 s

0/100

25%

SI (Speed Index)

Value9.3 s

13/100

10%

TBT (Total Blocking Time)

Value6,180 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.561

12/100

15%

TTI (Time to Interactive)

Value22.4 s

1/100

10%

Network Requests Diagram

sep.de

316 ms

www.sep.de

808 ms

merged-92ce2975d10a5e095a147967a2f7c55d-41e8eacc8c9cd5869fbb6a2480c753d8.css

299 ms

merged-ab0199115c4e9674615aa4deee67b491-094af48a69b329a2e4d19498c25a869a.js

575 ms

merged-6fbd66578890fdd78311872fd740bc49-623b39403cf53af1354381ad9ddf0715.js

338 ms

Our browser made a total of 86 requests to load all elements on the main page. We found that 83% of them (71 requests) were addressed to the original Sep.de, 8% (7 requests) were made to Use.typekit.net and 2% (2 requests) were made to Madixel.de. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Sep.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 336.7 kB (7%)

Content Size

4.9 MB

After Optimization

4.6 MB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Sep.de main page is 4.9 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. 50% of websites need less resources to load. Images take 4.5 MB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 186.1 kB

  • Original 259.7 kB
  • After minification 241.5 kB
  • After compression 73.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 186.1 kB or 72% of the original size.

Image Optimization

-2%

Potential reduce by 71.9 kB

  • Original 4.5 MB
  • After minification 4.5 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. SEP images are well optimized though.

JavaScript Optimization

-65%

Potential reduce by 78.7 kB

  • Original 120.5 kB
  • After minification 120.5 kB
  • After compression 41.8 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 78.7 kB or 65% of the original size.

Requests Breakdown

Number of requests can be reduced by 6 (8%)

Requests Now

72

After Optimization

66

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

sep.de

sep.de

316 ms

www.sep.de

www.sep.de

808 ms

merged-92ce2975d10a5e095a147967a2f7c55d-41e8eacc8c9cd5869fbb6a2480c753d8.css

merged-92ce2975d10a5e095a147967a2f7c55d-41e8eacc8c9cd5869fbb6a2480c753d8.css

299 ms

merged-ab0199115c4e9674615aa4deee67b491-094af48a69b329a2e4d19498c25a869a.js

merged-ab0199115c4e9674615aa4deee67b491-094af48a69b329a2e4d19498c25a869a.js

575 ms

merged-6fbd66578890fdd78311872fd740bc49-623b39403cf53af1354381ad9ddf0715.js

merged-6fbd66578890fdd78311872fd740bc49-623b39403cf53af1354381ad9ddf0715.js

338 ms

vca4ooo.js

vca4ooo.js

237 ms

insight.min.js

insight.min.js

204 ms

gtm.js

gtm.js

366 ms

tracking.js

tracking.js

778 ms

bg.jpg

bg.jpg

649 ms

csm_Company_Facts_971ddab4e6.png

csm_Company_Facts_971ddab4e6.png

369 ms

hintag-lenzburg-1.svg

hintag-lenzburg-1.svg

458 ms

KRAMSKI_Logo_blau_eps.svg

KRAMSKI_Logo_blau_eps.svg

472 ms

syna-logo.jpg

syna-logo.jpg

554 ms

Technische-Betriebe-Remscheid.png

Technische-Betriebe-Remscheid.png

473 ms

Logo_Wagner-AG.png

Logo_Wagner-AG.png

507 ms

logo-Ennepe-Ruhr-Kreis.png

logo-Ennepe-Ruhr-Kreis.png

538 ms

logo-Resolve-BioSciences-GmbH.png

logo-Resolve-BioSciences-GmbH.png

556 ms

Logo-MPK-Poznan.png

Logo-MPK-Poznan.png

566 ms

stuertz-logo.png

stuertz-logo.png

601 ms

steinemann_logo.png

steinemann_logo.png

722 ms

lraMS.png

lraMS.png

648 ms

landshut.png

landshut.png

745 ms

laserline.png

laserline.png

659 ms

walter.png

walter.png

694 ms

neuhofer.png

neuhofer.png

743 ms

Logo_pdg_RZ.jpg

Logo_pdg_RZ.jpg

1032 ms

cirb-brussels-it-is-for-you.png

cirb-brussels-it-is-for-you.png

753 ms

AXIANS_CRVB.jpeg

AXIANS_CRVB.jpeg

791 ms

Bildschirmfoto_2021-10-14_um_16.04.38.png

Bildschirmfoto_2021-10-14_um_16.04.38.png

817 ms

Bildschirmfoto_2021-09-11_um_09.55.36.png

Bildschirmfoto_2021-09-11_um_09.55.36.png

836 ms

LogoSBZ.png

LogoSBZ.png

843 ms

Wiener_Neustadt_Stadtwerke_Logo.png

Wiener_Neustadt_Stadtwerke_Logo.png

846 ms

Compact_Cleaning_Logo.png

Compact_Cleaning_Logo.png

885 ms

FENDT_Logo.png

FENDT_Logo.png

913 ms

Siedlungswerk.png

Siedlungswerk.png

1033 ms

Sauter.png

Sauter.png

937 ms

NAT.jpg

NAT.jpg

939 ms

motorol-logo.png

motorol-logo.png

978 ms

Jan-Pol_1.png

Jan-Pol_1.png

1007 ms

SAPUCC.jpg

SAPUCC.jpg

1034 ms

logo_Holiday_inn_Krakau.png

logo_Holiday_inn_Krakau.png

1034 ms

trafomodern.jpg

trafomodern.jpg

948 ms

DINCond-Regular.woff

DINCond-Regular.woff

926 ms

insight_tag_errors.gif

insight_tag_errors.gif

160 ms

d

d

26 ms

d

d

34 ms

d

d

36 ms

d

d

35 ms

d

d

36 ms

d

d

37 ms

DINCond-Light.woff

DINCond-Light.woff

766 ms

piwik.js

piwik.js

673 ms

DINCond-Bold.woff

DINCond-Bold.woff

694 ms

p.gif

p.gif

34 ms

icomoon.ttf

icomoon.ttf

666 ms

glyphicons-halflings-regular.woff

glyphicons-halflings-regular.woff

663 ms

MPA_logo.png

MPA_logo.png

695 ms

Collogia_Bild.jpg

Collogia_Bild.jpg

879 ms

huebner.jpg

huebner.jpg

684 ms

BBI_logo.png

BBI_logo.png

670 ms

KRZ-Cottbus-Geb%C3%A4ude.richtig.png

KRZ-Cottbus-Geb%C3%A4ude.richtig.png

865 ms

Pilz_Backwerk_logo.jpg

Pilz_Backwerk_logo.jpg

661 ms

RefLogo250-TUWien.png

RefLogo250-TUWien.png

661 ms

Hako_logo.png

Hako_logo.png

667 ms

Sagaflor_Logo_Format.png

Sagaflor_Logo_Format.png

669 ms

Spiegel_logo.png

Spiegel_logo.png

661 ms

Kwizda_logo.png

Kwizda_logo.png

661 ms

Vodafone-Logo-png-download.png

Vodafone-Logo-png-download.png

687 ms

UNIORG_Logo.png

UNIORG_Logo.png

668 ms

link-logo.png

link-logo.png

669 ms

GVB_2016_Logo.png

GVB_2016_Logo.png

695 ms

tracking.php

tracking.php

322 ms

Logo_ALDI_Nord.jpg

Logo_ALDI_Nord.jpg

687 ms

BeladenEinerZentrifuge_by_TillBudde_DIfE.jpg

BeladenEinerZentrifuge_by_TillBudde_DIfE.jpg

684 ms

ennit_full.png

ennit_full.png

667 ms

RefLogo250-StadtwerkePotsdam.png

RefLogo250-StadtwerkePotsdam.png

664 ms

DavosKlosters_logo.png

DavosKlosters_logo.png

667 ms

RefLogo250-Handelshof.png

RefLogo250-Handelshof.png

656 ms

RefLogo250-GEVA.png

RefLogo250-GEVA.png

658 ms

iphone.png

iphone.png

657 ms

csm_SEPsesamApollonLogoPlain1500px_669face5ec.png

csm_SEPsesamApollonLogoPlain1500px_669face5ec.png

659 ms

SEP-sesam-Box_EN_Web.png

SEP-sesam-Box_EN_Web.png

625 ms

bg-marketing.jpg

bg-marketing.jpg

602 ms

bg-2.jpg

bg-2.jpg

607 ms

piwik.php

piwik.php

148 ms

Accessibility Review

sep.de accessibility score

80

Accessibility Issues

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 input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

[role]s are not contained by their required parent element

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

Heading elements are not in a sequentially-descending order

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

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

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

sep.de best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

sep.de SEO score

79

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

High

Document doesn't have a valid hreflang

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Sep.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 Sep.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

sep.de

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