Tools & Wizards About Us
epigro.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

epigro.com

Solar Power Company in Sri Lanka - Solar Panels and Systems - Epigro

Page Load Speed

2.2 sec in total

First Response

163 ms

Resources Loaded

1.7 sec

Page Rendered

271 ms

epigro.com screenshot

About Website

Visit epigro.com now to see the best up-to-date Epigro content and also check out these interesting facts you probably never knew about epigro.com

Sri Lanka's expert solar power installers. Epigro showcases a huge range of solar panels for grid connect inverters and Solar Panels, also LED Lighting systems

Visit epigro.com

Key Findings

We analyzed Epigro.com page load time and found that the first response time was 163 ms and then it took 2 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.

Performance Metrics

epigro.com performance score

0

Network Requests Diagram

epigro.com

163 ms

epigro.com

290 ms

css

26 ms

css

17 ms

video.popup.css

71 ms

Our browser made a total of 50 requests to load all elements on the main page. We found that 76% of them (38 requests) were addressed to the original Epigro.com, 20% (10 requests) were made to Fonts.gstatic.com and 4% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (836 ms) belongs to the original domain Epigro.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 21.4 kB (4%)

Content Size

569.2 kB

After Optimization

547.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Epigro.com main page is 569.2 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. Images take 514.8 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 14.6 kB

  • Original 18.9 kB
  • After minification 16.5 kB
  • After compression 4.3 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. This page needs HTML code to be minified as it can gain 2.3 kB, which is 12% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 14.6 kB or 77% of the original size.

Image Optimization

-0%

Potential reduce by 2.4 kB

  • Original 514.8 kB
  • After minification 512.4 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. Epigro images are well optimized though.

JavaScript Optimization

-11%

Potential reduce by 3.6 kB

  • Original 33.4 kB
  • After minification 33.4 kB
  • After compression 29.7 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 3.6 kB or 11% of the original size.

CSS Optimization

-35%

Potential reduce by 791 B

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

Requests Breakdown

Number of requests can be reduced by 20 (63%)

Requests Now

32

After Optimization

12

  • Images
  • JavaScript
  • CSS

The browser has sent 32 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Epigro. 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 11 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

epigro.com

epigro.com

163 ms

epigro.com

epigro.com

290 ms

css

css

26 ms

css

css

17 ms

video.popup.css

video.popup.css

71 ms

animate.css

animate.css

140 ms

icomoon.css

icomoon.css

208 ms

bootstrap.css

bootstrap.css

279 ms

flexslider.css

flexslider.css

211 ms

flaticon.css

flaticon.css

214 ms

owl.carousel.min.css

owl.carousel.min.css

214 ms

owl.theme.default.min.css

owl.theme.default.min.css

213 ms

style.css

style.css

284 ms

modernizr-2.6.2.min.js

modernizr-2.6.2.min.js

288 ms

jquery.min.js

jquery.min.js

427 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

325 ms

bootstrap.min.js

bootstrap.min.js

325 ms

jquery.waypoints.min.js

jquery.waypoints.min.js

355 ms

jquery.flexslider-min.js

jquery.flexslider-min.js

354 ms

sticky-kit.min.js

sticky-kit.min.js

355 ms

owl.carousel.min.js

owl.carousel.min.js

366 ms

jquery.countTo.js

jquery.countTo.js

367 ms

main.js

main.js

420 ms

video.popup.js

video.popup.js

421 ms

epigro-logo-2.png

epigro-logo-2.png

120 ms

loader.gif

loader.gif

140 ms

img_bg_1.jpg

img_bg_1.jpg

725 ms

img_bg_2.jpg

img_bg_2.jpg

720 ms

img_bg_3.jpg

img_bg_3.jpg

788 ms

services-1.jpg

services-1.jpg

586 ms

services-2.jpg

services-2.jpg

587 ms

services-3.jpg

services-3.jpg

665 ms

services-4.jpg

services-4.jpg

800 ms

services-5.jpg

services-5.jpg

801 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4kaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4kaVQ.woff

23 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4kaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4kaVQ.woff

23 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4kaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4kaVQ.woff

24 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4kaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4kaVQ.woff

24 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4kaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4kaVQ.woff

25 ms

Flaticon.svg

Flaticon.svg

712 ms

Flaticon.woff

Flaticon.woff

763 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkWVQexg.woff

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkWVQexg.woff

40 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk5hkWVQexg.woff

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk5hkWVQexg.woff

32 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkxhjWVQexg.woff

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkxhjWVQexg.woff

30 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkyFjWVQexg.woff

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkyFjWVQexg.woff

31 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk0ZjWVQexg.woff

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk0ZjWVQexg.woff

39 ms

icomoon.ttf

icomoon.ttf

836 ms

icomoon.ttf

icomoon.ttf

781 ms

icomoon.woff

icomoon.woff

70 ms

icomoon.svg

icomoon.svg

69 ms

SEO Factors

epigro.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 Epigro.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 Epigro.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

epigro.com

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