Tools & Wizards About Us
omq.ai screenshot

Report Summary

  • 32

    Performance

    Renders faster than
    52% of other websites

  • 66

    Accessibility

    Visual factors better than
    that of 31% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

omq.ai

OMQ | Optimize your support - AI based customer service software | OMQ

Page Load Speed

42.1 sec in total

First Response

117 ms

Resources Loaded

1.6 sec

Page Rendered

40.4 sec

omq.ai screenshot

About Website

Visit omq.ai now to see the best up-to-date OMQ content and also check out these interesting facts you probably never knew about omq.ai

The OMQ software helps your customer support to answer requests automatically. The Artificial intelligence doesn’t have to be trained and can be integrated in all of your communication channels.

Visit omq.ai

Key Findings

We analyzed Omq.ai page load time and found that the first response time was 117 ms and then it took 42 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster.

Performance Metrics

omq.ai performance score

32

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.4 s

97/100

10%

LCP (Largest Contentful Paint)

Value9.0 s

1/100

25%

SI (Speed Index)

Value6.4 s

40/100

10%

TBT (Total Blocking Time)

Value2,020 ms

7/100

30%

CLS (Cumulative Layout Shift)

Value0.103

89/100

15%

TTI (Time to Interactive)

Value9.8 s

28/100

10%

Network Requests Diagram

omq.ai

117 ms

omq.ai

983 ms

tailwind.css

6 ms

main.css

16 ms

index.css

9 ms

Our browser made a total of 97 requests to load all elements on the main page. We found that 93% of them (90 requests) were addressed to the original Omq.ai, 2% (2 requests) were made to Googletagmanager.com and 2% (2 requests) were made to Snap.licdn.com. The less responsive or slowest element that took the longest time to load (983 ms) belongs to the original domain Omq.ai.

Page Optimization Overview & Recommendations

Page size can be reduced by 590.1 kB (5%)

Content Size

12.8 MB

After Optimization

12.2 MB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Omq.ai main page is 12.8 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. Only a small number of websites need less resources to load. Images take 12.6 MB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 121.8 kB

  • Original 142.1 kB
  • After minification 120.7 kB
  • After compression 20.3 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 21.5 kB, which is 15% 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 121.8 kB or 86% of the original size.

Image Optimization

-4%

Potential reduce by 467.2 kB

  • Original 12.6 MB
  • After minification 12.1 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

-2%

Potential reduce by 1.1 kB

  • Original 55.5 kB
  • After minification 55.5 kB
  • After compression 54.4 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. This website has mostly compressed JavaScripts.

Requests Breakdown

Number of requests can be reduced by 27 (28%)

Requests Now

95

After Optimization

68

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 95 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 11 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

omq.ai

omq.ai

117 ms

omq.ai

omq.ai

983 ms

tailwind.css

tailwind.css

6 ms

main.css

main.css

16 ms

index.css

index.css

9 ms

landingpage-new.css

landingpage-new.css

27 ms

main.js

main.js

12 ms

queryParam.js

queryParam.js

12 ms

contact-form.js

contact-form.js

48 ms

gtm.js

gtm.js

11 ms

page-data.json

page-data.json

268 ms

omq.svg

omq.svg

14 ms

chatbot_48x48.svg

chatbot_48x48.svg

18 ms

contact_48x48.svg

contact_48x48.svg

7 ms

gpt-chatbot_56x56.svg

gpt-chatbot_56x56.svg

12 ms

help_48x48.svg

help_48x48.svg

14 ms

reply_48x48.svg

reply_48x48.svg

23 ms

assist_48x48.svg

assist_48x48.svg

20 ms

caro.jpg

caro.jpg

19 ms

nadine_crehl_100@2x.jpg

nadine_crehl_100@2x.jpg

26 ms

frank.jpg

frank.jpg

25 ms

hamburger.svg

hamburger.svg

23 ms

check-black-on-transparent.svg

check-black-on-transparent.svg

26 ms

hero_chatbot.png

hero_chatbot.png

33 ms

hero_chatbot_mobile.png

hero_chatbot_mobile.png

58 ms

hero_help.png

hero_help.png

28 ms

hero_help_mobile.png

hero_help_mobile.png

31 ms

hero_contact.png

hero_contact.png

57 ms

hero_contact_mobile.png

hero_contact_mobile.png

55 ms

hero_assist.png

hero_assist.png

60 ms

hero_assist_mobile.png

hero_assist_mobile.png

58 ms

hero_reply.png

hero_reply.png

59 ms

hero_reply_mobile.png

hero_reply_mobile.png

67 ms

google-en.svg

google-en.svg

62 ms

g2-en.svg

g2-en.svg

65 ms

omr-en.svg

omr-en.svg

68 ms

chatbot.png

chatbot.png

115 ms

messenger.png

messenger.png

71 ms

24_7.png

24_7.png

72 ms

gpt_logo.png

gpt_logo.png

70 ms

help.png

help.png

106 ms

happy-customers.png

happy-customers.png

103 ms

time_icon.png

time_icon.png

102 ms

help-custom-design.png

help-custom-design.png

104 ms

gtm.js

gtm.js

101 ms

array.js

array.js

32 ms

contact.png

contact.png

155 ms

10_min.png

10_min.png

104 ms

dsgvo_icon.png

dsgvo_icon.png

101 ms

callcenter.png

callcenter.png

99 ms

assist.png

assist.png

104 ms

85_percent.png

85_percent.png

97 ms

agents.png

agents.png

96 ms

graph_up_icon.png

graph_up_icon.png

96 ms

reply.png

reply.png

141 ms

ai_icon.png

ai_icon.png

204 ms

automation_easy.png

automation_easy.png

95 ms

flags.png

flags.png

94 ms

automator-en.png

automator-en.png

94 ms

knowledge-base-en.png

knowledge-base-en.png

125 ms

dbbahn.svg

dbbahn.svg

123 ms

magix.svg

magix.svg

125 ms

defshop.svg

defshop.svg

122 ms

babywalz.svg

babywalz.svg

107 ms

hessnatur.svg

hessnatur.svg

108 ms

welt.svg

welt.svg

103 ms

alltours.svg

alltours.svg

102 ms

mister_spex.svg

mister_spex.svg

106 ms

tchibo.svg

tchibo.svg

105 ms

tchibo-logo.png

tchibo-logo.png

102 ms

tchibo-meike-schoenwandt.jpeg

tchibo-meike-schoenwandt.jpeg

152 ms

myphotobook-logo.png

myphotobook-logo.png

99 ms

myphotobook-bianca-gaede.png

myphotobook-bianca-gaede.png

130 ms

alltours-logo.png

alltours-logo.png

99 ms

alltours-andreas-lindemann.png

alltours-andreas-lindemann.png

129 ms

kkt-kolbe-logo.png

kkt-kolbe-logo.png

99 ms

kkt-kolbe-thomas-raab.png

kkt-kolbe-thomas-raab.png

100 ms

mister-spex-logo.png

mister-spex-logo.png

98 ms

mister-spex-rose-schenk.png

mister-spex-rose-schenk.png

99 ms

contact_16x16.svg

contact_16x16.svg

97 ms

assist_16x16.svg

assist_16x16.svg

98 ms

help_16x16.svg

help_16x16.svg

98 ms

reply_16x16.svg

reply_16x16.svg

99 ms

chatbot_16x16.svg

chatbot_16x16.svg

98 ms

omq-black.svg

omq-black.svg

102 ms

newsletter_black.svg

newsletter_black.svg

96 ms

twitter_black.svg

twitter_black.svg

95 ms

facebook_black.svg

facebook_black.svg

95 ms

instagram_black.svg

instagram_black.svg

97 ms

linkedin_black.svg

linkedin_black.svg

98 ms

js

js

41 ms

recorder.js

recorder.js

146 ms

insight.min.js

insight.min.js

104 ms

fbevents.js

fbevents.js

74 ms

pcs_headpicture.png

pcs_headpicture.png

30 ms

headpicture_sao_paulo_v2.png

headpicture_sao_paulo_v2.png

31 ms

insight.old.min.js

insight.old.min.js

7 ms

Accessibility Review

omq.ai accessibility score

66

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

Image elements do not have [alt] attributes

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

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

omq.ai SEO score

77

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

Image elements do not have [alt] attributes

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

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: