Report Summary

  • 35

    Performance

    Renders faster than
    55% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 66% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

qidenus.com

High-performance Book Scanners • Qidenus Technologies

Page Load Speed

6.7 sec in total

First Response

569 ms

Resources Loaded

5.7 sec

Page Rendered

442 ms

About Website

Visit qidenus.com now to see the best up-to-date Qidenus content for Austria and also check out these interesting facts you probably never knew about qidenus.com

Manufacturer of V-shaped Qidenus book scanners: scan A3, A3+, A2, A2+, A1; up to 1.000 ppi; up to 2.500 pages/hr; books up to 16 cm thick.

Visit qidenus.com

Key Findings

We analyzed Qidenus.com page load time and found that the first response time was 569 ms and then it took 6.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

qidenus.com performance score

35

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.7 s

5/100

10%

LCP (Largest Contentful Paint)

Value11.1 s

0/100

25%

SI (Speed Index)

Value10.3 s

8/100

10%

TBT (Total Blocking Time)

Value340 ms

75/100

30%

CLS (Cumulative Layout Shift)

Value0.211

59/100

15%

TTI (Time to Interactive)

Value10.3 s

25/100

10%

Network Requests Diagram

qidenus.com

569 ms

script.js

181 ms

js

68 ms

1de44d563420beb53c445107b96fd783.min.css

340 ms

frontend-gtag.min.js

331 ms

Our browser made a total of 29 requests to load all elements on the main page. We found that 76% of them (22 requests) were addressed to the original Qidenus.com, 14% (4 requests) were made to Maps.googleapis.com and 3% (1 request) were made to Cdn-cookieyes.com. The less responsive or slowest element that took the longest time to load (957 ms) belongs to the original domain Qidenus.com.

Page Optimization Overview & Recommendations

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

Content Size

2.0 MB

After Optimization

1.7 MB

In fact, the total size of Qidenus.com main page is 2.0 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.3 MB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 217.5 kB

  • Original 245.9 kB
  • After minification 244.2 kB
  • After compression 28.4 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 217.5 kB or 88% of the original size.

Image Optimization

-0%

Potential reduce by 2.2 kB

  • Original 1.3 MB
  • After minification 1.3 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. Qidenus images are well optimized though.

JavaScript Optimization

-10%

Potential reduce by 26.7 kB

  • Original 281.3 kB
  • After minification 281.3 kB
  • After compression 254.5 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.

CSS Optimization

-22%

Potential reduce by 32.2 kB

  • Original 145.1 kB
  • After minification 145.1 kB
  • After compression 112.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. Qidenus.com needs all CSS files to be minified and compressed as it can save up to 32.2 kB or 22% of the original size.

Requests Breakdown

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

Requests Now

23

After Optimization

16

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

Accessibility Review

qidenus.com accessibility score

87

Accessibility Issues

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

Image elements do not have [alt] attributes

Best Practices

qidenus.com 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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

qidenus.com SEO score

86

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

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

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