Report Summary

  • 28

    Performance

    Renders faster than
    48% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 76

    SEO

    Google-friendlier than
    35% of websites

phi.de

Öko Rechenzentrum | phi -wir leben green IT

Page Load Speed

3.7 sec in total

First Response

271 ms

Resources Loaded

2.8 sec

Page Rendered

579 ms

phi.de screenshot

About Website

Welcome to phi.de homepage info - get ready to check Phi best content right away, or after learning these important things about phi.de

Nachhaltiges Hosting mit Zukunft: Dank Green IT, hochskalierbarer Lösungen und bester Sicherheit für ihr Unternehmen. Öko Rechenzentrum im Herzen Jülichs.

Visit phi.de

Key Findings

We analyzed Phi.de page load time and found that the first response time was 271 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

phi.de performance score

28

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.6 s

64/100

10%

LCP (Largest Contentful Paint)

Value9.1 s

1/100

25%

SI (Speed Index)

Value8.8 s

15/100

10%

TBT (Total Blocking Time)

Value610 ms

48/100

30%

CLS (Cumulative Layout Shift)

Value0.393

26/100

15%

TTI (Time to Interactive)

Value11.8 s

17/100

10%

Network Requests Diagram

phi.de

271 ms

phi.de

641 ms

1453488395.js

175 ms

173941256.js

356 ms

animate.min.css

273 ms

Our browser made a total of 105 requests to load all elements on the main page. We found that 70% of them (73 requests) were addressed to the original Phi.de, 30% (32 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (921 ms) belongs to the original domain Phi.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 638.5 kB (28%)

Content Size

2.3 MB

After Optimization

1.6 MB

In fact, the total size of Phi.de main page is 2.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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 532.9 kB

  • Original 606.5 kB
  • After minification 601.8 kB
  • After compression 73.7 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 532.9 kB or 88% of the original size.

Image Optimization

-3%

Potential reduce by 30.3 kB

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

JavaScript Optimization

-15%

Potential reduce by 58.1 kB

  • Original 375.8 kB
  • After minification 375.8 kB
  • After compression 317.6 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.1 kB or 15% of the original size.

CSS Optimization

-19%

Potential reduce by 17.2 kB

  • Original 90.1 kB
  • After minification 90.1 kB
  • After compression 72.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. Phi.de needs all CSS files to be minified and compressed as it can save up to 17.2 kB or 19% of the original size.

Requests Breakdown

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

Requests Now

70

After Optimization

23

The browser has sent 70 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Phi. 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 18 to 1 for CSS and as a result speed up the page load time.

Accessibility Review

phi.de accessibility score

82

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

Image elements do not have [alt] attributes

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

phi.de best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

phi.de SEO score

76

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

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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 doesn't use 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 Phi.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 Phi.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 data is detected on the main page of Phi. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: