Report Summary

  • 29

    Performance

    Renders faster than
    49% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 46% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

flowerstory.pl

Kwiaciarnia Internetowa Kraków, Kwiaty i Bukiety z Dostawą - FlowerStory.pl

Page Load Speed

11.2 sec in total

First Response

1.5 sec

Resources Loaded

6.9 sec

Page Rendered

2.8 sec

flowerstory.pl screenshot

About Website

Click here to check amazing Flower Story content for Poland. Otherwise, check out these important facts you probably never knew about flowerstory.pl

Zamawiaj najpiękniejsze kwiaty z darmową dostawą na terenie Krakowa w naszej kwiaciarni internetowej!

Visit flowerstory.pl

Key Findings

We analyzed Flowerstory.pl page load time and found that the first response time was 1.5 sec and then it took 9.7 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

flowerstory.pl performance score

29

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

44/100

10%

LCP (Largest Contentful Paint)

Value9.6 s

0/100

25%

SI (Speed Index)

Value8.5 s

18/100

10%

TBT (Total Blocking Time)

Value1,120 ms

23/100

30%

CLS (Cumulative Layout Shift)

Value0.003

100/100

15%

TTI (Time to Interactive)

Value14.9 s

8/100

10%

Network Requests Diagram

www.flowerstory.pl

1473 ms

bootstrap.css

329 ms

37af751af12eb53bb8439948f68bd7d9_all.css

342 ms

skin.css

227 ms

2c33ebbaa5742718f7f77505f441937c.js

440 ms

Our browser made a total of 206 requests to load all elements on the main page. We found that 73% of them (150 requests) were addressed to the original Flowerstory.pl, 12% (24 requests) were made to Static.xx.fbcdn.net and 10% (21 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Flowerstory.pl.

Page Optimization Overview & Recommendations

Page size can be reduced by 446.5 kB (8%)

Content Size

5.3 MB

After Optimization

4.8 MB

In fact, the total size of Flowerstory.pl main page is 5.3 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. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 4.8 MB which makes up the majority of the site volume.

HTML Optimization

-89%

Potential reduce by 157.9 kB

  • Original 178.4 kB
  • After minification 178.3 kB
  • After compression 20.5 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 157.9 kB or 89% of the original size.

Image Optimization

-2%

Potential reduce by 85.3 kB

  • Original 4.8 MB
  • After minification 4.7 MB

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. Flower Story images are well optimized though.

JavaScript Optimization

-68%

Potential reduce by 203.3 kB

  • Original 299.5 kB
  • After minification 297.0 kB
  • After compression 96.2 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 203.3 kB or 68% of the original size.

Requests Breakdown

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

Requests Now

204

After Optimization

164

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

Accessibility Review

flowerstory.pl accessibility score

78

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

flowerstory.pl best practices score

67

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

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

flowerstory.pl SEO score

92

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

High

Tap targets are not sized appropriately

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

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