Access seemly.tw. 能多潔除蟲公司－最佳害蟲防治選擇

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

20/100

10%

LCP (Largest Contentful Paint)

Value11.1 s

0/100

25%

SI (Speed Index)

Value16.9 s

0/100

10%

TBT (Total Blocking Time)

Value1,390 ms

16/100

30%

CLS (Cumulative Layout Shift)

Value0.144

78/100

15%

TTI (Time to Interactive)

Value32.5 s

0/100

10%

seemly.tw

561 ms

seemly.tw

1405 ms

amazeui.css

1504 ms

app.css

501 ms

logo.png

1336 ms

Our browser made a total of 68 requests to load all elements on the main page. We found that 84% of them (57 requests) were addressed to the original Seemly.tw, 7% (5 requests) were made to Youtube.com and 3% (2 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (3.6 sec) belongs to the original domain Seemly.tw.

Content Size

6.9 MB

After Optimization

6.2 MB

In fact, the total size of Seemly.tw main page is 6.9 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. 80% 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 6.0 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 41.4 kB

Original 48.4 kB
After minification 44.9 kB
After compression 7.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 41.4 kB or 85% of the original size.

Image Optimization

-2%

Potential reduce by 146.0 kB

Original 6.0 MB
After minification 5.9 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. Seemly images are well optimized though.

JavaScript Optimization

-46%

Potential reduce by 213.8 kB

Original 464.8 kB
After minification 461.1 kB
After compression 251.0 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 213.8 kB or 46% of the original size.

CSS Optimization

-74%

Potential reduce by 290.2 kB

Original 393.5 kB
After minification 316.5 kB
After compression 103.3 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. Seemly.tw needs all CSS files to be minified and compressed as it can save up to 290.2 kB or 74% of the original size.

Requests Now

After Optimization

The browser has sent 63 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Seemly. 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 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-hidden="true"] elements contain focusable descendents

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

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 the interpretation of your content by users in different locales.

High

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

These items highlight common accessibility best practices.

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

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

Displays images with incorrect aspect ratio

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

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

N/A
Encoding

UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Seemly.tw can be misinterpreted by Google and other search engines. Our service has detected that Chinese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Seemly.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

seemly.tw

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

能多潔除蟲公司－最佳害蟲防治選擇

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

seemly.tw

seemly.tw

amazeui.css

app.css

logo.png

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

seemly.tw

seemly.tw

amazeui.css

app.css

logo.png

20220901162625.png

20180426184606.jpg

20180130130732.jpg

20170414171243.png

20170422115556.jpg

20180130130813.png

20170422115459.jpg

20170414170446.jpg

20070322174500.jpg

20070323152733.jpg

20160408021257.jpg

20070323171330.jpg

20070323171457.jpg

20070323171712.jpg

20070323172039.jpg

20070323172206.jpg

20070323172347.jpg

20070329163223.jpg

20070329163312.jpg

20070329163341.jpg

20160408004609.jpg

20071113024550.jpg

20170720172300.jpg

20120228162328.jpg

20120228173230.jpg

20120228181152.jpg

20120228163518.jpg

20120228175150.jpg

20070323053953.jpg

20120228162824.jpg

20070323035532.jpg

20120228164102.jpg

jquery.min.js

amazeui.min.js

ajaxfileupload.js

app.js

common.js

analytics.js