12.7 sec in total
3.1 sec
8.6 sec
963 ms
Welcome to editing.tw homepage info - get ready to check Editing best content for Taiwan right away, or after learning these important things about editing.tw
提供學術論文翻譯、英文編修、期刊摘要翻譯、文章中翻英等服務。我們是三段式翻譯服務,英文編修師針對文章內的台式英文句子進行英文潤稿,提供您最優質的翻譯編修服務
Visit editing.twWe analyzed Editing.tw page load time and found that the first response time was 3.1 sec and then it took 9.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
editing.tw performance score
name
value
score
weighting
Value9.0 s
0/100
10%
Value14.3 s
0/100
25%
Value11.1 s
5/100
10%
Value1,730 ms
10/100
30%
Value0
100/100
15%
Value14.6 s
8/100
10%
3126 ms
711 ms
65 ms
757 ms
480 ms
Our browser made a total of 55 requests to load all elements on the main page. We found that 73% of them (40 requests) were addressed to the original Editing.tw, 5% (3 requests) were made to S.gravatar.com and 4% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (3.1 sec) belongs to the original domain Editing.tw.
Page size can be reduced by 507.5 kB (58%)
874.0 kB
366.5 kB
In fact, the total size of Editing.tw main page is 874.0 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 40% of websites need less resources to load. Javascripts take 435.9 kB which makes up the majority of the site volume.
Potential reduce by 32.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 32.0 kB or 71% of the original size.
Potential reduce by 905 B
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. Editing images are well optimized though.
Potential reduce by 281.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 281.8 kB or 65% of the original size.
Potential reduce by 192.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. Editing.tw needs all CSS files to be minified and compressed as it can save up to 192.8 kB or 82% of the original size.
Number of requests can be reduced by 24 (47%)
51
27
The browser has sent 51 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Editing. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
www.editing.tw
3126 ms
autoptimize_2d35f307198279fbac37835d74dc3d25.css
711 ms
icon
65 ms
jquery-2.1.4.min.js
757 ms
noframework.waypoints.min.js
480 ms
vTicker.js
493 ms
css
38 ms
524 ms
jquery.js
1203 ms
jquery-migrate.min.js
1008 ms
d3.v3.min.js
1635 ms
d3-function.js
562 ms
gprofiles.js
59 ms
712 ms
devicepx-jetpack.js
14 ms
e-201611.js
7 ms
addfriends_zh-Hant.png
510 ms
enews6.jpg
496 ms
logo.png
447 ms
logo-1.png
465 ms
mainpage-edit-1.jpg
710 ms
ntu.png
529 ms
nctu.png
905 ms
nthu.jpg
966 ms
ncku.jpg
970 ms
ntuh.jpg
1002 ms
ncu.jpg
1236 ms
sinica.png
1300 ms
mmh.jpg
1421 ms
aer.jpg
1407 ms
nccu.jpg
1455 ms
fju.jpg
1445 ms
ntust.png
1681 ms
thu.jpg
1742 ms
map25-redish.png
1849 ms
envelope4-green.png
1904 ms
telephone65-blue.png
1887 ms
gtm.js
158 ms
logo-2.png
1903 ms
lines-dark.png
2097 ms
gk5FxslNkTTHtojXrkp-xD1GzwQ5qF9DNzkQQVRhJ4g.ttf
21 ms
analytics.js
13 ms
collect
6 ms
collect
68 ms
ga-audiences
56 ms
footer-icons.png
1305 ms
fontawesome-webfont.woff
2630 ms
rating_over.gif
1418 ms
www.editing.tw
1703 ms
www.editing.tw
1782 ms
www.editing.tw
1933 ms
hovercard.css
30 ms
services.css
56 ms
ajax-loader.gif
1690 ms
g.gif
4 ms
editing.tw accessibility score
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
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
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
<html> element does not have a [lang] attribute
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
Image elements do not have [alt] attributes
Links do not have a discernible name
editing.tw best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
editing.tw SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
Document uses legible font sizes
Tap targets are not sized appropriately
JA
ZH
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Editing.tw can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and it does not match the claimed Chinese language. Our system also found out that Editing.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.
editing.tw
Open Graph data is detected on the main page of Editing. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: