Access aams.tw. AAMS 全通媒體集團 || Facebook行銷專家 || 全通媒體集團 || ALL ACCESS MARKETING SOLUTIONS.

name

value

score

weighting

FCP (First Contentful Paint)

Value5.5 s

6/100

10%

LCP (Largest Contentful Paint)

Value15.0 s

0/100

25%

SI (Speed Index)

Value8.4 s

18/100

10%

TBT (Total Blocking Time)

Value150 ms

94/100

30%

CLS (Cumulative Layout Shift)

Value0.026

100/100

15%

TTI (Time to Interactive)

Value7.2 s

50/100

10%

aams.tw

959 ms

jquery.min.js

57 ms

bootstrap.min.js

89 ms

jquery.nav.js

488 ms

index.js

691 ms

Our browser made a total of 86 requests to load all elements on the main page. We found that 31% of them (27 requests) were addressed to the original Aams.tw, 33% (28 requests) were made to Google.com and 15% (13 requests) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (20 sec) belongs to the original domain Aams.tw.

Content Size

3.6 MB

After Optimization

3.3 MB

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

HTML Optimization

-69%

Potential reduce by 9.7 kB

Original 14.0 kB
After minification 13.1 kB
After compression 4.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 9.7 kB or 69% of the original size.

Image Optimization

-4%

Potential reduce by 119.5 kB

Original 3.4 MB
After minification 3.3 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. AAMS images are well optimized though.

JavaScript Optimization

-73%

Potential reduce by 26.4 kB

Original 36.0 kB
After minification 36.0 kB
After compression 9.6 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 26.4 kB or 73% of the original size.

CSS Optimization

-85%

Potential reduce by 121.4 kB

Original 142.1 kB
After minification 122.3 kB
After compression 20.8 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. Aams.tw needs all CSS files to be minified and compressed as it can save up to 121.4 kB or 85% of the original size.

Requests Now

After Optimization

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

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

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 experience of reading tabular or list data using assistive technology, like a screen reader.

High

<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.

These are opportunities to improve keyboard navigation in your application.

High

Heading elements are not in a sequentially-descending order

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

Low

Detected JavaScript libraries

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

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

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

aams.tw

Open Graph data is detected on the main page of AAMS. 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

AAMS 全通媒體集團 || Facebook行銷專家 || 全通媒體集團 || ALL ACCESS MARKETING SOLUTIONS.

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

aams.tw

jquery.min.js

bootstrap.min.js

jquery.nav.js

index.js

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

aams.tw

jquery.min.js

bootstrap.min.js

jquery.nav.js

index.js

sendmail.js

public.css

bootstrap.min.css

embed

service-1.png

service-1xs.png

service-2.png

service-2xs.png

service-3.png

service-3xs.png

success_list_photo_19.jpg

success_list_photo_18.jpg

success_list_photo_17.jpg

success_list_photo_16.png

about02.jpg

about04.jpg

about01.jpg

about03.jpg

about05.jpg

bannerphoto_3.png

bannerphoto_2.png

bannerphoto_4.png

js

init_embed.js

common.js

map.js

google4.png

overlay.js

util.js

onion.js

search_impl.js

stats.js

openhand_8_8.cur

ViewportInfoService.GetViewportInfo

ViewportInfoService.GetViewportInfo

kh

kh

transparent.png