Tools & Wizards About Us
epigro.com screenshot

Report Summary

  • 79

    Performance

    Renders faster than
    85% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 61% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 67

    SEO

    Google-friendlier than
    26% of websites

epigro.com

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

Page Load Speed

3.6 sec in total

First Response

229 ms

Resources Loaded

3.1 sec

Page Rendered

227 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 229 ms and then it took 3.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

epigro.com performance score

79

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.6 s

64/100

10%

LCP (Largest Contentful Paint)

Value4.0 s

49/100

25%

SI (Speed Index)

Value4.6 s

71/100

10%

TBT (Total Blocking Time)

Value10 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.004

100/100

15%

TTI (Time to Interactive)

Value4.7 s

80/100

10%

Network Requests Diagram

epigro.com

229 ms

epigro.com

408 ms

css

40 ms

css

60 ms

video.popup.css

129 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 (1.7 sec) belongs to the original domain Epigro.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 46.6 kB (2%)

Content Size

2.5 MB

After Optimization

2.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Epigro.com main page is 2.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. 45% of websites need less resources to load. Images take 2.3 MB 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 2.3 MB
  • After minification 2.3 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. Epigro images are well optimized though.

JavaScript Optimization

-17%

Potential reduce by 14.0 kB

  • Original 84.3 kB
  • After minification 84.3 kB
  • After compression 70.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 14.0 kB or 17% of the original size.

CSS Optimization

-31%

Potential reduce by 15.6 kB

  • Original 49.9 kB
  • After minification 49.9 kB
  • After compression 34.3 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 15.6 kB or 31% 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

229 ms

epigro.com

epigro.com

408 ms

css

css

40 ms

css

css

60 ms

video.popup.css

video.popup.css

129 ms

animate.css

animate.css

258 ms

icomoon.css

icomoon.css

360 ms

bootstrap.css

bootstrap.css

437 ms

flexslider.css

flexslider.css

363 ms

flaticon.css

flaticon.css

372 ms

owl.carousel.min.css

owl.carousel.min.css

397 ms

owl.theme.default.min.css

owl.theme.default.min.css

721 ms

style.css

style.css

482 ms

modernizr-2.6.2.min.js

modernizr-2.6.2.min.js

549 ms

jquery.min.js

jquery.min.js

613 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

581 ms

bootstrap.min.js

bootstrap.min.js

615 ms

jquery.waypoints.min.js

jquery.waypoints.min.js

604 ms

jquery.flexslider-min.js

jquery.flexslider-min.js

670 ms

sticky-kit.min.js

sticky-kit.min.js

803 ms

owl.carousel.min.js

owl.carousel.min.js

1327 ms

jquery.countTo.js

jquery.countTo.js

805 ms

main.js

main.js

1034 ms

video.popup.js

video.popup.js

1163 ms

epigro-logo-2.png

epigro-logo-2.png

188 ms

loader.gif

loader.gif

166 ms

img_bg_1.jpg

img_bg_1.jpg

620 ms

img_bg_2.jpg

img_bg_2.jpg

876 ms

img_bg_3.jpg

img_bg_3.jpg

632 ms

services-1.jpg

services-1.jpg

1205 ms

services-2.jpg

services-2.jpg

1092 ms

services-3.jpg

services-3.jpg

1728 ms

services-4.jpg

services-4.jpg

769 ms

services-5.jpg

services-5.jpg

810 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4kaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4kaVQ.woff

47 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4kaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4kaVQ.woff

58 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4kaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4kaVQ.woff

59 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4kaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4kaVQ.woff

59 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4kaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4kaVQ.woff

59 ms

Flaticon.svg

Flaticon.svg

878 ms

Flaticon.woff

Flaticon.woff

879 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkWVQexg.woff

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkWVQexg.woff

19 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk5hkWVQexg.woff

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk5hkWVQexg.woff

17 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkxhjWVQexg.woff

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkxhjWVQexg.woff

19 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkyFjWVQexg.woff

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkyFjWVQexg.woff

20 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk0ZjWVQexg.woff

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk0ZjWVQexg.woff

20 ms

icomoon.ttf

icomoon.ttf

1268 ms

icomoon.ttf

icomoon.ttf

1125 ms

icomoon.woff

icomoon.woff

106 ms

icomoon.svg

icomoon.svg

96 ms

Accessibility Review

epigro.com accessibility score

86

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

Links do not have a discernible name

Best Practices

epigro.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

epigro.com SEO score

67

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

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: