Tools & Wizards About Us

Report Summary

  • 52

    Performance

    Renders faster than
    69% of other websites

  • 58

    Accessibility

    Visual factors better than
    that of 25% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

aams.tw

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

Page Load Speed

5 sec in total

First Response

122 ms

Resources Loaded

4.5 sec

Page Rendered

407 ms

About Website

Click here to check amazing AAMS content for Taiwan. Otherwise, check out these important facts you probably never knew about aams.tw

Facebook行銷服務領先群倫的全通媒體集團一直以來不斷致力於網路行銷工具與方式的研究，以協助企業客戶有效完成網路行銷上的各式需求。從網站建置開始到成功的網路行銷成果，都能提供最精確完善的服務。我們也努力經營社群與網友的目光流量。期待透過我們有系統的思考與安排，讓客戶順利搭上網路廣告與行銷的黃金列車。

Visit aams.tw

Key Findings

We analyzed Aams.tw page load time and found that the first response time was 122 ms and then it took 4.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

aams.tw performance score

52

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

45/100

10%

LCP (Largest Contentful Paint)

Value7.4 s

4/100

25%

SI (Speed Index)

Value5.4 s

56/100

10%

TBT (Total Blocking Time)

Value440 ms

64/100

30%

CLS (Cumulative Layout Shift)

Value0.026

100/100

15%

TTI (Time to Interactive)

Value6.1 s

64/100

10%

Network Requests Diagram

aams.tw

122 ms

aams.tw

521 ms

jquery.min.js

38 ms

bootstrap.min.js

73 ms

jquery.nav.js

509 ms

Our browser made a total of 36 requests to load all elements on the main page. We found that 81% of them (29 requests) were addressed to the original Aams.tw, 11% (4 requests) were made to Maps.googleapis.com and 3% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (3.1 sec) belongs to the original domain Aams.tw.

Page Optimization Overview & Recommendations

Page size can be reduced by 80.2 kB (6%)

Content Size

1.2 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-69%

Potential reduce by 9.7 kB

  • Original 14.1 kB
  • After minification 13.2 kB
  • After compression 4.4 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

-1%

Potential reduce by 8.2 kB

  • Original 1.0 MB
  • After minification 1.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. AAMS images are well optimized though.

JavaScript Optimization

-35%

Potential reduce by 61.6 kB

  • Original 175.4 kB
  • After minification 175.4 kB
  • After compression 113.8 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 61.6 kB or 35% of the original size.

CSS Optimization

-3%

Potential reduce by 706 B

  • Original 21.5 kB
  • After minification 21.5 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 has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 8 (24%)

Requests Now

33

After Optimization

25

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 33 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 9 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

Accessibility Review

aams.tw accessibility score

58

Accessibility Issues

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

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

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

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.

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

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

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Internationalization and localization

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

Impact

Issue

High

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

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

aams.tw best practices score

83

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

SEO Factors

aams.tw SEO score

85

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

High

robots.txt is not valid

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

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

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: