Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 74

    Accessibility

    Visual factors better than
    that of 41% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 91

    SEO

    Google-friendlier than
    71% of websites

oxb2.de

3d Visualisierung, Konzeption & Design, PreisWERT von PerspektiveEins

Page Load Speed

2 sec in total

First Response

517 ms

Resources Loaded

1.3 sec

Page Rendered

196 ms

oxb2.de screenshot

About Website

Welcome to oxb2.de homepage info - get ready to check Oxb 2 best content for Indonesia right away, or after learning these important things about oxb2.de

Brilliante 3D Visualisierung, fotorealistische Architekturvisualisierung, Messestanddesign oder Produktpräsentation, wir bringen Ihr Projekt zum Glänzen.

Visit oxb2.de

Key Findings

We analyzed Oxb2.de page load time and found that the first response time was 517 ms and then it took 1.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.

Performance Metrics

oxb2.de performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.3 s

7/100

10%

LCP (Largest Contentful Paint)

Value11.7 s

0/100

25%

SI (Speed Index)

Value14.5 s

1/100

10%

TBT (Total Blocking Time)

Value2,360 ms

5/100

30%

CLS (Cumulative Layout Shift)

Value0.109

87/100

15%

TTI (Time to Interactive)

Value16.9 s

5/100

10%

Network Requests Diagram

oxb2.de

517 ms

cssloader.php

200 ms

jsloader.php

394 ms

jsloader.php

407 ms

jsloader.php

582 ms

Our browser made a total of 19 requests to load all elements on the main page. We found that all of those requests were addressed to Oxb2.de and no external sources were called. The less responsive or slowest element that took the longest time to load (582 ms) belongs to the original domain Oxb2.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 26.3 kB (45%)

Content Size

58.3 kB

After Optimization

32.0 kB

In fact, the total size of Oxb2.de main page is 58.3 kB. 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 10% of websites need less resources to load. Images take 35.8 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 7.8 kB

  • Original 10.4 kB
  • After minification 10.1 kB
  • After compression 2.6 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 7.8 kB or 75% of the original size.

Image Optimization

-24%

Potential reduce by 8.6 kB

  • Original 35.8 kB
  • After minification 27.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, Oxb 2 needs image optimization as it can save up to 8.6 kB or 24% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

CSS Optimization

-82%

Potential reduce by 9.9 kB

  • Original 12.0 kB
  • After minification 8.5 kB
  • After compression 2.1 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. Oxb2.de needs all CSS files to be minified and compressed as it can save up to 9.9 kB or 82% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

15

After Optimization

15

The browser has sent 15 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Oxb 2. According to our analytics all requests are already optimized.

Accessibility Review

oxb2.de accessibility score

74

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

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.

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

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

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

oxb2.de best practices score

75

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

oxb2.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 Oxb2.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 Oxb2.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

Open Graph description is not detected on the main page of Oxb 2. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: