Report Summary

  • 16

    Performance

    Renders faster than
    35% of other websites

  • 73

    Accessibility

    Visual factors better than
    that of 48% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    29% of websites

  • 50

    SEO

    Google-friendlier than
    28% of websites

mazine.ws

MAzine | Exploring the potential of networked media

Page Load Speed

5.2 sec in total

First Response

1.6 sec

Resources Loaded

3.2 sec

Page Rendered

357 ms

mazine.ws screenshot

About Website

Click here to check amazing MAzine content. Otherwise, check out these important facts you probably never knew about mazine.ws

Visit mazine.ws

Key Findings

We analyzed Mazine.ws page load time and found that the first response time was 1.6 sec and then it took 3.6 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

mazine.ws performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

38/100

10%

LCP (Largest Contentful Paint)

Value14.0 s

0/100

25%

SI (Speed Index)

Value9.1 s

13/100

10%

TBT (Total Blocking Time)

Value1,750 ms

10/100

30%

CLS (Cumulative Layout Shift)

Value0.274

44/100

15%

TTI (Time to Interactive)

Value13.8 s

10/100

10%

Network Requests Diagram

mazine.ws

1582 ms

node.css

211 ms

defaults.css

213 ms

system.css

215 ms

system-menus.css

215 ms

Our browser made a total of 45 requests to load all elements on the main page. We found that 64% of them (29 requests) were addressed to the original Mazine.ws, 9% (4 requests) were made to Pagead2.googlesyndication.com and 4% (2 requests) were made to Googleads.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Mazine.ws.

Page Optimization Overview & Recommendations

Page size can be reduced by 490.4 kB (49%)

Content Size

1.0 MB

After Optimization

520.2 kB

In fact, the total size of Mazine.ws main page is 1.0 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. 40% of websites need less resources to load. Javascripts take 363.6 kB which makes up the majority of the site volume.

HTML Optimization

-73%

Potential reduce by 17.1 kB

  • Original 23.5 kB
  • After minification 23.0 kB
  • After compression 6.4 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 17.1 kB or 73% of the original size.

Image Optimization

-5%

Potential reduce by 18.5 kB

  • Original 353.6 kB
  • After minification 335.2 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. MAzine images are well optimized though.

JavaScript Optimization

-64%

Potential reduce by 232.5 kB

  • Original 363.6 kB
  • After minification 355.2 kB
  • After compression 131.1 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 232.5 kB or 64% of the original size.

CSS Optimization

-82%

Potential reduce by 222.4 kB

  • Original 269.9 kB
  • After minification 262.4 kB
  • After compression 47.5 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. Mazine.ws needs all CSS files to be minified and compressed as it can save up to 222.4 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 20 (49%)

Requests Now

41

After Optimization

21

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

Accessibility Review

mazine.ws accessibility score

73

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

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

<object> elements do not have alternate text

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

mazine.ws best practices score

58

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

Browser errors were logged to the console

SEO Factors

mazine.ws SEO score

50

Search Engine Optimization Advices

Content Best Practices

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

Impact

Issue

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

High

Document uses plugins

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Mazine.ws can be misinterpreted by Google and other search engines. Our service has detected that English 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 Mazine.ws 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 MAzine. 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: