Report Summary

  • 48

    Performance

    Renders faster than
    66% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

mazeberry.com

Today’s and tomorrow’s next-gen Data Platform | mediarithmics

Page Load Speed

7.4 sec in total

First Response

1.4 sec

Resources Loaded

5.7 sec

Page Rendered

327 ms

mazeberry.com screenshot

About Website

Welcome to mazeberry.com homepage info - get ready to check Mazeberry best content for Morocco right away, or after learning these important things about mazeberry.com

A sustainable and privacy-first next-Gen Data Platform to deliver advanced use cases for leading retail, media and broadcast players. We also provide you with the most advanced solutions for a cookiel...

Visit mazeberry.com

Key Findings

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

Performance Metrics

mazeberry.com performance score

48

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

58/100

10%

LCP (Largest Contentful Paint)

Value13.6 s

0/100

25%

SI (Speed Index)

Value4.2 s

77/100

10%

TBT (Total Blocking Time)

Value250 ms

84/100

30%

CLS (Cumulative Layout Shift)

Value0.238

52/100

15%

TTI (Time to Interactive)

Value11.6 s

18/100

10%

Network Requests Diagram

www.mazeberry.com

1407 ms

language-selector.css

194 ms

shortcodes.css

272 ms

flexslider.css

188 ms

basic.css

186 ms

Our browser made a total of 88 requests to load all elements on the main page. We found that 69% of them (61 requests) were addressed to the original Mazeberry.com, 8% (7 requests) were made to Fonts.gstatic.com and 3% (3 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Mazeberry.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 888.4 kB (55%)

Content Size

1.6 MB

After Optimization

713.4 kB

In fact, the total size of Mazeberry.com 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. 45% of websites need less resources to load. CSS take 547.2 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 48.2 kB

  • Original 60.9 kB
  • After minification 58.0 kB
  • After compression 12.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 48.2 kB or 79% of the original size.

Image Optimization

-12%

Potential reduce by 57.4 kB

  • Original 478.0 kB
  • After minification 420.6 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. Obviously, Mazeberry needs image optimization as it can save up to 57.4 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-62%

Potential reduce by 317.9 kB

  • Original 515.7 kB
  • After minification 497.1 kB
  • After compression 197.8 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 317.9 kB or 62% of the original size.

CSS Optimization

-85%

Potential reduce by 464.9 kB

  • Original 547.2 kB
  • After minification 460.2 kB
  • After compression 82.3 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. Mazeberry.com needs all CSS files to be minified and compressed as it can save up to 464.9 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 60 (79%)

Requests Now

76

After Optimization

16

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

Accessibility Review

mazeberry.com accessibility score

78

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

[role]s are not contained by their required parent element

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

[id] attributes on active, focusable elements are not unique

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

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

mazeberry.com 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

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

mazeberry.com SEO score

82

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    FR

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Mazeberry.com can be misinterpreted by Google and other search engines. Our service has detected that French is used on the page, and it does not match the claimed English language. Our system also found out that Mazeberry.com 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 Mazeberry. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: