Access 2015.eyny.com. 伊莉討論區

2015.eyny.com screenshot

78

Performance

Renders faster than
85% of other websites
85

Accessibility

Visual factors better than
that of 60% of websites
75

Best Practices

More advanced features
available than in
36% of websites
62

SEO

Google-friendlier than
22% of websites

First Response

143 ms

Resources Loaded

1.6 sec

Page Rendered

565 ms

2015.eyny.com screenshot

About Website

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

伊莉,伊莉討論區,伊莉論壇,forum,discuss ,伊莉討論區

Visit 2015.eyny.com

Key Findings

We analyzed 2015.eyny.com page load time and found that the first response time was 143 ms and then it took 2.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

name

value

score

weighting

FCP (First Contentful Paint)

Value1.6 s

93/100

10%

LCP (Largest Contentful Paint)

Value2.5 s

89/100

25%

SI (Speed Index)

Value2.1 s

99/100

10%

TBT (Total Blocking Time)

Value650 ms

45/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value4.8 s

78/100

10%

index.php

143 ms

style_1_common.css

64 ms

style_1_forum_index.css

71 ms

css_common.css

72 ms

js_common.js

73 ms

Our browser made a total of 157 requests to load all elements on the main page. We found that 80% of them (125 requests) were addressed to the original 2015.eyny.com, 3% (5 requests) were made to Tpc.googlesyndication.com and 3% (5 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (662 ms) relates to the external source Servedby.flashtalking.com.

Content Size

281.4 kB

After Optimization

150.9 kB

In fact, the total size of 2015.eyny.com main page is 281.4 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. 50% of websites need less resources to load. HTML takes 131.8 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 109.0 kB

Original 131.8 kB
After minification 131.6 kB
After compression 22.8 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 109.0 kB or 83% of the original size.

Image Optimization

-0%

Potential reduce by 342 B

Original 83.5 kB
After minification 83.2 kB

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. 2015 Eyny images are well optimized though.

JavaScript Optimization

-32%

Potential reduce by 20.7 kB

Original 65.1 kB
After minification 64.9 kB
After compression 44.3 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 20.7 kB or 32% of the original size.

CSS Optimization

-37%

Potential reduce by 378 B

Original 1.0 kB
After minification 954 B
After compression 657 B

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. 2015.eyny.com needs all CSS files to be minified and compressed as it can save up to 378 B or 37% of the original size.

Requests Now

156

After Optimization

100

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

Accessibility Issues

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

Form elements do not have associated labels

These are opportunities to improve keyboard navigation in your application.

High

Some elements have a [tabindex] value greater than 0

Areas of Improvement

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

High

Serves images with low resolution

Search Engine Optimization Advices

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

High

Links are not crawlable

High

Page is blocked from indexing

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 2015.eyny.com 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 2015.eyny.com 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

2015.eyny.com

Open Graph description is not detected on the main page of 2015 Eyny. 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: