Access talk.tw. Talk 滔客生活傳媒 | 享樂生活、開拓視野

talk.tw screenshot

5

Performance

Renders faster than
21% of other websites
62

Accessibility

Visual factors better than
that of 28% of websites
77

Best Practices

More advanced features
available than in
56% of websites
73

SEO

Google-friendlier than
31% of websites

First Response

1.7 sec

Resources Loaded

11.4 sec

Page Rendered

567 ms

talk.tw screenshot

About Website

Welcome to talk.tw homepage info - get ready to check Talk best content for Taiwan right away, or after learning these important things about talk.tw

滔客線上雜誌是集合眾多編輯群的聯合數位出版平台，依據作者專業特性進行分眾編輯，每本線上雜誌均擁有獨立的採編管理與經營模式，目標將成為華人線上最大的聯合出版集團。

Visit talk.tw

Key Findings

We analyzed Talk.tw page load time and found that the first response time was 1.7 sec and then it took 12 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster. This domain responded with an error, which can significantly jeopardize Talk.tw rating and web reputation

name

value

score

weighting

FCP (First Contentful Paint)

Value7.2 s

1/100

10%

LCP (Largest Contentful Paint)

Value9.7 s

1/100

25%

SI (Speed Index)

Value13.1 s

3/100

10%

TBT (Total Blocking Time)

Value1,500 ms

14/100

30%

CLS (Cumulative Layout Shift)

Value1.833

0/100

15%

TTI (Time to Interactive)

Value18.7 s

3/100

10%

talk.tw

1701 ms

bootstrap.css

1704 ms

bootstrap-submenu.css

667 ms

talk-style.css

1330 ms

font-awesome.css

1114 ms

Our browser made a total of 158 requests to load all elements on the main page. We found that 15% of them (23 requests) were addressed to the original Talk.tw, 53% (84 requests) were made to Filedisk.talk.tw and 15% (23 requests) were made to Tpc.googlesyndication.com. The less responsive or slowest element that took the longest time to load (5.2 sec) relates to the external source Filedisk.talk.tw.

Content Size

3.1 MB

After Optimization

2.2 MB

In fact, the total size of Talk.tw main page is 3.1 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 2.5 MB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 110.8 kB

Original 125.3 kB
After minification 52.7 kB
After compression 14.5 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. This page needs HTML code to be minified as it can gain 72.6 kB, which is 58% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 110.8 kB or 88% of the original size.

Image Optimization

-19%

Potential reduce by 462.0 kB

Original 2.5 MB
After minification 2.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. Obviously, Talk needs image optimization as it can save up to 462.0 kB or 19% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-52%

Potential reduce by 146.4 kB

Original 283.3 kB
After minification 255.3 kB
After compression 136.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 146.4 kB or 52% of the original size.

CSS Optimization

-86%

Potential reduce by 211.2 kB

Original 245.1 kB
After minification 184.4 kB
After compression 34.0 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. Talk.tw needs all CSS files to be minified and compressed as it can save up to 211.2 kB or 86% of the original size.

Requests Now

149

After Optimization

127

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

[aria-*] attributes do not match their roles

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

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

High

Browser errors were logged to the console

Search Engine Optimization Advices

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

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

To appear in search results, crawlers need access to your app.

High

Links are not crawlable

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

talk.tw

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