Tools & Wizards About Us
edge-core.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

edge-core.com

Edgecore Networks

Page Load Speed

19.5 sec in total

First Response

1.5 sec

Resources Loaded

17.9 sec

Page Rendered

129 ms

edge-core.com screenshot

About Website

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

Edgecore Networks, a leading provider of traditional and open network solutions, delivers wired and wireless networking products and solutions through channel partners and system integrators worldwide...

Visit edge-core.com

Key Findings

We analyzed Edge-core.com page load time and found that the first response time was 1.5 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

edge-core.com performance score

0

Network Requests Diagram

edge-core.com

1481 ms

share.css

2930 ms

hp.css

655 ms

jquery-1.7.1.min.js

5222 ms

jquery.nivo.slider.pack.js

2545 ms

Our browser made a total of 65 requests to load all elements on the main page. We found that 97% of them (63 requests) were addressed to the original Edge-core.com, 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (10.3 sec) belongs to the original domain Edge-core.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 270.0 kB (16%)

Content Size

1.7 MB

After Optimization

1.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-76%

Potential reduce by 18.4 kB

  • Original 24.3 kB
  • After minification 24.3 kB
  • After compression 5.9 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 18.4 kB or 76% of the original size.

Image Optimization

-10%

Potential reduce by 149.5 kB

  • Original 1.5 MB
  • After minification 1.4 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. Edgecore images are well optimized though.

JavaScript Optimization

-59%

Potential reduce by 87.3 kB

  • Original 146.8 kB
  • After minification 144.6 kB
  • After compression 59.5 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 87.3 kB or 59% of the original size.

CSS Optimization

-78%

Potential reduce by 14.8 kB

  • Original 19.0 kB
  • After minification 15.6 kB
  • After compression 4.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. Edge-core.com needs all CSS files to be minified and compressed as it can save up to 14.8 kB or 78% of the original size.

Requests Breakdown

Number of requests can be reduced by 15 (23%)

Requests Now

64

After Optimization

49

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

edge-core.com

edge-core.com

1481 ms

share.css

share.css

2930 ms

hp.css

hp.css

655 ms

jquery-1.7.1.min.js

jquery-1.7.1.min.js

5222 ms

jquery.nivo.slider.pack.js

jquery.nivo.slider.pack.js

2545 ms

jquery.liquidcarousel.pack.js

jquery.liquidcarousel.pack.js

680 ms

ec_init.js

ec_init.js

505 ms

ec_menu.js

ec_menu.js

384 ms

m1a.jpg

m1a.jpg

408 ms

m2a.jpg

m2a.jpg

382 ms

m3a.jpg

m3a.jpg

395 ms

m4a.jpg

m4a.jpg

403 ms

m5a.jpg

m5a.jpg

413 ms

m6a.jpg

m6a.jpg

414 ms

m1b.jpg

m1b.jpg

653 ms

m2b.jpg

m2b.jpg

659 ms

m3b.jpg

m3b.jpg

678 ms

m4b.jpg

m4b.jpg

785 ms

m5b.jpg

m5b.jpg

769 ms

m6b.jpg

m6b.jpg

790 ms

header_bg.jpg

header_bg.jpg

936 ms

logo.jpg

logo.jpg

946 ms

banner_datacenter.jpg

banner_datacenter.jpg

5924 ms

banner_co2re.jpg

banner_co2re.jpg

10321 ms

banner_access.jpg

banner_access.jpg

7481 ms

banner_wireless.jpg

banner_wireless.jpg

6518 ms

banner_web_smart.jpg

banner_web_smart.jpg

7274 ms

facebook.png

facebook.png

1312 ms

rss.png

rss.png

1596 ms

youtube.png

youtube.png

1863 ms

more.jpg

more.jpg

2095 ms

hotprod_ECW7220-L_310x130.jpg

hotprod_ECW7220-L_310x130.jpg

3765 ms

hotprod_EWS4606_310x130.jpg

hotprod_EWS4606_310x130.jpg

6205 ms

case_studies.jpg

case_studies.jpg

6407 ms

chosetool.jpg

chosetool.jpg

6649 ms

Button02-2.jpg

Button02-2.jpg

6658 ms

Computex%202015_banner.jpg

Computex%202015_banner.jpg

6991 ms

ECView_f.0416.jpg

ECView_f.0416.jpg

8663 ms

Exhibition2015-3.jpg

Exhibition2015-3.jpg

6933 ms

NewsLetter--2015.jpg

NewsLetter--2015.jpg

7178 ms

reg.jpg

reg.jpg

7224 ms

lang.jpg

lang.jpg

7409 ms

search.jpg

search.jpg

7461 ms

searchbutton.jpg

searchbutton.jpg

7478 ms

ga.js

ga.js

8 ms

__utm.gif

__utm.gif

14 ms

m_switch01.jpg

m_switch01.jpg

8777 ms

m_switch02.jpg

m_switch02.jpg

8753 ms

m_switch03.jpg

m_switch03.jpg

8804 ms

m_switch04.jpg

m_switch04.jpg

8589 ms

m_switch05.jpg

m_switch05.jpg

8682 ms

m_switch06.jpg

m_switch06.jpg

9737 ms

m_switch07.jpg

m_switch07.jpg

8874 ms

m_solution.jpg

m_solution.jpg

8739 ms

m_space.png

m_space.png

9943 ms

m_support.jpg

m_support.jpg

10213 ms

m_where.jpg

m_where.jpg

9805 ms

loading.gif

loading.gif

9012 ms

hot_bg.jpg

hot_bg.jpg

9114 ms

button_bg.jpg

button_bg.jpg

9334 ms

button_previous.jpg

button_previous.jpg

9068 ms

button_next.jpg

button_next.jpg

8913 ms

footer-bg.png

footer-bg.png

8686 ms

arrows.png

arrows.png

251 ms

bullets.png

bullets.png

220 ms

SEO Factors

edge-core.com SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Edge-core.com can be misinterpreted by Google and other search engines. Our service has detected that English 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 Edge-core.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

edge-core.com

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