Report Summary

  • 42

    Performance

    Renders faster than
    61% of other websites

  • 76

    Accessibility

    Visual factors better than
    that of 42% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

qbit.hr

Qbit - digital design, development and marketing agency

Page Load Speed

9.7 sec in total

First Response

1.7 sec

Resources Loaded

7.6 sec

Page Rendered

378 ms

qbit.hr screenshot

About Website

Visit qbit.hr now to see the best up-to-date Qbit content and also check out these interesting facts you probably never knew about qbit.hr

Design & development agency, building mobile and web solutions, online marketing and product design

Visit qbit.hr

Key Findings

We analyzed Qbit.hr page load time and found that the first response time was 1.7 sec and then it took 8 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

qbit.hr performance score

42

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.4 s

70/100

10%

LCP (Largest Contentful Paint)

Value9.1 s

1/100

25%

SI (Speed Index)

Value9.2 s

13/100

10%

TBT (Total Blocking Time)

Value530 ms

55/100

30%

CLS (Cumulative Layout Shift)

Value0.005

100/100

15%

TTI (Time to Interactive)

Value10.4 s

24/100

10%

Network Requests Diagram

qbit.hr

1693 ms

qbit.hr

1995 ms

css

30 ms

lazysizes.min.js

44 ms

global

653 ms

Our browser made a total of 24 requests to load all elements on the main page. We found that 79% of them (19 requests) were addressed to the original Qbit.hr, 13% (3 requests) were made to Fonts.gstatic.com and 4% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (3.8 sec) belongs to the original domain Qbit.hr.

Page Optimization Overview & Recommendations

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

Content Size

1.2 MB

After Optimization

51.7 kB

In fact, the total size of Qbit.hr main page is 1.2 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. 60% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 25.0 kB

  • Original 33.8 kB
  • After minification 30.7 kB
  • After compression 8.8 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 25.0 kB or 74% of the original size.

Image Optimization

-98%

Potential reduce by 1.2 MB

  • Original 1.2 MB
  • After minification 18.2 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. Obviously, Qbit needs image optimization as it can save up to 1.2 MB or 98% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-4%

Potential reduce by 1.0 kB

  • Original 25.8 kB
  • After minification 25.8 kB
  • After compression 24.8 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 4 (25%)

Requests Now

16

After Optimization

12

The browser has sent 16 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Qbit. 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.

Accessibility Review

qbit.hr accessibility score

76

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

qbit.hr best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

qbit.hr SEO score

92

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

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 Qbit.hr 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 Qbit.hr 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 Qbit. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: