Access ivy.com.tw. 常春藤網路書城｜免費英文文章、音檔任你讀！升學考試絕對首選

ivy.com.tw screenshot

18

Performance

Renders faster than
34% of other websites
81

Accessibility

Visual factors better than
that of 52% of websites
83

Best Practices

More advanced features
available than in
56% of websites
88

SEO

Google-friendlier than
66% of websites

First Response

2.1 sec

Resources Loaded

15.3 sec

Page Rendered

354 ms

ivy.com.tw screenshot

About Website

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

提供學測、多益、英檢、普思等升學考試檢定相關教材。《常春藤解析英語雜誌》深獲全國英文老師的口碑肯定，並為多所高中指定之英文課外教材，更是無數青年學子心目中的第一品牌！

Visit ivy.com.tw

Key Findings

We analyzed Ivy.com.tw page load time and found that the first response time was 2.1 sec and then it took 15.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

name

value

score

weighting

FCP (First Contentful Paint)

Value4.3 s

18/100

10%

LCP (Largest Contentful Paint)

Value16.3 s

0/100

25%

SI (Speed Index)

Value17.0 s

0/100

10%

TBT (Total Blocking Time)

Value3,050 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.009

100/100

15%

TTI (Time to Interactive)

Value16.6 s

5/100

10%

www.ivy.com.tw

2143 ms

public.js

840 ms

JsLoader.js

633 ms

xajax.js

1261 ms

xajax_extend.js

1088 ms

Our browser made a total of 188 requests to load all elements on the main page. We found that 82% of them (155 requests) were addressed to the original Ivy.com.tw, 4% (8 requests) were made to Apis.google.com and 2% (3 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (3.7 sec) belongs to the original domain Ivy.com.tw.

Content Size

5.7 MB

After Optimization

4.6 MB

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

HTML Optimization

-82%

Potential reduce by 135.1 kB

Original 164.7 kB
After minification 158.4 kB
After compression 29.6 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 135.1 kB or 82% of the original size.

Image Optimization

-5%

Potential reduce by 226.4 kB

Original 4.5 MB
After minification 4.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. Ivy images are well optimized though.

JavaScript Optimization

-65%

Potential reduce by 434.6 kB

Original 666.3 kB
After minification 647.7 kB
After compression 231.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 434.6 kB or 65% of the original size.

CSS Optimization

-84%

Potential reduce by 320.0 kB

Original 380.2 kB
After minification 368.2 kB
After compression 60.2 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. Ivy.com.tw needs all CSS files to be minified and compressed as it can save up to 320.0 kB or 84% of the original size.

Requests Now

182

After Optimization

124

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

Accessibility Issues

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

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

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

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

JA
Language Claimed

EN
Encoding

UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ivy.com.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 English language. Our system also found out that Ivy.com.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

ivy.com.tw

Open Graph description is not detected on the main page of Ivy. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: