Tools & Wizards About Us
e-pao.net screenshot

Report Summary

  • 49

    Performance

    Renders faster than
    67% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 83% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

e-pao.net

Manipur - E-Pao! :: Complete e-platform for Manipuris

Page Load Speed

2.6 sec in total

First Response

50 ms

Resources Loaded

2.2 sec

Page Rendered

304 ms

e-pao.net screenshot

About Website

Visit e-pao.net now to see the best up-to-date E Pao content for India and also check out these interesting facts you probably never knew about e-pao.net

Complete e-platform for Manipuris. A Platform for Manipuries to showcase their rich cultural heritage and talents. Manipur's First Online News Service

Visit e-pao.net

Key Findings

We analyzed E-pao.net page load time and found that the first response time was 50 ms and then it took 2.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

e-pao.net performance score

49

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.0 s

9/100

10%

LCP (Largest Contentful Paint)

Value6.2 s

11/100

25%

SI (Speed Index)

Value7.5 s

26/100

10%

TBT (Total Blocking Time)

Value340 ms

74/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value6.8 s

55/100

10%

Network Requests Diagram

e-pao.net

50 ms

e-pao.net

97 ms

portalMain.css

272 ms

jcalendar.css

292 ms

jplayer.blue.monday.css

277 ms

Our browser made a total of 93 requests to load all elements on the main page. We found that 43% of them (40 requests) were addressed to the original E-pao.net, 23% (21 requests) were made to Static.xx.fbcdn.net and 8% (7 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain E-pao.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 131.8 kB (23%)

Content Size

584.1 kB

After Optimization

452.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of E-pao.net main page is 584.1 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 299.1 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 78.6 kB

  • Original 100.2 kB
  • After minification 91.9 kB
  • After compression 21.7 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 78.6 kB or 78% of the original size.

Image Optimization

-2%

Potential reduce by 1.8 kB

  • Original 115.9 kB
  • After minification 114.1 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. E Pao images are well optimized though.

JavaScript Optimization

-17%

Potential reduce by 50.2 kB

  • Original 299.1 kB
  • After minification 299.1 kB
  • After compression 248.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 50.2 kB or 17% of the original size.

CSS Optimization

-2%

Potential reduce by 1.3 kB

  • Original 68.8 kB
  • After minification 68.8 kB
  • After compression 67.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. E-pao.net has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 58 (65%)

Requests Now

89

After Optimization

31

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

e-pao.net

e-pao.net

50 ms

e-pao.net

e-pao.net

97 ms

portalMain.css

portalMain.css

272 ms

jcalendar.css

jcalendar.css

292 ms

jplayer.blue.monday.css

jplayer.blue.monday.css

277 ms

epversion09.js

epversion09.js

271 ms

jquery.min.js

jquery.min.js

43 ms

epmayekscript.js

epmayekscript.js

291 ms

epHLMayekscript.js

epHLMayekscript.js

321 ms

jquery.jplayer.min.js

jquery.jplayer.min.js

523 ms

detectMobile.js

detectMobile.js

517 ms

jsapi

jsapi

40 ms

jquery.cycle.js

jquery.cycle.js

554 ms

slideshow.js

slideshow.js

554 ms

combination_widget.js

combination_widget.js

49 ms

widgets.js

widgets.js

49 ms

jcalendar.js

jcalendar.js

553 ms

epArcValidateNew.js

epArcValidateNew.js

610 ms

loader.js

loader.js

21 ms

logo.gif

logo.gif

301 ms

epChronicle_202105.gif

epChronicle_202105.gif

95 ms

head_link_sep.gif

head_link_sep.gif

308 ms

head_link_seplight.gif

head_link_seplight.gif

299 ms

search_go.gif

search_go.gif

309 ms

fb.gif

fb.gif

377 ms

gplus.png

gplus.png

217 ms

tr.gif

tr.gif

513 ms

rs.gif

rs.gif

657 ms

bigelowii_20240505_sm.jpg

bigelowii_20240505_sm.jpg

658 ms

COCOMI_20240504_sm.jpg

COCOMI_20240504_sm.jpg

656 ms

Heritage_20240503_sm.jpg

Heritage_20240503_sm.jpg

656 ms

Rajmuhon_20240502_sm.jpg

Rajmuhon_20240502_sm.jpg

656 ms

Athouba_20240501_2_sm.jpg

Athouba_20240501_2_sm.jpg

1332 ms

Rally_20240505_sm.jpg

Rally_20240505_sm.jpg

1343 ms

news_photo_05.jpg

news_photo_05.jpg

1342 ms

page.php

page.php

188 ms

link_bullet_org.gif

link_bullet_org.gif

1161 ms

link_bullet.gif

link_bullet.gif

1161 ms

tab_heads1.gif

tab_heads1.gif

1307 ms

tab_sep_portal1.gif

tab_sep_portal1.gif

1297 ms

avatar92.jpg

avatar92.jpg

147 ms

noavatar92.png

noavatar92.png

180 ms

OkU1MeV0Q5A

OkU1MeV0Q5A

329 ms

7v5Z-G4mMR4

7v5Z-G4mMR4

557 ms

T93qGLRN3Nw

T93qGLRN3Nw

578 ms

avatar92.jpg

avatar92.jpg

172 ms

avatar92.jpg

avatar92.jpg

177 ms

wiget_bg_border.png

wiget_bg_border.png

1266 ms

AIRLOGO.jpg

AIRLOGO.jpg

1359 ms

jplayer.blue.monday.jpg

jplayer.blue.monday.jpg

1360 ms

ratha.ttf

ratha.ttf

1264 ms

widget.min.js

widget.min.js

197 ms

analytics.js

analytics.js

140 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

54 ms

slidenavcount.gif

slidenavcount.gif

1236 ms

gzCy-hx--rE.css

gzCy-hx--rE.css

75 ms

lhzi7nlXu3o.css

lhzi7nlXu3o.css

88 ms

uDSuoOQ7RZ1.css

uDSuoOQ7RZ1.css

92 ms

RsWZ-myCkRn.js

RsWZ-myCkRn.js

114 ms

71nLmDRGsWE.js

71nLmDRGsWE.js

104 ms

teTZ2tZqwkq.js

teTZ2tZqwkq.js

96 ms

5hjr18zii08.js

5hjr18zii08.js

103 ms

zYzGplAqD4J.js

zYzGplAqD4J.js

101 ms

p55HfXW__mM.js

p55HfXW__mM.js

100 ms

btW70syVT6v.js

btW70syVT6v.js

101 ms

ywjcIatsjHa.js

ywjcIatsjHa.js

164 ms

4RIW-HrYocA.js

4RIW-HrYocA.js

186 ms

4Za9TE_Wiy4.js

4Za9TE_Wiy4.js

181 ms

OSjeAdWp3LG.js

OSjeAdWp3LG.js

193 ms

CkL1MBePXJW.js

CkL1MBePXJW.js

162 ms

8SEqTYRL4HT.js

8SEqTYRL4HT.js

209 ms

HzxD9aAXSyD.js

HzxD9aAXSyD.js

213 ms

qnn7MVQZYOT.js

qnn7MVQZYOT.js

215 ms

settings

settings

264 ms

collect

collect

35 ms

collect

collect

144 ms

js

js

338 ms

www-player.css

www-player.css

138 ms

www-embed-player.js

www-embed-player.js

135 ms

base.js

base.js

409 ms

89 ms

304628389_495969522535733_723898763287786294_n.png

304628389_495969522535733_723898763287786294_n.png

260 ms

UXtr_j2Fwe-.png

UXtr_j2Fwe-.png

64 ms

0T4g9t4AXAk.js

0T4g9t4AXAk.js

28 ms

7mzhNKqWkDi.js

7mzhNKqWkDi.js

97 ms

if_w.css

if_w.css

130 ms

angular-1.5.8.min.js

angular-1.5.8.min.js

225 ms

iApp.min.js

iApp.min.js

215 ms

timeline.e108540dddc96e4b707f5cf259a582d7.js

timeline.e108540dddc96e4b707f5cf259a582d7.js

127 ms

open.svg

open.svg

531 ms

71suEs83z0XiqH0n_P_GdL05qLj4eQk8ZwtXjY02tX0.js

71suEs83z0XiqH0n_P_GdL05qLj4eQk8ZwtXjY02tX0.js

173 ms

embed.js

embed.js

114 ms

main.js

main.js

100 ms

Accessibility Review

e-pao.net accessibility score

94

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

Best Practices

e-pao.net best practices score

58

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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

e-pao.net SEO score

91

Search Engine Optimization Advices

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

    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 E-pao.net 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 E-pao.net 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

e-pao.net

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