Tools & Wizards About Us
epaper.guardian.ng screenshot

Report Summary

  • 35

    Performance

    Renders faster than
    55% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

epaper.guardian.ng

Guardian Nigeria ePaper – Just another WordPress site

Page Load Speed

6.9 sec in total

First Response

1.5 sec

Resources Loaded

5 sec

Page Rendered

420 ms

epaper.guardian.ng screenshot

About Website

Visit epaper.guardian.ng now to see the best up-to-date EPaper Guardian content for Nigeria and also check out these interesting facts you probably never knew about epaper.guardian.ng

Visit epaper.guardian.ng

Key Findings

We analyzed Epaper.guardian.ng page load time and found that the first response time was 1.5 sec and then it took 5.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

epaper.guardian.ng performance score

35

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.7 s

13/100

10%

LCP (Largest Contentful Paint)

Value12.2 s

0/100

25%

SI (Speed Index)

Value7.7 s

24/100

10%

TBT (Total Blocking Time)

Value560 ms

52/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value20.6 s

2/100

10%

Network Requests Diagram

epaper.guardian.ng

1480 ms

style.min.css

20 ms

woocommerce-layout.css

277 ms

woocommerce.css

288 ms

style.css

282 ms

Our browser made a total of 78 requests to load all elements on the main page. We found that 90% of them (70 requests) were addressed to the original Epaper.guardian.ng, 8% (6 requests) were made to Fonts.gstatic.com and 1% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Epaper.guardian.ng.

Page Optimization Overview & Recommendations

Page size can be reduced by 80.1 kB (5%)

Content Size

1.7 MB

After Optimization

1.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Epaper.guardian.ng 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. 65% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 38.1 kB

  • Original 50.4 kB
  • After minification 49.6 kB
  • After compression 12.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. 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 38.1 kB or 76% of the original size.

Image Optimization

-3%

Potential reduce by 34.3 kB

  • Original 1.1 MB
  • After minification 1.0 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. EPaper Guardian images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 5.9 kB

  • Original 455.5 kB
  • After minification 455.5 kB
  • After compression 449.6 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. This website has mostly compressed JavaScripts.

CSS Optimization

-2%

Potential reduce by 1.9 kB

  • Original 94.1 kB
  • After minification 94.1 kB
  • After compression 92.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. Epaper.guardian.ng has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 64 (90%)

Requests Now

71

After Optimization

7

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

epaper.guardian.ng

epaper.guardian.ng

1480 ms

style.min.css

style.min.css

20 ms

woocommerce-layout.css

woocommerce-layout.css

277 ms

woocommerce.css

woocommerce.css

288 ms

style.css

style.css

282 ms

css2

css2

42 ms

themify-icons.min.css

themify-icons.min.css

291 ms

dflip.min.css

dflip.min.css

26 ms

heateor-social-login-public.css

heateor-social-login-public.css

297 ms

dashicons.min.css

dashicons.min.css

436 ms

thickbox.css

thickbox.css

545 ms

jquery.min.js

jquery.min.js

694 ms

jquery-migrate.min.js

jquery-migrate.min.js

556 ms

jquery.blockUI.min.js

jquery.blockUI.min.js

563 ms

add-to-cart.min.js

add-to-cart.min.js

566 ms

js.cookie.min.js

js.cookie.min.js

445 ms

woocommerce.min.js

woocommerce.min.js

788 ms

js

js

168 ms

wc-blocks.css

wc-blocks.css

551 ms

sourcebuster.min.js

sourcebuster.min.js

853 ms

order-attribution.min.js

order-attribution.min.js

854 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

855 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

856 ms

wp-polyfill.min.js

wp-polyfill.min.js

1100 ms

react.min.js

react.min.js

998 ms

hooks.min.js

hooks.min.js

1115 ms

deprecated.min.js

deprecated.min.js

1116 ms

dom.min.js

dom.min.js

1117 ms

react-dom.min.js

react-dom.min.js

1377 ms

escape-html.min.js

escape-html.min.js

1270 ms

element.min.js

element.min.js

1369 ms

is-shallow-equal.min.js

is-shallow-equal.min.js

1116 ms

i18n.min.js

i18n.min.js

1388 ms

keycodes.min.js

keycodes.min.js

1390 ms

priority-queue.min.js

priority-queue.min.js

1393 ms

compose.min.js

compose.min.js

1281 ms

private-apis.min.js

private-apis.min.js

1559 ms

redux-routine.min.js

redux-routine.min.js

1639 ms

data.min.js

data.min.js

1656 ms

lodash.min.js

lodash.min.js

1775 ms

wc-blocks-registry.js

wc-blocks-registry.js

1509 ms

url.min.js

url.min.js

1402 ms

api-fetch.min.js

api-fetch.min.js

1531 ms

wc-settings.js

wc-settings.js

1558 ms

data-controls.min.js

data-controls.min.js

1626 ms

html-entities.min.js

html-entities.min.js

1645 ms

notices.min.js

notices.min.js

1515 ms

wc-blocks-middleware.js

wc-blocks-middleware.js

1360 ms

wc-blocks-data.js

wc-blocks-data.js

1666 ms

dom-ready.min.js

dom-ready.min.js

1533 ms

a11y.min.js

a11y.min.js

1566 ms

primitives.min.js

primitives.min.js

1363 ms

warning.min.js

warning.min.js

1639 ms

blocks-components.js

blocks-components.js

1567 ms

blocks-checkout.js

blocks-checkout.js

1106 ms

order-attribution-blocks.min.js

order-attribution-blocks.min.js

1384 ms

verify-payment.min.js

verify-payment.min.js

1504 ms

pinch-zoom.umd.js

pinch-zoom.umd.js

1541 ms

KFOmCnqEu92Fr1Me5Q.ttf

KFOmCnqEu92Fr1Me5Q.ttf

120 ms

KFOlCnqEu92Fr1MmEU9vAw.ttf

KFOlCnqEu92Fr1MmEU9vAw.ttf

156 ms

KFOlCnqEu92Fr1MmSU5vAw.ttf

KFOlCnqEu92Fr1MmSU5vAw.ttf

208 ms

KFOkCnqEu92Fr1MmgWxP.ttf

KFOkCnqEu92Fr1MmgWxP.ttf

207 ms

KFOlCnqEu92Fr1MmWUlvAw.ttf

KFOlCnqEu92Fr1MmWUlvAw.ttf

211 ms

KFOlCnqEu92Fr1MmYUtvAw.ttf

KFOlCnqEu92Fr1MmYUtvAw.ttf

214 ms

custom.js

custom.js

1615 ms

subscriptions.min.js

subscriptions.min.js

1484 ms

pdf.js

pdf.js

1140 ms

reader.min.js

reader.min.js

1283 ms

pdf-render.js

pdf-render.js

1512 ms

dflip.min.js

dflip.min.js

1651 ms

thickbox.js

thickbox.js

1295 ms

heateor-social-login-public.js

heateor-social-login-public.js

1400 ms

loading.gif

loading.gif

1407 ms

guardian-conscience.png

guardian-conscience.png

1509 ms

ads.png

ads.png

1768 ms

FRONT-2-scaled.jpg

FRONT-2-scaled.jpg

1200 ms

loadingAnimation.gif

loadingAnimation.gif

410 ms

woocommerce-smallscreen.css

woocommerce-smallscreen.css

272 ms

Accessibility Review

epaper.guardian.ng accessibility score

100

Accessibility Issues

Best Practices

epaper.guardian.ng best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

epaper.guardian.ng SEO score

92

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

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Epaper.guardian.ng can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Epaper.guardian.ng 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

epaper.guardian.ng

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