Access aotter.net. Aotter 電獺｜Ahead of Time. 用網路發明世界

aotter.net screenshot

49

Performance

Renders faster than
68% of other websites
81

Accessibility

Visual factors better than
that of 52% of websites
75

Best Practices

More advanced features
available than in
36% of websites
78

SEO

Google-friendlier than
40% of websites

First Response

1.2 sec

Resources Loaded

18.9 sec

Page Rendered

517 ms

aotter.net screenshot

About Website

Click here to check amazing Aotter content for Taiwan. Otherwise, check out these important facts you probably never knew about aotter.net

電獺公司是一間致力縮短「價值創造時間」的創新研發公司，我們的核心宗旨為讓知識、資訊透過新科技體現價值，主要朝媒體、社群及專家工具三個面向發展；我們從創作工具、變現工具與數據廣告等平台服務，乃至職人偶像培養、線下空間、影視內容創作等都提供相對應的服務，與數位內容創作者並肩，矢志創造嶄新的「腦袋產業」。

Visit aotter.net

Key Findings

We analyzed Aotter.net page load time and found that the first response time was 1.2 sec and then it took 19.4 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.

name

value

score

weighting

FCP (First Contentful Paint)

Value8.0 s

0/100

10%

LCP (Largest Contentful Paint)

Value8.9 s

1/100

25%

SI (Speed Index)

Value12.9 s

2/100

10%

TBT (Total Blocking Time)

Value70 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value9.0 s

34/100

10%

aotter.net

1199 ms

main.css

888 ms

jquery-1.10.1.min.js

714 ms

jquery-migrate-1.2.1.min.js

587 ms

jquery.ba-bbq.min.js

587 ms

Our browser made a total of 166 requests to load all elements on the main page. We found that 60% of them (100 requests) were addressed to the original Aotter.net, 32% (53 requests) were made to Maps.googleapis.com and 4% (6 requests) were made to Maps.gstatic.com. The less responsive or slowest element that took the longest time to load (13.1 sec) belongs to the original domain Aotter.net.

Content Size

17.6 MB

After Optimization

15.9 MB

In fact, the total size of Aotter.net main page is 17.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. 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 16.8 MB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 104.7 kB

Original 121.6 kB
After minification 114.1 kB
After compression 16.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. 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 104.7 kB or 86% of the original size.

Image Optimization

-7%

Potential reduce by 1.2 MB

Original 16.8 MB
After minification 15.6 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. Aotter images are well optimized though.

JavaScript Optimization

-65%

Potential reduce by 431.1 kB

Original 661.5 kB
After minification 658.4 kB
After compression 230.4 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 431.1 kB or 65% of the original size.

CSS Optimization

-84%

Potential reduce by 43.3 kB

Original 51.8 kB
After minification 42.0 kB
After compression 8.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. Aotter.net needs all CSS files to be minified and compressed as it can save up to 43.3 kB or 84% of the original size.

Requests Now

159

After Optimization

133

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

Accessibility Issues

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

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

Links do not have a discernible name

Areas of Improvement

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

High

Displays images with incorrect aspect ratio

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

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

aotter.net

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