Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 65

    Accessibility

    Visual factors better than
    that of 31% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 81

    SEO

    Google-friendlier than
    43% of websites

magnessa.com

Magnessa

Page Load Speed

45.8 sec in total

First Response

16.3 sec

Resources Loaded

29.1 sec

Page Rendered

386 ms

magnessa.com screenshot

About Website

Welcome to magnessa.com homepage info - get ready to check Magnessa best content for Bangladesh right away, or after learning these important things about magnessa.com

MagneSSa introduces a new world of naturally effective, one-of-a-kind wellness products to you, your home, and your family. And with over 70 unique products to choose from, shopping with MagneSSa is a...

Visit magnessa.com

Key Findings

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

Performance Metrics

magnessa.com performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value11.3 s

0/100

10%

LCP (Largest Contentful Paint)

Value11.7 s

0/100

25%

SI (Speed Index)

Value21.8 s

0/100

10%

TBT (Total Blocking Time)

Value1,030 ms

26/100

30%

CLS (Cumulative Layout Shift)

Value0.179

67/100

15%

TTI (Time to Interactive)

Value12.8 s

13/100

10%

Network Requests Diagram

16345 ms

css

70 ms

css

85 ms

css

97 ms

calendar-win2k-1.css

720 ms

Our browser made a total of 108 requests to load all elements on the main page. We found that 94% of them (101 requests) were addressed to the original Magnessa.com, 4% (4 requests) were made to Fonts.gstatic.com and 3% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (16.3 sec) belongs to the original domain Magnessa.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.7 MB (38%)

Content Size

4.3 MB

After Optimization

2.7 MB

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

HTML Optimization

-81%

Potential reduce by 40.8 kB

  • Original 50.1 kB
  • After minification 46.8 kB
  • After compression 9.3 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.8 kB or 81% of the original size.

Image Optimization

-2%

Potential reduce by 42.0 kB

  • Original 2.3 MB
  • After minification 2.2 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. Magnessa images are well optimized though.

JavaScript Optimization

-75%

Potential reduce by 1.1 MB

  • Original 1.4 MB
  • After minification 1.2 MB
  • After compression 349.4 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 1.1 MB or 75% of the original size.

CSS Optimization

-85%

Potential reduce by 497.7 kB

  • Original 583.2 kB
  • After minification 505.2 kB
  • After compression 85.5 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. Magnessa.com needs all CSS files to be minified and compressed as it can save up to 497.7 kB or 85% of the original size.

Requests Breakdown

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

Requests Now

101

After Optimization

23

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

Accessibility Review

magnessa.com accessibility score

65

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

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

ARIA toggle fields do not have accessible names

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

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

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.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

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

High

Missing source maps for large first-party JavaScript

SEO Factors

magnessa.com SEO score

81

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Magnessa.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 Magnessa.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 Magnessa. 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: