Report Summary

  • 43

    Performance

    Renders faster than
    62% of other websites

  • 74

    Accessibility

    Visual factors better than
    that of 40% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

adzine.de

ADZINE - Magazin für Media. Marketing. Technologie.

Page Load Speed

9.4 sec in total

First Response

353 ms

Resources Loaded

9 sec

Page Rendered

99 ms

adzine.de screenshot

About Website

Welcome to adzine.de homepage info - get ready to check ADZINE best content for Switzerland right away, or after learning these important things about adzine.de

Die wichtigsten Themen aus Digital Marketing, Advertising und Technologie

Visit adzine.de

Key Findings

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

Performance Metrics

adzine.de performance score

43

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.3 s

18/100

10%

LCP (Largest Contentful Paint)

Value5.1 s

25/100

25%

SI (Speed Index)

Value11.3 s

5/100

10%

TBT (Total Blocking Time)

Value520 ms

56/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value9.3 s

31/100

10%

Network Requests Diagram

adzine.de

353 ms

adzine.de

388 ms

www.adzine.de

6541 ms

base.css

97 ms

font-awesome.min.css

188 ms

Our browser made a total of 98 requests to load all elements on the main page. We found that 76% of them (74 requests) were addressed to the original Adzine.de, 8% (8 requests) were made to Adfarm1.adition.com and 8% (8 requests) were made to Th.adzine.de. The less responsive or slowest element that took the longest time to load (6.5 sec) belongs to the original domain Adzine.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 437.1 kB (27%)

Content Size

1.6 MB

After Optimization

1.2 MB

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

HTML Optimization

-83%

Potential reduce by 97.2 kB

  • Original 117.4 kB
  • After minification 105.7 kB
  • After compression 20.2 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 97.2 kB or 83% of the original size.

Image Optimization

-3%

Potential reduce by 30.7 kB

  • Original 1.0 MB
  • After minification 989.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. ADZINE images are well optimized though.

JavaScript Optimization

-70%

Potential reduce by 302.0 kB

  • Original 430.9 kB
  • After minification 430.9 kB
  • After compression 128.9 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 302.0 kB or 70% of the original size.

CSS Optimization

-22%

Potential reduce by 7.1 kB

  • Original 32.8 kB
  • After minification 32.8 kB
  • After compression 25.6 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. Adzine.de needs all CSS files to be minified and compressed as it can save up to 7.1 kB or 22% of the original size.

Requests Breakdown

Number of requests can be reduced by 22 (23%)

Requests Now

94

After Optimization

72

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

Accessibility Review

adzine.de accessibility score

74

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

adzine.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

High

Page has valid source maps

SEO Factors

adzine.de SEO score

85

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 uses legible font sizes

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 Adzine.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 Adzine.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 ADZINE. 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: