Tools & Wizards About Us
magnolia.co.th screenshot

Report Summary

  • 4

    Performance

    Renders faster than
    20% of other websites

  • 67

    Accessibility

    Visual factors better than
    that of 32% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 80

    SEO

    Google-friendlier than
    42% of websites

magnolia.co.th

Project Brands - Magnolia Quality Development Corporation Limited

Page Load Speed

7.5 sec in total

First Response

35 ms

Resources Loaded

7 sec

Page Rendered

471 ms

magnolia.co.th screenshot

About Website

Visit magnolia.co.th now to see the best up-to-date Magnolia content and also check out these interesting facts you probably never knew about magnolia.co.th

Project Brands - Magnolia Quality Development Corporation Limited

Visit magnolia.co.th

Key Findings

We analyzed Magnolia.co.th page load time and found that the first response time was 35 ms and then it took 7.4 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

magnolia.co.th performance score

4

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.4 s

7/100

10%

LCP (Largest Contentful Paint)

Value22.6 s

0/100

25%

SI (Speed Index)

Value20.1 s

0/100

10%

TBT (Total Blocking Time)

Value1,800 ms

10/100

30%

CLS (Cumulative Layout Shift)

Value1.086

1/100

15%

TTI (Time to Interactive)

Value20.2 s

2/100

10%

Network Requests Diagram

magnolia.co.th

35 ms

1030 ms

1007 ms

project

441 ms

gtm.js

89 ms

Our browser made a total of 52 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Magnolia.co.th, 90% (47 requests) were made to Mqdc.com and 4% (2 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (3.1 sec) relates to the external source Mqdc.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 70.1 kB (2%)

Content Size

3.1 MB

After Optimization

3.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Magnolia.co.th main page is 3.1 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 2.8 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 43.8 kB

  • Original 51.6 kB
  • After minification 37.9 kB
  • After compression 7.8 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. This page needs HTML code to be minified as it can gain 13.7 kB, which is 27% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 43.8 kB or 85% of the original size.

Image Optimization

-1%

Potential reduce by 25.9 kB

  • Original 2.8 MB
  • After minification 2.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. Magnolia images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 105 B

  • Original 228.0 kB
  • After minification 228.0 kB
  • After compression 227.9 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 335 B

  • Original 68.3 kB
  • After minification 68.3 kB
  • After compression 68.0 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. Magnolia.co.th has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 5 (12%)

Requests Now

43

After Optimization

38

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

magnolia.co.th

magnolia.co.th

35 ms

1030 ms

1007 ms

project

project

441 ms

gtm.js

gtm.js

89 ms

app.css

app.css

502 ms

app.js

app.js

1004 ms

all.js

all.js

1758 ms

fontface.css

fontface.css

749 ms

logo-mqdc.png

logo-mqdc.png

247 ms

icon-close.svg

icon-close.svg

310 ms

banner-register-m.jpg

banner-register-m.jpg

542 ms

bg-head-flower-left.png

bg-head-flower-left.png

804 ms

bg-head-flower-right.png

bg-head-flower-right.png

734 ms

bg-shadow-menu.png

bg-shadow-menu.png

738 ms

bg-shadow-logo.png

bg-shadow-logo.png

979 ms

logo-mqdc-white.png

logo-mqdc-white.png

984 ms

banner-business-project-en.jpg

banner-business-project-en.jpg

2043 ms

banner-project-brand-m.jpg

banner-project-brand-m.jpg

1797 ms

icon-arrowborder-top.svg

icon-arrowborder-top.svg

1069 ms

shadow-right.png

shadow-right.png

1563 ms

mqdc-business-magnolias.jpg

mqdc-business-magnolias.jpg

1710 ms

mqdc-business-magnolias-m.jpg

mqdc-business-magnolias-m.jpg

1229 ms

mqdc-logo-magnolias.jpg

mqdc-logo-magnolias.jpg

1559 ms

mqdc-business-whizdom.jpg

mqdc-business-whizdom.jpg

1720 ms

mqdc-business-whizdom-m.jpg

mqdc-business-whizdom-m.jpg

2539 ms

mqdc-logo-whizdom.jpg

mqdc-logo-whizdom.jpg

1809 ms

mqdc-business-mulberrygrove.jpg

mqdc-business-mulberrygrove.jpg

1955 ms

mqdc-business-mulberrygrove-m.jpg

mqdc-business-mulberrygrove-m.jpg

1966 ms

mqdc-logo-mulberrygrove.jpg

mqdc-logo-mulberrygrove.jpg

2040 ms

mqdc-business-aspentree.jpg

mqdc-business-aspentree.jpg

3075 ms

mqdc-business-aspentree-m.jpg

mqdc-business-aspentree-m.jpg

2201 ms

mqdc-logo-aspentree.jpg

mqdc-logo-aspentree.jpg

2211 ms

icon-mail.svg

icon-mail.svg

2283 ms

icon-callcenter.svg

icon-callcenter.svg

2288 ms

icon-fb.svg

icon-fb.svg

2445 ms

icon-tw.svg

icon-tw.svg

2457 ms

icon-ig.svg

icon-ig.svg

2527 ms

icon-yt.svg

icon-yt.svg

2536 ms

icon-line.svg

icon-line.svg

2688 ms

dbhelvethaicax-webfont.woff

dbhelvethaicax-webfont.woff

2659 ms

dbhelvethaicaxli-webfont.woff

dbhelvethaicaxli-webfont.woff

2726 ms

dbhelvethaicaxmed-webfont.woff

dbhelvethaicaxmed-webfont.woff

2741 ms

dbhelvethaicaxbd-webfont.woff

dbhelvethaicaxbd-webfont.woff

2741 ms

vinegar-regular-webfont.woff

vinegar-regular-webfont.woff

2691 ms

en.json

en.json

2455 ms

jquery.mousewheel.min.js

jquery.mousewheel.min.js

45 ms

th.json

th.json

2478 ms

cn.json

cn.json

2481 ms

icon-close.svg

icon-close.svg

2303 ms

iframe_api

iframe_api

36 ms

www-widgetapi.js

www-widgetapi.js

3 ms

Accessibility Review

magnolia.co.th accessibility score

67

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.

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 IDs are not unique

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

Low

No form fields have multiple labels

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

magnolia.co.th 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

magnolia.co.th SEO score

80

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 Magnolia.co.th 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 Magnolia.co.th 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

magnolia.co.th

Open Graph data is detected on the main page of Magnolia. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: