Access lovingfamily.com.tw. 戀家小舖

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

24/100

10%

LCP (Largest Contentful Paint)

Value46.4 s

0/100

25%

SI (Speed Index)

Value26.0 s

0/100

10%

TBT (Total Blocking Time)

Value6,230 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.681

8/100

15%

TTI (Time to Interactive)

Value27.3 s

0/100

10%

lovingfamily.com.tw

400 ms

lovingfamily.com.tw

793 ms

www.lovingfamily.com.tw

798 ms

index.aspx

1836 ms

magnific-popup.css

390 ms

Our browser made a total of 94 requests to load all elements on the main page. We found that 49% of them (46 requests) were addressed to the original Lovingfamily.com.tw, 41% (39 requests) were made to Photo.lovingfamily.com.tw and 7% (7 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (5.1 sec) relates to the external source Photo.lovingfamily.com.tw.

Content Size

12.3 MB

After Optimization

12.1 MB

In fact, the total size of Lovingfamily.com.tw main page is 12.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. 75% 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 12.0 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 95.6 kB

Original 116.2 kB
After minification 106.5 kB
After compression 20.6 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 95.6 kB or 82% of the original size.

Image Optimization

-0%

Potential reduce by 41.9 kB

Original 12.0 MB
After minification 12.0 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. Lovingfamily images are well optimized though.

JavaScript Optimization

-28%

Potential reduce by 45.3 kB

Original 162.5 kB
After minification 162.3 kB
After compression 117.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 45.3 kB or 28% of the original size.

CSS Optimization

-43%

Potential reduce by 8.8 kB

Original 20.3 kB
After minification 20.3 kB
After compression 11.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. Lovingfamily.com.tw needs all CSS files to be minified and compressed as it can save up to 8.8 kB or 43% of the original size.

Requests Now

After Optimization

The browser has sent 90 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lovingfamily. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 23 to 1 for JavaScripts and from 9 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

button, link, and menuitem elements do not have accessible names.

High

[role]s are not contained by their required parent element

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

[id] attributes on active, focusable elements are not unique

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

High

<html> element does not have a valid value for its [lang] attribute.

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

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

Areas of Improvement

High

Does not use HTTPS

High

Requests the notification permission on page load

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

High

robots.txt is not valid

Format your HTML in a way that enables crawlers to better understand your app’s content.

High

Image elements do not have [alt] attributes

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

High

Tap targets are not sized appropriately

Language and Encoding

Language Detected

ZH
Language Claimed

TC
Encoding

UTF-8

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

lovingfamily.com.tw

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

Report Summary

Performance

Accessibility

Best Practices

SEO

戀家小舖

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

lovingfamily.com.tw

lovingfamily.com.tw

www.lovingfamily.com.tw

index.aspx

magnific-popup.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

lovingfamily.com.tw

lovingfamily.com.tw

www.lovingfamily.com.tw

index.aspx

magnific-popup.css

main.css

style.css

mp-menu.css

banner.css

slick.css

slick-theme.css

jquery-3.3.1.min.js

jquery.lazyload.js

jquery.magnific-popup.min.js

jquery.cookie.js

lovingfamily.js

js

WebResource.axd

ScriptResource.axd

ScriptResource.axd

Index.css

ucKV.css

jquery.cycle2.js

jquery.cycle2.carousel.js

edm.js

classie.js

mlpushmenu.js

customer.js

bootstrap.js

gtm.js

gtm.js

gtm.js

fbevents.js

gtm.js

gtm.js

gtm.js

240708_%E6%9E%9C%E5%87%8D%E8%A2%AB&%E9%87%9D%E7%B9%94%E6%B6%BC%E8%A2%AB%E4%B8%80%E4%BB%B6$1180%E4%BA%8C%E4%BB%B6$1980_1200x500.jpg

logo.jpg

cart.png

%E6%94%BE%E5%A4%A7%E9%8F%A1.jpg

burg.png

logo.png

soc-1.jpg