Access magicwed.com.tw. 婚禮魔法屋

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

25/100

10%

LCP (Largest Contentful Paint)

Value37.5 s

0/100

25%

SI (Speed Index)

Value15.0 s

1/100

10%

TBT (Total Blocking Time)

Value1,330 ms

17/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value24.9 s

0/100

10%

magicwed.com.tw

647 ms

magicwed.com.tw

1352 ms

font-awesome.min.css

409 ms

flaticon.css

611 ms

bootstrap.min.css

1218 ms

Our browser made a total of 58 requests to load all elements on the main page. We found that 76% of them (44 requests) were addressed to the original Magicwed.com.tw, 9% (5 requests) were made to Fonts.gstatic.com and 9% (5 requests) were made to Widget.sndcdn.com. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Magicwed.com.tw.

Content Size

9.2 MB

After Optimization

7.9 MB

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

HTML Optimization

-83%

Potential reduce by 24.7 kB

Original 29.6 kB
After minification 17.9 kB
After compression 4.9 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 11.7 kB, which is 39% 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 24.7 kB or 83% of the original size.

Image Optimization

-5%

Potential reduce by 374.2 kB

Original 8.1 MB
After minification 7.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. Magic Wed images are well optimized though.

JavaScript Optimization

-79%

Potential reduce by 504.4 kB

Original 641.8 kB
After minification 554.6 kB
After compression 137.5 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 504.4 kB or 79% of the original size.

CSS Optimization

-88%

Potential reduce by 359.8 kB

Original 406.7 kB
After minification 305.7 kB
After compression 46.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. Magicwed.com.tw needs all CSS files to be minified and compressed as it can save up to 359.8 kB or 88% of the original size.

Requests Now

After Optimization

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

Accessibility Issues

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.

High

[aria-*] attributes do not match their roles

High

[aria-hidden="true"] elements contain focusable descendents

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

High

[aria-*] attributes do not have valid values

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.

High

Buttons do not have an accessible name

High

Links do not have a discernible name

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

These are opportunities to improve keyboard navigation in your application.

High

Heading elements are not in a sequentially-descending order

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

High

Serves images with low resolution

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

Search Engine Optimization Advices

To appear in search results, crawlers need access to your app.

High

Links are not crawlable

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/).

High

Document uses legible font sizes

Language and Encoding

Language Detected

JA
Language Claimed

ZH
Encoding

UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Magicwed.com.tw can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and it does not match the claimed Chinese language. Our system also found out that Magicwed.com.tw 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

magicwed.com.tw

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

Report Summary

Performance

Accessibility

Best Practices

SEO

婚禮魔法屋 - Magic Wedding House

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

magicwed.com.tw

magicwed.com.tw

font-awesome.min.css

flaticon.css

bootstrap.min.css

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

magicwed.com.tw

magicwed.com.tw

font-awesome.min.css

flaticon.css

bootstrap.min.css

animate.css

owl.carousel.css

owl.theme.css

slick.css

slick-theme.css

owl.transitions.css

jquery.fancybox.css

magnific-popup.css

style2.css

js

jquery.min.js

bootstrap.min.js

jquery-plugin-collection.js

spirit.js

script.js

css

cwtexyen.css

slide-1.jpg

zjU3LqNYv0HFuykUVDq9QQuCxh5Qdq0N.jpg

F7ANStdFn6YvfgKh6EPs1u60BuUoXS3B.jpg

logo.png

img-6.jpg

img-8.jpg

img-7.jpg

bcCibtJSn5Q7rjx7BZUx7SFdpxhKoeNA.jpg

LM9Yz6LdkDtyYiJ4jxWMLUf6uV0Nhu82.jpg

0JL6T5zJqKmMKOZQnQFL2mIP7kyuuZRv.jpg

8Of0OtHHwnH7v6O3IqnRyXdHQcHXQrUY.JPG

H7w809QmrXK73AM0GhED3t5arWTcoqh5.jpg

tqXJ2dZkMPIZTrmur0S4yUQseiua2Wov.jpg

DNZNaP1qYQsAAANEeiN9bySHiqO3SVgw.jpg

psF6OGIreazuVTwmZ0URl5zlOvGhc2qB.jpg

jOzJkgfiWIllLjvey50co280mdRjZSDi.jpg

5Ty7KcIqDAXehUA5Qb1MLRtYNKbb7eud.jpg

YptjVnGNWqx5dDVZGJObZl5xWkJbRJtQ.jpg

U5TzzYEMWBYw6XWuAgEVhnbbE6IpyP0t.jpg

a9XJOqoc7TQTJY52pZ1Xnm9Aq7cyPXYZ.jpg

PZnLFLUw8vWVvyANWqj4GNI22Ky4aAIZ.jpg