Tools & Wizards About Us
eloquium.de screenshot

Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 71

    Accessibility

    Visual factors better than
    that of 36% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

eloquium.de

eloquium - Ihre Agentur für Marketing und eBusiness - Startseite

Page Load Speed

3.6 sec in total

First Response

318 ms

Resources Loaded

2.9 sec

Page Rendered

348 ms

eloquium.de screenshot

About Website

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

Eloquium ist Ihr starker Partner für Ihr eBusiness. Vom Online-Shop über Warenwirtschaft und Lagerverwaltungssoftware bis zur individuellen Softwarelösung.

Visit eloquium.de

Key Findings

We analyzed Eloquium.de page load time and found that the first response time was 318 ms and then it took 3.3 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

eloquium.de performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.8 s

5/100

10%

LCP (Largest Contentful Paint)

Value10.9 s

0/100

25%

SI (Speed Index)

Value13.7 s

2/100

10%

TBT (Total Blocking Time)

Value3,010 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value13.8 s

10/100

10%

Network Requests Diagram

eloquium.de

318 ms

www.eloquium.de

1315 ms

js

66 ms

A.autoptimize_80e4be35076b7b01b791d69c7e2c38e9.css.pagespeed.cf.K_PGYryPXI.css

579 ms

A.autoptimize_00df71b5809d374b00ce03791ac8fac1.css.pagespeed.cf.zdkk0kVwMG.css

299 ms

Our browser made a total of 26 requests to load all elements on the main page. We found that 92% of them (24 requests) were addressed to the original Eloquium.de, 4% (1 request) were made to Googletagmanager.com and 4% (1 request) were made to Get.anydesk.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Eloquium.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.2 MB (54%)

Content Size

2.3 MB

After Optimization

1.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Eloquium.de main page is 2.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. 30% of websites need less resources to load. Javascripts take 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 112.3 kB

  • Original 144.4 kB
  • After minification 144.3 kB
  • After compression 32.1 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 112.3 kB or 78% of the original size.

Image Optimization

-0%

Potential reduce by 895 B

  • Original 597.9 kB
  • After minification 597.0 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. Eloquium images are well optimized though.

JavaScript Optimization

-66%

Potential reduce by 766.1 kB

  • Original 1.2 MB
  • After minification 1.2 MB
  • After compression 393.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 766.1 kB or 66% of the original size.

CSS Optimization

-96%

Potential reduce by 344.4 kB

  • Original 357.3 kB
  • After minification 67.4 kB
  • After compression 12.9 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. Eloquium.de needs all CSS files to be minified and compressed as it can save up to 344.4 kB or 96% of the original size.

Requests Breakdown

Number of requests can be reduced by 12 (63%)

Requests Now

19

After Optimization

7

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

eloquium.de

eloquium.de

318 ms

www.eloquium.de

www.eloquium.de

1315 ms

js

js

66 ms

A.autoptimize_80e4be35076b7b01b791d69c7e2c38e9.css.pagespeed.cf.K_PGYryPXI.css

A.autoptimize_80e4be35076b7b01b791d69c7e2c38e9.css.pagespeed.cf.K_PGYryPXI.css

579 ms

A.autoptimize_00df71b5809d374b00ce03791ac8fac1.css.pagespeed.cf.zdkk0kVwMG.css

A.autoptimize_00df71b5809d374b00ce03791ac8fac1.css.pagespeed.cf.zdkk0kVwMG.css

299 ms

c81b5475cc66bdfca4c37c9051c281e5.js,qver=b0759e6f78c1d393b42cbf57d4842856.pagespeed.ce.sHWeb3jB05.js

c81b5475cc66bdfca4c37c9051c281e5.js,qver=b0759e6f78c1d393b42cbf57d4842856.pagespeed.ce.sHWeb3jB05.js

397 ms

9abb7efed57614525b2ca9749d2b5b6b.js,qver=b1de37713dec44c8ce34af65eb7cd331.pagespeed.ce.gav0T3jkB3.js

9abb7efed57614525b2ca9749d2b5b6b.js,qver=b1de37713dec44c8ce34af65eb7cd331.pagespeed.ce.gav0T3jkB3.js

445 ms

A.animate.min.css,qver=4.1.1.pagespeed.cf.M3aj0gs58u.css

A.animate.min.css,qver=4.1.1.pagespeed.cf.M3aj0gs58u.css

300 ms

A.,qgt3_show_only_css=1,aver=6.2.1.pagespeed.cf.rvJyua04z6.css

A.,qgt3_show_only_css=1,aver=6.2.1.pagespeed.cf.rvJyua04z6.css

302 ms

autoptimize_single_a6b8d51ca910b9ec87e164e9ac8fb636.css

autoptimize_single_a6b8d51ca910b9ec87e164e9ac8fb636.css

413 ms

autoptimize_single_36ea4805809e6b690c2f5126a0808297.css

autoptimize_single_36ea4805809e6b690c2f5126a0808297.css

511 ms

jquery.min.js,qver=3.6.4.pagespeed.jm.eeevgC5Itb.js

jquery.min.js,qver=3.6.4.pagespeed.jm.eeevgC5Itb.js

512 ms

lazysizes.min.js,qao_version=3.1.8.1.pagespeed.jm.1GZcCAEhu4.js

lazysizes.min.js,qao_version=3.1.8.1.pagespeed.jm.1GZcCAEhu4.js

496 ms

autoptimize_single_6d9f0819ade6c4c733d150571ebcb026.css

autoptimize_single_6d9f0819ade6c4c733d150571ebcb026.css

748 ms

24cb307c465f23c4380832fbbb7b88fd.js,qver=a60b028afbcee4e4bb81108ec7e534fc.pagespeed.ce.fUlZzpPMoy.js

24cb307c465f23c4380832fbbb7b88fd.js,qver=a60b028afbcee4e4bb81108ec7e534fc.pagespeed.ce.fUlZzpPMoy.js

548 ms

autoptimize_f546db8b966c00e49763f349b760688f.js

autoptimize_f546db8b966c00e49763f349b760688f.js

1122 ms

dummy.png.pagespeed.ce.KmN9PYJWc8.png

dummy.png.pagespeed.ce.KmN9PYJWc8.png

107 ms

xmehrwert-startseite.jpg,qid=2080.pagespeed.ic.jCgRAWehov.jpg

xmehrwert-startseite.jpg,qid=2080.pagespeed.ic.jCgRAWehov.jpg

413 ms

xunsere-kunden.jpg,qid=2082.pagespeed.ic.Hi2QjTLCIG.jpg

xunsere-kunden.jpg,qid=2082.pagespeed.ic.Hi2QjTLCIG.jpg

497 ms

fa-solid-900.woff

fa-solid-900.woff

366 ms

fa-solid-900.woff

fa-solid-900.woff

321 ms

fa-regular-400.woff

fa-regular-400.woff

182 ms

fa-regular-400.woff

fa-regular-400.woff

297 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

507 ms

dl-btn-rw-medium.png

dl-btn-rw-medium.png

449 ms

eloquium-logo.png.pagespeed.ce.tCBKyXZ3SQ.png

eloquium-logo.png.pagespeed.ce.tCBKyXZ3SQ.png

383 ms

Accessibility Review

eloquium.de accessibility score

71

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-*] attributes do not match their roles

High

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

High

[aria-*] attributes do not have valid values

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

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

eloquium.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

High

Missing source maps for large first-party JavaScript

SEO Factors

eloquium.de SEO score

90

Search Engine Optimization Advices

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    DE

  • Language Claimed

    DE

  • Encoding

    UTF-8

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

eloquium.de

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