Tools & Wizards About Us
centrope.com screenshot

Report Summary

  • 50

    Performance

    Renders faster than
    68% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 66% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 78

    SEO

    Google-friendlier than
    39% of websites

centrope.com

Centrope - grenzüberschreitende Zusammenarbeit zwischen Österreich, Ungarn, Slowakei und Tschechien

Page Load Speed

3.4 sec in total

First Response

385 ms

Resources Loaded

2.8 sec

Page Rendered

163 ms

centrope.com screenshot

About Website

Click here to check amazing Centrope content. Otherwise, check out these important facts you probably never knew about centrope.com

Centrope (Central Europe) ist ein Zusammenschluss mehrerer Regionen zwischen Österreich, Ungarn, Slowakei und Tschechien über die nationalen Grenzen hinweg.

Visit centrope.com

Key Findings

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

Performance Metrics

centrope.com performance score

50

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.6 s

5/100

10%

LCP (Largest Contentful Paint)

Value7.4 s

4/100

25%

SI (Speed Index)

Value8.5 s

18/100

10%

TBT (Total Blocking Time)

Value110 ms

98/100

30%

CLS (Cumulative Layout Shift)

Value0.098

90/100

15%

TTI (Time to Interactive)

Value8.4 s

39/100

10%

Network Requests Diagram

centrope.com

385 ms

centrope.html

553 ms

vie-resp.css

208 ms

responsive2.css

313 ms

jquery-ui.min.css

334 ms

Our browser made a total of 54 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Centrope.com, 91% (49 requests) were made to Wien.gv.at and 4% (2 requests) were made to Ssl-wiengvat.oewabox.at. The less responsive or slowest element that took the longest time to load (898 ms) relates to the external source Wien.gv.at.

Page Optimization Overview & Recommendations

Page size can be reduced by 62.1 kB (18%)

Content Size

348.1 kB

After Optimization

286.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Centrope.com main page is 348.1 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. 30% of websites need less resources to load. Javascripts take 214.3 kB which makes up the majority of the site volume.

HTML Optimization

-73%

Potential reduce by 29.6 kB

  • Original 40.5 kB
  • After minification 38.4 kB
  • After compression 11.0 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 29.6 kB or 73% of the original size.

Image Optimization

-9%

Potential reduce by 2.5 kB

  • Original 27.8 kB
  • After minification 25.4 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. Centrope images are well optimized though.

JavaScript Optimization

-5%

Potential reduce by 10.3 kB

  • Original 214.3 kB
  • After minification 214.3 kB
  • After compression 204.0 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

-30%

Potential reduce by 19.7 kB

  • Original 65.5 kB
  • After minification 65.5 kB
  • After compression 45.8 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. Centrope.com needs all CSS files to be minified and compressed as it can save up to 19.7 kB or 30% of the original size.

Requests Breakdown

Number of requests can be reduced by 41 (80%)

Requests Now

51

After Optimization

10

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

centrope.com

centrope.com

385 ms

centrope.html

centrope.html

553 ms

vie-resp.css

vie-resp.css

208 ms

responsive2.css

responsive2.css

313 ms

jquery-ui.min.css

jquery-ui.min.css

334 ms

wienvideo.css

wienvideo.css

374 ms

modernizr.custom.vie.js

modernizr.custom.vie.js

336 ms

jquery-1.11.3.min.js

jquery-1.11.3.min.js

439 ms

jquery-migrate-1.2.1.min.js

jquery-migrate-1.2.1.min.js

336 ms

jquery-ui.min.js

jquery-ui.min.js

518 ms

flashcheck.js

flashcheck.js

435 ms

videolanguage_DE.js

videolanguage_DE.js

436 ms

jwplayer.js

jwplayer.js

600 ms

jquery.wienvideo.js

jquery.wienvideo.js

547 ms

vidembedding.js

vidembedding.js

557 ms

audembedding.js

audembedding.js

579 ms

swfobject.js

swfobject.js

547 ms

audiofunctions.js

audiofunctions.js

618 ms

de-at.js

de-at.js

619 ms

datepicker.js

datepicker.js

643 ms

responsive.js

responsive.js

670 ms

languages-de.js

languages-de.js

690 ms

articfunc.js

articfunc.js

695 ms

jquery.tabs.js

jquery.tabs.js

719 ms

wat-tabs.js

wat-tabs.js

720 ms

vie-sticky-nav.js

vie-sticky-nav.js

744 ms

jquery.jcarousel.js

jquery.jcarousel.js

760 ms

wat-carousel.js

wat-carousel.js

782 ms

jquery.cookie.js

jquery.cookie.js

797 ms

bezirksfunc.js

bezirksfunc.js

820 ms

wat-ahstoggle.js

wat-ahstoggle.js

820 ms

jquery.biggerlink.js

jquery.biggerlink.js

845 ms

jquery.afontsize.js

jquery.afontsize.js

861 ms

logout_wienat.js

logout_wienat.js

881 ms

focusfix.js

focusfix.js

898 ms

logo-wien.at.png

logo-wien.at.png

327 ms

icons-head.png

icons-head.png

328 ms

button-suche.gif

button-suche.gif

329 ms

ma27-klein.jpg

ma27-klein.jpg

331 ms

logo-stadt-wien.png

logo-stadt-wien.png

335 ms

icon-facebook.png

icon-facebook.png

352 ms

icon-toplink.gif

icon-toplink.gif

375 ms

icon-sprites.png

icon-sprites.png

364 ms

centrope.html

centrope.html

711 ms

piwik.js

piwik.js

517 ms

vconfig_154784.js

vconfig_154784.js

212 ms

ui-bg_flat_75_ffffff_40x100.png

ui-bg_flat_75_ffffff_40x100.png

114 ms

ui-bg_glass_75_e6e6e6_1x400.png

ui-bg_glass_75_e6e6e6_1x400.png

130 ms

icons-artikelfunktionen.png

icons-artikelfunktionen.png

154 ms

jwpsrv.js

jwpsrv.js

136 ms

ui-icons_888888_256x240.png

ui-icons_888888_256x240.png

108 ms

logo.png

logo.png

33 ms

piwik.php

piwik.php

456 ms

blank.gif

blank.gif

103 ms

Accessibility Review

centrope.com accessibility score

87

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-hidden="true"] elements contain focusable descendents

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

Best Practices

centrope.com best practices score

67

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

SEO Factors

centrope.com SEO score

78

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

High

robots.txt is not valid

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

    ISO-8859-1

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

centrope.com

Open Graph description is not detected on the main page of Centrope. 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: