Tools & Wizards About Us
omq.de screenshot

Report Summary

  • 49

    Performance

    Renders faster than
    67% of other websites

  • 71

    Accessibility

    Visual factors better than
    that of 36% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

omq.de

Mit KI im Kundenservice zur Effizienzsteigerung

Page Load Speed

23.7 sec in total

First Response

38 ms

Resources Loaded

5.8 sec

Page Rendered

17.9 sec

omq.de screenshot

About Website

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

Künstliche Intelligenz im Kundenservice ► Automatisiere Anfragen, steigere die Effizienz & verbessere die Kundenzufriedenheit. Jetzt mehr erfahren! ✓

Visit omq.de

Key Findings

We analyzed Omq.de page load time and found that the first response time was 38 ms and then it took 23.7 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.

Performance Metrics

omq.de performance score

49

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

40/100

10%

LCP (Largest Contentful Paint)

Value3.3 s

70/100

25%

SI (Speed Index)

Value5.6 s

54/100

10%

TBT (Total Blocking Time)

Value1,040 ms

26/100

30%

CLS (Cumulative Layout Shift)

Value0.139

79/100

15%

TTI (Time to Interactive)

Value9.6 s

29/100

10%

Network Requests Diagram

omq.de

38 ms

369 ms

uc.js

20 ms

e03c8b0001074b6588801d9d2088a9f128e510fc420643a8baaad9572230be67.js

312 ms

gtm.js

97 ms

Our browser made a total of 90 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Omq.de, 92% (83 requests) were made to Omq.ai and 1% (1 request) were made to Consent.cookiebot.com. The less responsive or slowest element that took the longest time to load (3.7 sec) relates to the external source Omq.ai.

Page Optimization Overview & Recommendations

Page size can be reduced by 852.6 kB (6%)

Content Size

13.6 MB

After Optimization

12.7 MB

  • HTML
  • Images
  • JavaScript

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

HTML Optimization

-86%

Potential reduce by 293.5 kB

  • Original 341.4 kB
  • After minification 299.4 kB
  • After compression 48.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. This page needs HTML code to be minified as it can gain 42.0 kB, which is 12% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 293.5 kB or 86% of the original size.

Image Optimization

-4%

Potential reduce by 471.3 kB

  • Original 13.0 MB
  • After minification 12.6 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. Omq images are well optimized though.

JavaScript Optimization

-50%

Potential reduce by 87.9 kB

  • Original 174.9 kB
  • After minification 174.9 kB
  • After compression 87.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 87.9 kB or 50% of the original size.

Requests Breakdown

Number of requests can be reduced by 19 (22%)

Requests Now

88

After Optimization

69

  • AJAX
  • Images
  • JavaScript

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

Network Requests Diagram

omq.de

omq.de

38 ms

369 ms

uc.js

uc.js

20 ms

e03c8b0001074b6588801d9d2088a9f128e510fc420643a8baaad9572230be67.js

e03c8b0001074b6588801d9d2088a9f128e510fc420643a8baaad9572230be67.js

312 ms

gtm.js

gtm.js

97 ms

array.js

array.js

32 ms

omq.svg

omq.svg

20 ms

page-data.json

page-data.json

910 ms

chatbot_48x48.svg

chatbot_48x48.svg

43 ms

contact_48x48.svg

contact_48x48.svg

34 ms

gpt-chatbot_56x56.svg

gpt-chatbot_56x56.svg

40 ms

help_48x48.svg

help_48x48.svg

33 ms

reply_48x48.svg

reply_48x48.svg

35 ms

assist_48x48.svg

assist_48x48.svg

39 ms

caro.jpg

caro.jpg

43 ms

nadine_crehl_100@2x.jpg

nadine_crehl_100@2x.jpg

78 ms

frank.jpg

frank.jpg

78 ms

hamburger.svg

hamburger.svg

76 ms

check-black-on-transparent.svg

check-black-on-transparent.svg

76 ms

hero_chatbot_de.png

hero_chatbot_de.png

1176 ms

hero_chatbot_de_mobile.png

hero_chatbot_de_mobile.png

1013 ms

hero_help_de.png

hero_help_de.png

451 ms

hero_help_de_mobile.png

hero_help_de_mobile.png

1113 ms

hero_contact_de.png

hero_contact_de.png

979 ms

hero_contact_de_mobile.png

hero_contact_de_mobile.png

912 ms

hero_assist_de.png

hero_assist_de.png

1458 ms

hero_assist_de_mobile.png

hero_assist_de_mobile.png

1458 ms

hero_reply_de.png

hero_reply_de.png

1530 ms

hero_reply_de_mobile.png

hero_reply_de_mobile.png

1569 ms

google-de.svg

google-de.svg

1550 ms

g2-de.svg

g2-de.svg

1596 ms

omr-de.svg

omr-de.svg

1885 ms

chatbot_de.png

chatbot_de.png

2304 ms

messenger.png

messenger.png

2029 ms

24_7.png

24_7.png

1884 ms

gpt_logo.png

gpt_logo.png

1827 ms

help_de.png

help_de.png

2691 ms

happy-customers.png

happy-customers.png

2452 ms

time_icon.png

time_icon.png

2332 ms

help-custom-design.png

help-custom-design.png

2310 ms

contact_de.png

contact_de.png

3017 ms

10_min.png

10_min.png

2459 ms

dsgvo_icon.png

dsgvo_icon.png

2728 ms

532 ms

callcenter.png

callcenter.png

2849 ms

assist_de.png

assist_de.png

3262 ms

85_percent.png

85_percent.png

2693 ms

agents.png

agents.png

3216 ms

graph_up_icon.png

graph_up_icon.png

2950 ms

reply_de.png

reply_de.png

3419 ms

ai_icon.png

ai_icon.png

3276 ms

automatisierung_einfach.png

automatisierung_einfach.png

3343 ms

flags.png

flags.png

3280 ms

support-team.png

support-team.png

3698 ms

check-white-on-transparent.svg

check-white-on-transparent.svg

3222 ms

automator-de.png

automator-de.png

3302 ms

recorder.js

recorder.js

39 ms

knowledge-base-de.png

knowledge-base-de.png

2873 ms

dbbahn.svg

dbbahn.svg

2704 ms

magix.svg

magix.svg

2697 ms

defshop.svg

defshop.svg

2698 ms

babywalz.svg

babywalz.svg

2763 ms

hessnatur.svg

hessnatur.svg

2746 ms

welt.svg

welt.svg

2497 ms

alltours.svg

alltours.svg

2464 ms

mister_spex.svg

mister_spex.svg

2397 ms

tchibo.svg

tchibo.svg

2484 ms

tchibo-logo.png

tchibo-logo.png

2573 ms

tchibo-meike-schoenwandt.jpeg

tchibo-meike-schoenwandt.jpeg

3715 ms

myphotobook-logo_black.png

myphotobook-logo_black.png

2362 ms

myphotobook-bianca-gaede.png

myphotobook-bianca-gaede.png

2773 ms

alltours-logo.png

alltours-logo.png

2234 ms

alltours-andreas-lindemann.png

alltours-andreas-lindemann.png

2667 ms

kkt-kolbe-logo.png

kkt-kolbe-logo.png

2159 ms

kkt-kolbe-thomas-raab.png

kkt-kolbe-thomas-raab.png

2461 ms

mister-spex-logo_black.png

mister-spex-logo_black.png

2020 ms

mister-spex-rose-schenk.png

mister-spex-rose-schenk.png

2458 ms

contact_16x16.svg

contact_16x16.svg

2012 ms

assist_16x16.svg

assist_16x16.svg

1782 ms

help_16x16.svg

help_16x16.svg

1749 ms

reply_16x16.svg

reply_16x16.svg

1753 ms

chatbot_16x16.svg

chatbot_16x16.svg

1603 ms

omq-black.svg

omq-black.svg

1501 ms

newsletter_black.svg

newsletter_black.svg

1478 ms

twitter_black.svg

twitter_black.svg

1243 ms

facebook_black.svg

facebook_black.svg

1205 ms

instagram_black.svg

instagram_black.svg

1207 ms

linkedin_black.svg

linkedin_black.svg

1165 ms

headpicture_sao_paulo_v2.png

headpicture_sao_paulo_v2.png

1178 ms

heapicture_lima.png

heapicture_lima.png

1137 ms

Accessibility Review

omq.de accessibility score

71

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

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.

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

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

Page has valid source maps

SEO Factors

omq.de SEO score

91

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

omq.de

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