Tools & Wizards About Us
mayyer.com screenshot

Report Summary

  • 38

    Performance

    Renders faster than
    57% of other websites

  • 68

    Accessibility

    Visual factors better than
    that of 33% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

mayyer.com

MAYYER.PL – Strony www, sklepy internetowe, grafika reklamowa

Page Load Speed

3.5 sec in total

First Response

377 ms

Resources Loaded

3 sec

Page Rendered

122 ms

mayyer.com screenshot

About Website

Welcome to mayyer.com homepage info - get ready to check MAYYER best content right away, or after learning these important things about mayyer.com

Visit mayyer.com

Key Findings

We analyzed Mayyer.com page load time and found that the first response time was 377 ms and then it took 3.1 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

mayyer.com performance score

38

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.1 s

1/100

10%

LCP (Largest Contentful Paint)

Value7.2 s

5/100

25%

SI (Speed Index)

Value7.9 s

23/100

10%

TBT (Total Blocking Time)

Value230 ms

87/100

30%

CLS (Cumulative Layout Shift)

Value0.402

25/100

15%

TTI (Time to Interactive)

Value8.1 s

41/100

10%

Network Requests Diagram

mayyer.com

377 ms

www.mayyer.pl

453 ms

mayyer.pl

613 ms

style.min.css

214 ms

full-styles.6.10.2.css

420 ms

Our browser made a total of 49 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Mayyer.com, 59% (29 requests) were made to Mayyer.pl and 37% (18 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (774 ms) relates to the external source Mayyer.pl.

Page Optimization Overview & Recommendations

Page size can be reduced by 72.5 kB (12%)

Content Size

602.8 kB

After Optimization

530.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Mayyer.com main page is 602.8 kB. 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 213.1 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 51.1 kB

  • Original 64.3 kB
  • After minification 63.4 kB
  • After compression 13.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 51.1 kB or 80% of the original size.

Image Optimization

-9%

Potential reduce by 18.7 kB

  • Original 213.1 kB
  • After minification 194.3 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. MAYYER images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 1.7 kB

  • Original 150.4 kB
  • After minification 150.4 kB
  • After compression 148.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. This website has mostly compressed JavaScripts.

CSS Optimization

-1%

Potential reduce by 980 B

  • Original 175.1 kB
  • After minification 175.1 kB
  • After compression 174.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. Mayyer.com has all CSS files already compressed.

Requests Breakdown

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

Requests Now

26

After Optimization

6

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

mayyer.com

mayyer.com

377 ms

www.mayyer.pl

www.mayyer.pl

453 ms

mayyer.pl

mayyer.pl

613 ms

style.min.css

style.min.css

214 ms

full-styles.6.10.2.css

full-styles.6.10.2.css

420 ms

mkhb-render.css

mkhb-render.css

321 ms

mkhb-row.css

mkhb-row.css

325 ms

mkhb-column.css

mkhb-column.css

325 ms

js_composer.min.css

js_composer.min.css

566 ms

theme-options-production-1665160381.css

theme-options-production-1665160381.css

338 ms

shortcodes-styles.min.css

shortcodes-styles.min.css

540 ms

webfontloader.js

webfontloader.js

433 ms

jquery.min.js

jquery.min.js

565 ms

jquery-migrate.min.js

jquery-migrate.min.js

448 ms

animate.min.css

animate.min.css

421 ms

v4-shims.min.css

v4-shims.min.css

462 ms

all.min.css

all.min.css

462 ms

smoothscroll.js

smoothscroll.js

537 ms

full-scripts.6.10.2.js

full-scripts.6.10.2.js

774 ms

mkhb-render.js

mkhb-render.js

546 ms

mkhb-column.js

mkhb-column.js

547 ms

shortcodes-scripts.min.js

shortcodes-scripts.min.js

665 ms

js_composer_front.min.js

js_composer_front.min.js

666 ms

vc-waypoints.min.js

vc-waypoints.min.js

667 ms

css

css

73 ms

logo-2-pvicvverpycu0k7k3gujntad85i1z6hdi0z8yzt70g.png

logo-2-pvicvverpycu0k7k3gujntad85i1z6hdi0z8yzt70g.png

143 ms

doswiadczenie.png

doswiadczenie.png

433 ms

klienci-loga.png

klienci-loga.png

393 ms

generate-captcha.php

generate-captcha.php

141 ms

pxiEyp8kv8JHgFVrJJnedw.ttf

pxiEyp8kv8JHgFVrJJnedw.ttf

38 ms

pxiByp8kv8JHgFVrLGT9Z1JlEA.ttf

pxiByp8kv8JHgFVrLGT9Z1JlEA.ttf

50 ms

pxiByp8kv8JHgFVrLDz8Z1JlEA.ttf

pxiByp8kv8JHgFVrLDz8Z1JlEA.ttf

49 ms

pxiByp8kv8JHgFVrLFj_Z1JlEA.ttf

pxiByp8kv8JHgFVrLFj_Z1JlEA.ttf

49 ms

pxiGyp8kv8JHgFVrLPTufntF.ttf

pxiGyp8kv8JHgFVrLPTufntF.ttf

47 ms

pxiByp8kv8JHgFVrLEj6Z1JlEA.ttf

pxiByp8kv8JHgFVrLEj6Z1JlEA.ttf

47 ms

pxiByp8kv8JHgFVrLCz7Z1JlEA.ttf

pxiByp8kv8JHgFVrLCz7Z1JlEA.ttf

49 ms

pxiByp8kv8JHgFVrLDD4Z1JlEA.ttf

pxiByp8kv8JHgFVrLDD4Z1JlEA.ttf

50 ms

pxiByp8kv8JHgFVrLBT5Z1JlEA.ttf

pxiByp8kv8JHgFVrLBT5Z1JlEA.ttf

50 ms

pxiAyp8kv8JHgFVrJJLmE0tMMPc.ttf

pxiAyp8kv8JHgFVrJJLmE0tMMPc.ttf

76 ms

pxiDyp8kv8JHgFVrJJLmv1pVGdeL.ttf

pxiDyp8kv8JHgFVrJJLmv1pVGdeL.ttf

76 ms

pxiDyp8kv8JHgFVrJJLm21lVGdeL.ttf

pxiDyp8kv8JHgFVrJJLm21lVGdeL.ttf

75 ms

pxiGyp8kv8JHgFVrJJLufntF.ttf

pxiGyp8kv8JHgFVrJJLufntF.ttf

76 ms

pxiDyp8kv8JHgFVrJJLmg1hVGdeL.ttf

pxiDyp8kv8JHgFVrJJLmg1hVGdeL.ttf

79 ms

pxiDyp8kv8JHgFVrJJLmr19VGdeL.ttf

pxiDyp8kv8JHgFVrJJLmr19VGdeL.ttf

79 ms

pxiDyp8kv8JHgFVrJJLmy15VGdeL.ttf

pxiDyp8kv8JHgFVrJJLmy15VGdeL.ttf

79 ms

pxiDyp8kv8JHgFVrJJLm111VGdeL.ttf

pxiDyp8kv8JHgFVrJJLm111VGdeL.ttf

79 ms

pxiDyp8kv8JHgFVrJJLm81xVGdeL.ttf

pxiDyp8kv8JHgFVrJJLm81xVGdeL.ttf

80 ms

fa-solid-900.woff

fa-solid-900.woff

332 ms

fa-regular-400.woff

fa-regular-400.woff

318 ms

Accessibility Review

mayyer.com accessibility score

68

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

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

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

mayyer.com SEO score

86

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

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

    PL

  • Language Claimed

    PL

  • Encoding

    UTF-8

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

mayyer.com

Open Graph description is not detected on the main page of MAYYER. 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: