Report Summary

  • 56

    Performance

    Renders faster than
    72% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 80

    SEO

    Google-friendlier than
    42% of websites

aycan.de

Innovative Lösungen für PACS und Patientenkommunikation seit 1996

Page Load Speed

3.7 sec in total

First Response

327 ms

Resources Loaded

3.1 sec

Page Rendered

314 ms

aycan.de screenshot

About Website

Visit aycan.de now to see the best up-to-date Aycan content for India and also check out these interesting facts you probably never knew about aycan.de

Wir bieten RIS/PACS aus einer Hand mit strukturierter Befundung, Spracherkennung, Teleradiologie und Patientenportal mit einem exzellenten Support.

Visit aycan.de

Key Findings

We analyzed Aycan.de page load time and found that the first response time was 327 ms and then it took 3.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

aycan.de performance score

56

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

50/100

10%

LCP (Largest Contentful Paint)

Value4.9 s

29/100

25%

SI (Speed Index)

Value7.0 s

32/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.753

6/100

15%

TTI (Time to Interactive)

Value3.1 s

95/100

10%

Network Requests Diagram

aycan.de

327 ms

www.aycan.de

324 ms

www.aycan.de

554 ms

merged-3005063b2c3fbb95ced215e7218a8f40-d0cda9191c9a2da6dacb878cb249261a.css.gzip

102 ms

jquery.min.js

402 ms

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

Page Optimization Overview & Recommendations

Page size can be reduced by 94.2 kB (7%)

Content Size

1.3 MB

After Optimization

1.2 MB

In fact, the total size of Aycan.de main page is 1.3 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. 30% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 35.2 kB

  • Original 42.8 kB
  • After minification 42.3 kB
  • After compression 7.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 35.2 kB or 82% of the original size.

Image Optimization

-0%

Potential reduce by 393 B

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

JavaScript Optimization

-48%

Potential reduce by 58.5 kB

  • Original 121.5 kB
  • After minification 121.5 kB
  • After compression 63.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 58.5 kB or 48% of the original size.

CSS Optimization

-1%

Potential reduce by 184 B

  • Original 12.3 kB
  • After minification 12.3 kB
  • After compression 12.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. Aycan.de has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 24 (47%)

Requests Now

51

After Optimization

27

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

Accessibility Review

aycan.de accessibility score

88

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.

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

aycan.de 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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

aycan.de SEO score

80

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

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Aycan.de can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and it does not match the claimed English language. Our system also found out that Aycan.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 Aycan. 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: