Tools & Wizards About Us
eoplly.com screenshot

Report Summary

  • 0

    Performance

  • 34

    Accessibility

    Visual factors better than
    that of 18% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

eoplly.com

欧贝黎新能源科技股份有限公司-欧贝黎新能源科技股份有限公司

Page Load Speed

19.1 sec in total

First Response

1.1 sec

Resources Loaded

17.6 sec

Page Rendered

434 ms

eoplly.com screenshot

About Website

Click here to check amazing Eoplly content. Otherwise, check out these important facts you probably never knew about eoplly.com

欧贝黎新能源科技股份有限公司成立于2006年1月，注册资本1.6亿元，是全球太阳能电池和光伏组件转化效率行业领先的龙头企业，是聚焦光伏领域电池转化效率研发及制造的高新技术企业。公司坚持以价值服务为宗旨、以产品应用为载体，成为优化的新能源发电解决方案提供商。

Visit eoplly.com

Key Findings

We analyzed Eoplly.com page load time and found that the first response time was 1.1 sec and then it took 18 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.

Performance Metrics

eoplly.com performance score

0

Network Requests Diagram

eoplly.com

1091 ms

style.css

719 ms

jquery-1.8.3.min.js

1447 ms

jquery.SuperSlide.2.1.1.js

722 ms

lrtk.js

484 ms

Our browser made a total of 39 requests to load all elements on the main page. We found that all of those requests were addressed to Eoplly.com and no external sources were called. The less responsive or slowest element that took the longest time to load (11.2 sec) belongs to the original domain Eoplly.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 179.0 kB (6%)

Content Size

2.9 MB

After Optimization

2.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-73%

Potential reduce by 15.7 kB

  • Original 21.5 kB
  • After minification 21.2 kB
  • After compression 5.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 15.7 kB or 73% of the original size.

Image Optimization

-3%

Potential reduce by 91.1 kB

  • Original 2.7 MB
  • After minification 2.6 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. Eoplly images are well optimized though.

JavaScript Optimization

-37%

Potential reduce by 71.4 kB

  • Original 191.5 kB
  • After minification 191.1 kB
  • After compression 120.0 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 71.4 kB or 37% of the original size.

CSS Optimization

-13%

Potential reduce by 791 B

  • Original 6.3 kB
  • After minification 6.3 kB
  • After compression 5.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. Eoplly.com needs all CSS files to be minified and compressed as it can save up to 791 B or 13% of the original size.

Requests Breakdown

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

Requests Now

38

After Optimization

31

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

eoplly.com

eoplly.com

1091 ms

style.css

style.css

719 ms

jquery-1.8.3.min.js

jquery-1.8.3.min.js

1447 ms

jquery.SuperSlide.2.1.1.js

jquery.SuperSlide.2.1.1.js

722 ms

lrtk.js

lrtk.js

484 ms

jquery-1.3.2.min.js

jquery-1.3.2.min.js

1217 ms

global.js

global.js

490 ms

jquery-1.4.2.min.js

jquery-1.4.2.min.js

1462 ms

jquery-1.11.2.min.js

jquery-1.11.2.min.js

2210 ms

jquery.SuperSlide.2.1.js

jquery.SuperSlide.2.1.js

958 ms

html.gif

html.gif

273 ms

body.jpg

body.jpg

271 ms

logo.jpg

logo.jpg

491 ms

slider-arrow.png

slider-arrow.png

242 ms

a1.jpg

a1.jpg

1214 ms

a2.jpg

a2.jpg

724 ms

a3.jpg

a3.jpg

763 ms

a4.jpg

a4.jpg

961 ms

14527398897.jpg

14527398897.jpg

1228 ms

145274097897.jpg

145274097897.jpg

1268 ms

145273684801.jpg

145273684801.jpg

1208 ms

145267531222.jpg

145267531222.jpg

1244 ms

20160914160123_61222.jpg

20160914160123_61222.jpg

5322 ms

20160914152057_50963.jpg

20160914152057_50963.jpg

3622 ms

20160914152540_83447.jpg

20160914152540_83447.jpg

11157 ms

about.jpg

about.jpg

1946 ms

20160817104939_38634.jpg

20160817104939_38634.jpg

2726 ms

20160817104859_92801.jpg

20160817104859_92801.jpg

2982 ms

weixin.jpg

weixin.jpg

2665 ms

banner1.jpg

banner1.jpg

5753 ms

p1.png

p1.png

2941 ms

Advantage_bg.jpg

Advantage_bg.jpg

5343 ms

pageBtn.png

pageBtn.png

3169 ms

email10.png

email10.png

3415 ms

tel10.png

tel10.png

3659 ms

contact_2.png

contact_2.png

3804 ms

banner2.jpg

banner2.jpg

5827 ms

banner3.jpg

banner3.jpg

5989 ms

banner4.jpg

banner4.jpg

3962 ms

Accessibility Review

eoplly.com accessibility score

34

Accessibility Issues

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

Document doesn't have a <title> element

High

<frame> or <iframe> elements do not have a title

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

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

eoplly.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

High

Browser errors were logged to the console

SEO Factors

eoplly.com SEO score

75

Search Engine Optimization Advices

Content Best Practices

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

Impact

Issue

High

Document doesn't have a <title> element

Crawling and Indexing

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

Impact

Issue

High

robots.txt is not valid

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 uses legible font sizes

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

eoplly.com

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