Tools & Wizards About Us
adrg.info screenshot

Report Summary

  • 37

    Performance

    Renders faster than
    56% of other websites

  • 61

    Accessibility

    Visual factors better than
    that of 27% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

adrg.info

ADRG Gebäudereinigung | Höchstadt a.d. Aisch | Start

Page Load Speed

5.5 sec in total

First Response

267 ms

Resources Loaded

4.7 sec

Page Rendered

522 ms

adrg.info screenshot

About Website

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

Ihr Partner rund um die Themen Gebäudereinigung, Facility Management und Sicherheitsdienst. Hier klicken!

Visit adrg.info

Key Findings

We analyzed Adrg.info page load time and found that the first response time was 267 ms and then it took 5.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

adrg.info performance score

37

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.3 s

7/100

10%

LCP (Largest Contentful Paint)

Value16.2 s

0/100

25%

SI (Speed Index)

Value8.5 s

17/100

10%

TBT (Total Blocking Time)

Value40 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.546

13/100

15%

TTI (Time to Interactive)

Value10.6 s

23/100

10%

Network Requests Diagram

adrg.info

267 ms

adrg-gebaeudereinigung.de

1318 ms

beng-proxy.js

632 ms

font-awesome.min.css

800 ms

widget-runtime.css

707 ms

Our browser made a total of 59 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Adrg.info, 39% (23 requests) were made to Strato-editor.com and 32% (19 requests) were made to Fonts.cm4all.net. The less responsive or slowest element that took the longest time to load (1.7 sec) relates to the external source Adrg-gebaeudereinigung.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 394.4 kB (44%)

Content Size

886.3 kB

After Optimization

491.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Adrg.info main page is 886.3 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. 50% of websites need less resources to load. Javascripts take 404.1 kB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 76.9 kB

  • Original 90.9 kB
  • After minification 90.0 kB
  • After compression 14.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 76.9 kB or 85% of the original size.

Image Optimization

-1%

Potential reduce by 4.2 kB

  • Original 331.5 kB
  • After minification 327.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. ADRG images are well optimized though.

JavaScript Optimization

-66%

Potential reduce by 268.1 kB

  • Original 404.1 kB
  • After minification 401.4 kB
  • After compression 136.0 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 268.1 kB or 66% of the original size.

CSS Optimization

-76%

Potential reduce by 45.2 kB

  • Original 59.8 kB
  • After minification 59.2 kB
  • After compression 14.5 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. Adrg.info needs all CSS files to be minified and compressed as it can save up to 45.2 kB or 76% of the original size.

Requests Breakdown

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

Requests Now

24

After Optimization

6

  • Images
  • JavaScript
  • CSS

The browser has sent 24 CSS, Javascripts, AJAX and image requests in order to completely render the main page of ADRG. 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 8 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

adrg.info

adrg.info

267 ms

adrg-gebaeudereinigung.de

adrg-gebaeudereinigung.de

1318 ms

beng-proxy.js

beng-proxy.js

632 ms

font-awesome.min.css

font-awesome.min.css

800 ms

widget-runtime.css

widget-runtime.css

707 ms

deploy.css

deploy.css

711 ms

slideshow-common.css

slideshow-common.css

715 ms

jquery.js

jquery.js

821 ms

prototype.js

prototype.js

843 ms

legacy.js

legacy.js

808 ms

widget-runtime.js

widget-runtime.js

919 ms

slideshow-common.js

slideshow-common.js

819 ms

deploy.js

deploy.js

901 ms

uro-min.js

uro-min.js

938 ms

main.css

main.css

958 ms

responsive.css

responsive.css

953 ms

effects.js

effects.js

1033 ms

cm_template-focus-point.js

cm_template-focus-point.js

1036 ms

vars.css

vars.css

330 ms

cm-templates-global-script.js

cm-templates-global-script.js

842 ms

show.js

show.js

167 ms

css

css

462 ms

picture-200

picture-200

215 ms

picture-200

picture-200

112 ms

picture-200

picture-200

113 ms

ptRMTiqXYfZMCOiVj9kQ1Of4LQ.ttf

ptRMTiqXYfZMCOiVj9kQ1Of4LQ.ttf

207 ms

ptRPTiqXYfZMCOiVj9kQ3ELaPQJPrQ.ttf

ptRPTiqXYfZMCOiVj9kQ3ELaPQJPrQ.ttf

432 ms

ptRPTiqXYfZMCOiVj9kQ3FLdPQJPrQ.ttf

ptRPTiqXYfZMCOiVj9kQ3FLdPQJPrQ.ttf

433 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVc.ttf

411 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0B4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0B4uaVc.ttf

416 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVc.ttf

416 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVc.ttf

313 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVc.ttf

444 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4uaVc.ttf

612 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCGPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCGPrQ.ttf

622 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoorCGPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoorCGPrQ.ttf

622 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCGPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCGPrQ.ttf

633 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtaorCGPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtaorCGPrQ.ttf

633 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvao7CGPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvao7CGPrQ.ttf

537 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpbCGPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpbCGPrQ.ttf

646 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCGPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCGPrQ.ttf

715 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtapbCGPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtapbCGPrQ.ttf

726 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtzpbCGPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtzpbCGPrQ.ttf

727 ms

_pixel.img

_pixel.img

139 ms

arrows.png

arrows.png

113 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

223 ms

bif_39651412_cm-a.jpg

bif_39651412_cm-a.jpg

605 ms

picture-1200

picture-1200

1650 ms

picture-200

picture-200

232 ms

picture-200

picture-200

270 ms

picture-200

picture-200

207 ms

picture-200

picture-200

230 ms

picture-200

picture-200

251 ms

picture-200

picture-200

289 ms

picture-200

picture-200

250 ms

picture-200

picture-200

277 ms

picture-2600

picture-2600

777 ms

_FUN6997%20a%20Logo%20ret.jpg

_FUN6997%20a%20Logo%20ret.jpg

679 ms

picture-2600

picture-2600

673 ms

Accessibility Review

adrg.info accessibility score

61

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

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

Form elements do not have associated labels

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

adrg.info best practices score

83

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

Page has valid source maps

SEO Factors

adrg.info SEO score

92

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

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 Adrg.info 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 Adrg.info 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

adrg.info

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