Report Summary

  • 30

    Performance

    Renders faster than
    50% of other websites

  • 74

    Accessibility

    Visual factors better than
    that of 40% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 80

    SEO

    Google-friendlier than
    42% of websites

magnoliastore.com

Magnolia Store - The collection contains over 800 magnolias!

Page Load Speed

2.7 sec in total

First Response

213 ms

Resources Loaded

2.2 sec

Page Rendered

240 ms

magnoliastore.com screenshot

About Website

Click here to check amazing Magnolia Store content for Ukraine. Otherwise, check out these important facts you probably never knew about magnoliastore.com

Welcome, on this website you will find more information about our company,and the database of the collection from Magnolia's.

Visit magnoliastore.com

Key Findings

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

Performance Metrics

magnoliastore.com performance score

30

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

34/100

10%

LCP (Largest Contentful Paint)

Value12.9 s

0/100

25%

SI (Speed Index)

Value8.0 s

22/100

10%

TBT (Total Blocking Time)

Value400 ms

68/100

30%

CLS (Cumulative Layout Shift)

Value0.607

10/100

15%

TTI (Time to Interactive)

Value10.2 s

25/100

10%

Network Requests Diagram

magnoliastore.com

213 ms

en

619 ms

styles.css

186 ms

head.min.js

264 ms

css2

33 ms

Our browser made a total of 21 requests to load all elements on the main page. We found that 57% of them (12 requests) were addressed to the original Magnoliastore.com, 19% (4 requests) were made to Fonts.gstatic.com and 10% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (622 ms) belongs to the original domain Magnoliastore.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 550.8 kB (41%)

Content Size

1.3 MB

After Optimization

795.3 kB

In fact, the total size of Magnoliastore.com main page is 1.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. 35% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-71%

Potential reduce by 40.1 kB

  • Original 56.1 kB
  • After minification 53.2 kB
  • After compression 16.0 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 40.1 kB or 71% of the original size.

Image Optimization

-47%

Potential reduce by 510.6 kB

  • Original 1.1 MB
  • After minification 583.7 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, Magnolia Store needs image optimization as it can save up to 510.6 kB or 47% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-0%

Potential reduce by 50 B

  • Original 131.8 kB
  • After minification 131.8 kB
  • After compression 131.7 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

-0%

Potential reduce by 0 B

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

Requests Breakdown

Number of requests can be reduced by 4 (33%)

Requests Now

12

After Optimization

8

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

Accessibility Review

magnoliastore.com accessibility score

74

Accessibility Issues

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

Buttons do not have an accessible name

High

Links do not have a discernible name

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

Heading elements are not in a sequentially-descending order

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

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

magnoliastore.com SEO score

80

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

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

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