Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 57% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 99

    SEO

    Google-friendlier than
    93% of websites

ibelsa.com

ibelsa cloudbasierte Hotelsoftware, PMS digitale Hotels

Page Load Speed

2.9 sec in total

First Response

314 ms

Resources Loaded

2.3 sec

Page Rendered

250 ms

ibelsa.com screenshot

About Website

Click here to check amazing Ibelsa content for Germany. Otherwise, check out these important facts you probably never knew about ibelsa.com

ibelsa, die cloudbasierte Hotelsoftware für das Hotel deiner Zukunft. Digital, schnell, sicher, persönlicher Support und alles in einer Cloud.

Visit ibelsa.com

Key Findings

We analyzed Ibelsa.com page load time and found that the first response time was 314 ms and then it took 2.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

ibelsa.com performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.5 s

2/100

10%

LCP (Largest Contentful Paint)

Value30.8 s

0/100

25%

SI (Speed Index)

Value18.5 s

0/100

10%

TBT (Total Blocking Time)

Value3,070 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value20.6 s

2/100

10%

Network Requests Diagram

ibelsa.com

314 ms

124 ms

merged-f761f4704fd14aa60e93983b68794986-faaa8537d8a19cfe7f059edc303b8748.css.gzip

101 ms

screen-7de24cbcfd4c1f9d943ef21ae0040f5d.css.gzip

187 ms

colorbox-582d182decb11505344ec6bcac2f9d97.css.gzip

197 ms

Our browser made a total of 69 requests to load all elements on the main page. We found that 93% of them (64 requests) were addressed to the original Ibelsa.com, 4% (3 requests) were made to Fonts.gstatic.com and 1% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (791 ms) belongs to the original domain Ibelsa.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 163.0 kB (23%)

Content Size

723.5 kB

After Optimization

560.5 kB

In fact, the total size of Ibelsa.com main page is 723.5 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. 50% of websites need less resources to load. Images take 560.0 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 22.2 kB

  • Original 28.8 kB
  • After minification 27.9 kB
  • After compression 6.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 22.2 kB or 77% of the original size.

Image Optimization

-4%

Potential reduce by 24.9 kB

  • Original 560.0 kB
  • After minification 535.1 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. Ibelsa images are well optimized though.

CSS Optimization

-86%

Potential reduce by 115.8 kB

  • Original 134.7 kB
  • After minification 133.4 kB
  • After compression 18.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. Ibelsa.com needs all CSS files to be minified and compressed as it can save up to 115.8 kB or 86% of the original size.

Requests Breakdown

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

Requests Now

63

After Optimization

33

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

Accessibility Review

ibelsa.com accessibility score

84

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

Links do not have a discernible name

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

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

High

Page has valid source maps

SEO Factors

ibelsa.com SEO score

99

Search Engine Optimization Advices

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

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ibelsa.com 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 Ibelsa.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 description is not detected on the main page of Ibelsa. 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: