Tools & Wizards About Us
m.e-kwiaty.pl screenshot

Report Summary

  • 26

    Performance

    Renders faster than
    45% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 86% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

m.e-kwiaty.pl

Kwiaciarnia Internetowa - Poczta i Dostawa Kwiatowa w 24h - E-kwiaty

Page Load Speed

3.4 sec in total

First Response

348 ms

Resources Loaded

2.5 sec

Page Rendered

531 ms

m.e-kwiaty.pl screenshot

About Website

Visit m.e-kwiaty.pl now to see the best up-to-date M E Kwiaty content for India and also check out these interesting facts you probably never knew about m.e-kwiaty.pl

Wejdź i zamów kwiaty przez internet lub telefon. Dostawa pocztą - Ekspresem kwiatowym nawet w dniu zamówienia. Wyślij piękny bukiet z E-kwiaty!

Visit m.e-kwiaty.pl

Key Findings

We analyzed M.e-kwiaty.pl page load time and found that the first response time was 348 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

m.e-kwiaty.pl performance score

26

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.6 s

31/100

10%

LCP (Largest Contentful Paint)

Value11.0 s

0/100

25%

SI (Speed Index)

Value8.6 s

17/100

10%

TBT (Total Blocking Time)

Value1,270 ms

19/100

30%

CLS (Cumulative Layout Shift)

Value0.098

90/100

15%

TTI (Time to Interactive)

Value12.4 s

15/100

10%

Network Requests Diagram

m.e-kwiaty.pl

348 ms

www.e-kwiaty.pl

1048 ms

gtm.js

71 ms

uc.js

39 ms

css2

33 ms

Our browser made a total of 28 requests to load all elements on the main page. We found that 4% of them (1 request) were addressed to the original M.e-kwiaty.pl, 61% (17 requests) were made to E-kwiaty.pl and 21% (6 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source E-kwiaty.pl.

Page Optimization Overview & Recommendations

Page size can be reduced by 528.0 kB (56%)

Content Size

942.1 kB

After Optimization

414.1 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of M.e-kwiaty.pl main page is 942.1 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. 35% of websites need less resources to load. HTML takes 514.2 kB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 440.1 kB

  • Original 514.2 kB
  • After minification 514.2 kB
  • After compression 74.1 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 440.1 kB or 86% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 164.5 kB
  • After minification 164.5 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. M E Kwiaty images are well optimized though.

JavaScript Optimization

-33%

Potential reduce by 87.9 kB

  • Original 263.5 kB
  • After minification 263.5 kB
  • After compression 175.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 87.9 kB or 33% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

20

After Optimization

20

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 20 CSS, Javascripts, AJAX and image requests in order to completely render the main page of M E Kwiaty. According to our analytics all requests are already optimized.

Network Requests Diagram

m.e-kwiaty.pl

m.e-kwiaty.pl

348 ms

www.e-kwiaty.pl

www.e-kwiaty.pl

1048 ms

gtm.js

gtm.js

71 ms

uc.js

uc.js

39 ms

css2

css2

33 ms

main_page.display.min_20240809094938.js

main_page.display.min_20240809094938.js

343 ms

0.gif

0.gif

381 ms

ekomi_logo.png

ekomi_logo.png

57 ms

597-mwggqm-lplb.png

597-mwggqm-lplb.png

448 ms

597-mwggqm-rwwv.png

597-mwggqm-rwwv.png

435 ms

601-ibhdqz-gxkd.png

601-ibhdqz-gxkd.png

455 ms

601-ibhdqz-lefo.png

601-ibhdqz-lefo.png

469 ms

602-qrzusr-mwzy.png

602-qrzusr-mwzy.png

400 ms

602-qrzusr-cdaq.png

602-qrzusr-cdaq.png

552 ms

603-nxuyfs-jivx.png

603-nxuyfs-jivx.png

519 ms

603-nxuyfs-bwtt.png

603-nxuyfs-bwtt.png

544 ms

S6uyw4BMUTPHvxo.woff

S6uyw4BMUTPHvxo.woff

30 ms

S6u9w4BMUTPHh7USeww.woff

S6u9w4BMUTPHh7USeww.woff

91 ms

S6u9w4BMUTPHh6UVeww.woff

S6u9w4BMUTPHh6UVeww.woff

106 ms

S6u9w4BMUTPHh50Xeww.woff

S6u9w4BMUTPHh50Xeww.woff

107 ms

epmobile_animated.gif

epmobile_animated.gif

1135 ms

ppromo_txt.png

ppromo_txt.png

537 ms

coupon.png

coupon.png

554 ms

logo.png

logo.png

606 ms

close.png

close.png

620 ms

MaterialIcons-Regular.woff

MaterialIcons-Regular.woff

848 ms

S6u8w4BMUTPHjxswWA.woff

S6u8w4BMUTPHjxswWA.woff

14 ms

S6u_w4BMUTPHjxsI3wiPHw.woff

S6u_w4BMUTPHjxsI3wiPHw.woff

15 ms

Accessibility Review

m.e-kwiaty.pl accessibility score

95

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 input fields do not have accessible names

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

Links do not have a discernible name

Best Practices

m.e-kwiaty.pl best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

m.e-kwiaty.pl SEO score

92

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

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 M.e-kwiaty.pl 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 M.e-kwiaty.pl 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

m.e-kwiaty.pl

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