Report Summary

  • 46

    Performance

    Renders faster than
    65% of other websites

  • 54

    Accessibility

    Visual factors better than
    that of 23% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 70

    SEO

    Google-friendlier than
    30% of websites

Page Load Speed

63.7 sec in total

First Response

2 sec

Resources Loaded

60.6 sec

Page Rendered

1.1 sec

static.eelly.com screenshot

About Website

Welcome to static.eelly.com homepage info - get ready to check Static Eelly best content for China right away, or after learning these important things about static.eelly.com

Visit static.eelly.com

Key Findings

We analyzed Static.eelly.com page load time and found that the first response time was 2 sec and then it took 61.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there were 20 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

static.eelly.com performance score

46

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

58/100

10%

LCP (Largest Contentful Paint)

Value5.7 s

16/100

25%

SI (Speed Index)

Value10.3 s

8/100

10%

TBT (Total Blocking Time)

Value260 ms

83/100

30%

CLS (Cumulative Layout Shift)

Value0.512

15/100

15%

TTI (Time to Interactive)

Value4.6 s

81/100

10%

Network Requests Diagram

static.eelly.com

2016 ms

www.eelly.com

4954 ms

base.css

489 ms

home.css

1414 ms

jquery.js.2b1ac101e0adf6b43bb2b93bb9b1e3ad.js

2526 ms

Our browser made a total of 185 requests to load all elements on the main page. We found that 22% of them (41 requests) were addressed to the original Static.eelly.com, 54% (100 requests) were made to Img.eelly.com and 11% (20 requests) were made to Cm.emarbox.com. The less responsive or slowest element that took the longest time to load (20.5 sec) relates to the external source Img.eelly.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 771.0 kB (17%)

Content Size

4.5 MB

After Optimization

3.7 MB

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

HTML Optimization

-78%

Potential reduce by 181.7 kB

  • Original 233.9 kB
  • After minification 230.8 kB
  • After compression 52.2 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 181.7 kB or 78% of the original size.

Image Optimization

-7%

Potential reduce by 256.7 kB

  • Original 3.8 MB
  • After minification 3.5 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. Static Eelly images are well optimized though.

JavaScript Optimization

-68%

Potential reduce by 256.4 kB

  • Original 379.3 kB
  • After minification 377.1 kB
  • After compression 122.9 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 256.4 kB or 68% of the original size.

CSS Optimization

-78%

Potential reduce by 76.2 kB

  • Original 97.7 kB
  • After minification 97.1 kB
  • After compression 21.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. Static.eelly.com needs all CSS files to be minified and compressed as it can save up to 76.2 kB or 78% of the original size.

Requests Breakdown

Number of requests can be reduced by 24 (18%)

Requests Now

130

After Optimization

106

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

Accessibility Review

static.eelly.com accessibility score

54

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

static.eelly.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

static.eelly.com SEO score

70

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

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

High

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

High

Document doesn't use legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    ZH

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Static.eelly.com can be misinterpreted by Google and other search engines. Our service has detected that Chinese is used on the page, and it does not match the claimed English language. Our system also found out that Static.eelly.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

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