Tools & Wizards About Us
q2e.at screenshot

Report Summary

  • 75

    Performance

    Renders faster than
    84% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

q2e.at

Q2E Online-Agentur in NÖ | Webdesign & Online Marketing

Page Load Speed

4 sec in total

First Response

328 ms

Resources Loaded

3.3 sec

Page Rendered

327 ms

q2e.at screenshot

About Website

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

Wir sind Q2E, die kreative Online-Agentur und Ihr Wegbegleiter zum digitalen Erfolg: Sprechen wir darüber, wie Sie online neue Kunden gewinnen >

Visit q2e.at

Key Findings

We analyzed Q2e.at page load time and found that the first response time was 328 ms and then it took 3.6 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

q2e.at performance score

75

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

58/100

10%

LCP (Largest Contentful Paint)

Value4.1 s

46/100

25%

SI (Speed Index)

Value4.0 s

81/100

10%

TBT (Total Blocking Time)

Value120 ms

97/100

30%

CLS (Cumulative Layout Shift)

Value0.093

91/100

15%

TTI (Time to Interactive)

Value5.3 s

73/100

10%

Network Requests Diagram

q2e.at

328 ms

www.q2e.at

755 ms

css

36 ms

css

49 ms

_styles.css

250 ms

Our browser made a total of 46 requests to load all elements on the main page. We found that 78% of them (36 requests) were addressed to the original Q2e.at, 9% (4 requests) were made to Fonts.gstatic.com and 7% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Q2e.at.

Page Optimization Overview & Recommendations

Page size can be reduced by 259.8 kB (14%)

Content Size

1.9 MB

After Optimization

1.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Q2e.at main page is 1.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. 40% of websites need less resources to load. Images take 1.6 MB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 63.4 kB

  • Original 73.3 kB
  • After minification 65.9 kB
  • After compression 9.9 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 63.4 kB or 87% of the original size.

Image Optimization

-3%

Potential reduce by 39.8 kB

  • Original 1.6 MB
  • After minification 1.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. Q2E images are well optimized though.

JavaScript Optimization

-61%

Potential reduce by 115.2 kB

  • Original 189.5 kB
  • After minification 188.6 kB
  • After compression 74.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 115.2 kB or 61% of the original size.

CSS Optimization

-80%

Potential reduce by 41.4 kB

  • Original 51.6 kB
  • After minification 46.0 kB
  • After compression 10.3 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. Q2e.at needs all CSS files to be minified and compressed as it can save up to 41.4 kB or 80% of the original size.

Requests Breakdown

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

Requests Now

40

After Optimization

33

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

q2e.at

q2e.at

328 ms

www.q2e.at

www.q2e.at

755 ms

css

css

36 ms

css

css

49 ms

_styles.css

_styles.css

250 ms

jquery.fancybox.css

jquery.fancybox.css

229 ms

css

css

71 ms

_tps.js

_tps.js

463 ms

ModuleSiteindexCompendium.js

ModuleSiteindexCompendium.js

241 ms

_q2e.js

_q2e.js

222 ms

body_bg.jpg

body_bg.jpg

239 ms

bg_main.jpg

bg_main.jpg

552 ms

logo_q2e_new.png

logo_q2e_new.png

234 ms

nv_bg.png

nv_bg.png

224 ms

menu_icon.png

menu_icon.png

255 ms

sn_nav_bg.jpg

sn_nav_bg.jpg

225 ms

si_area1_default_img.png

si_area1_default_img.png

939 ms

si_site1_area1_box1-1-1-1_135.png

si_site1_area1_box1-1-1-1_135.png

1162 ms

si_site1_area1_box2-1-1-3_548.png

si_site1_area1_box2-1-1-3_548.png

1068 ms

si_site1_area1_box3-1-1-5_997.png

si_site1_area1_box3-1-1-5_997.png

1162 ms

si_site1_area1_box5-1-1-4_978.png

si_site1_area1_box5-1-1-4_978.png

985 ms

bg_tagcloud.png

bg_tagcloud.png

769 ms

bg_si_area_2_3.png

bg_si_area_2_3.png

994 ms

si_site1_area2-1-2_155.png

si_site1_area2-1-2_155.png

1277 ms

si_site1_area3-1-3_471.png

si_site1_area3-1-3_471.png

1196 ms

icons_sprite.png

icons_sprite.png

1202 ms

si_site1_area5_box12-1-5-20_149.jpg

si_site1_area5_box12-1-5-20_149.jpg

1291 ms

si_site1_area5_box14-1-5-16_840.jpg

si_site1_area5_box14-1-5-16_840.jpg

1376 ms

si_site1_area5_box14-1-5-21_635.jpg

si_site1_area5_box14-1-5-21_635.jpg

1378 ms

si_site1_area5_box7-1-5-17_753.jpg

si_site1_area5_box7-1-5-17_753.jpg

1411 ms

si_site1_area5_box3-1-5-18_564.jpg

si_site1_area5_box3-1-5-18_564.jpg

1417 ms

si_site1_area5_box1-1-5-50_432.jpg

si_site1_area5_box1-1-5-50_432.jpg

1489 ms

si_site1_area5_box1-1-5-23_905.jpg

si_site1_area5_box1-1-5-23_905.jpg

1505 ms

si_site1_area5_box1-1-5-25_557.jpg

si_site1_area5_box1-1-5-25_557.jpg

1587 ms

si_site1_area5_box15-1-5-49_650.jpg

si_site1_area5_box15-1-5-49_650.jpg

1595 ms

si_site1_area5_box15-1-5-22_777.jpg

si_site1_area5_box15-1-5-22_777.jpg

1628 ms

si_site1_area5_box1-1-5-47_168.jpg

si_site1_area5_box1-1-5-47_168.jpg

1642 ms

gk5FxslNkTTHtojXrkp-xHET45GJjz32KVyq5hq61wLr7w4p9aSvGirXi6XmeXNA.ttf

gk5FxslNkTTHtojXrkp-xHET45GJjz32KVyq5hq61wLr7w4p9aSvGirXi6XmeXNA.ttf

86 ms

gk5FxslNkTTHtojXrkp-xEb5azEPpng8GbF4Y4e4kqzr7w4p9aSvGirXi6XmeXNA.ttf

gk5FxslNkTTHtojXrkp-xEb5azEPpng8GbF4Y4e4kqzr7w4p9aSvGirXi6XmeXNA.ttf

20 ms

gk5FxslNkTTHtojXrkp-xAfzRY4x1pTcKIDzdDtazqHr7w4p9aSvGirXi6XmeXNA.ttf

gk5FxslNkTTHtojXrkp-xAfzRY4x1pTcKIDzdDtazqHr7w4p9aSvGirXi6XmeXNA.ttf

87 ms

gk5FxslNkTTHtojXrkp-xGtXp_56cyzG87rk01y3A5nr7w4p9aSvGirXi6XmeXNA.ttf

gk5FxslNkTTHtojXrkp-xGtXp_56cyzG87rk01y3A5nr7w4p9aSvGirXi6XmeXNA.ttf

29 ms

ga.js

ga.js

15 ms

__utm.gif

__utm.gif

34 ms

buttons_sprite.png

buttons_sprite.png

1596 ms

up-arrow.png

up-arrow.png

1612 ms

__utm.gif

__utm.gif

14 ms

Accessibility Review

q2e.at accessibility score

98

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

Links do not have a discernible name

Best Practices

q2e.at 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

SEO Factors

q2e.at 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

    N/A

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Q2e.at 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 Q2e.at main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

q2e.at

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