Tools & Wizards About Us
etx.ng screenshot

Report Summary

  • 35

    Performance

    Renders faster than
    55% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

etx.ng

ETX.NG: Electronic Transcript & Verification Exchange - Nigeria

Page Load Speed

4.3 sec in total

First Response

1.1 sec

Resources Loaded

3.1 sec

Page Rendered

142 ms

etx.ng screenshot

About Website

Click here to check amazing ETX content for Nigeria. Otherwise, check out these important facts you probably never knew about etx.ng

We’re connecting the education sector in Nigeria with the people who interact with it; through electronic credentials management.

Visit etx.ng

Key Findings

We analyzed Etx.ng page load time and found that the first response time was 1.1 sec and then it took 3.2 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

etx.ng performance score

35

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.8 s

5/100

10%

LCP (Largest Contentful Paint)

Value8.8 s

1/100

25%

SI (Speed Index)

Value8.5 s

18/100

10%

TBT (Total Blocking Time)

Value80 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value1.127

1/100

15%

TTI (Time to Interactive)

Value10.2 s

25/100

10%

Network Requests Diagram

etx.ng

1080 ms

style.min.css

413 ms

css

42 ms

style.css

193 ms

jquery.min.js

477 ms

Our browser made a total of 49 requests to load all elements on the main page. We found that 86% of them (42 requests) were addressed to the original Etx.ng, 8% (4 requests) were made to Fonts.googleapis.com and 2% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Etx.ng.

Page Optimization Overview & Recommendations

Page size can be reduced by 558.2 kB (39%)

Content Size

1.4 MB

After Optimization

891.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Etx.ng main page is 1.4 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. 25% of websites need less resources to load. Images take 755.7 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 30.4 kB

  • Original 37.2 kB
  • After minification 29.4 kB
  • After compression 6.8 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 7.8 kB, which is 21% 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 30.4 kB or 82% of the original size.

Image Optimization

-7%

Potential reduce by 53.7 kB

  • Original 755.7 kB
  • After minification 702.0 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. ETX images are well optimized though.

JavaScript Optimization

-63%

Potential reduce by 239.8 kB

  • Original 381.0 kB
  • After minification 375.5 kB
  • After compression 141.2 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 239.8 kB or 63% of the original size.

CSS Optimization

-85%

Potential reduce by 234.3 kB

  • Original 275.4 kB
  • After minification 264.7 kB
  • After compression 41.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. Etx.ng needs all CSS files to be minified and compressed as it can save up to 234.3 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 32 (67%)

Requests Now

48

After Optimization

16

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

etx.ng

etx.ng

1080 ms

style.min.css

style.min.css

413 ms

css

css

42 ms

style.css

style.css

193 ms

jquery.min.js

jquery.min.js

477 ms

jquery-migrate.min.js

jquery-migrate.min.js

288 ms

custom.js

custom.js

383 ms

style.css

style.css

290 ms

responsive.css

responsive.css

288 ms

page3.css

page3.css

382 ms

page1.css

page1.css

383 ms

bootstrap.min.css

bootstrap.min.css

576 ms

css

css

106 ms

css

css

62 ms

css

css

62 ms

owl.carousel.css

owl.carousel.css

414 ms

owl.theme.default.css

owl.theme.default.css

488 ms

jquery.min.js

jquery.min.js

26 ms

bootstrap.min.js

bootstrap.min.js

571 ms

js

js

65 ms

owl.carousel.js

owl.carousel.js

543 ms

core.min.js

core.min.js

480 ms

menu.min.js

menu.min.js

541 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

542 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

639 ms

wp-polyfill.min.js

wp-polyfill.min.js

640 ms

dom-ready.min.js

dom-ready.min.js

641 ms

hooks.min.js

hooks.min.js

642 ms

i18n.min.js

i18n.min.js

642 ms

a11y.min.js

a11y.min.js

643 ms

autocomplete.min.js

autocomplete.min.js

674 ms

mouse.min.js

mouse.min.js

731 ms

slider.min.js

slider.min.js

731 ms

jquery.form.min.js

jquery.form.min.js

732 ms

jquery.ui.touch-punch.js

jquery.ui.touch-punch.js

734 ms

body-bg.png

body-bg.png

175 ms

top-head-bg.png

top-head-bg.png

206 ms

logo.png

logo.png

557 ms

slide1.png

slide1.png

296 ms

Nneka_4.jpg

Nneka_4.jpg

483 ms

Israel1_.jpg

Israel1_.jpg

467 ms

undergraduate_schools.png

undergraduate_schools.png

279 ms

pcb.png

pcb.png

307 ms

Receive-Document.png

Receive-Document.png

383 ms

Screen-Shot-2023-09-25-at-8.40.20-AM.png

Screen-Shot-2023-09-25-at-8.40.20-AM.png

392 ms

facebook.png

facebook.png

403 ms

twitter.png

twitter.png

480 ms

linkdin.png

linkdin.png

487 ms

font

font

17 ms

Accessibility Review

etx.ng accessibility score

83

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.

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

etx.ng best practices score

83

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

SEO Factors

etx.ng SEO score

93

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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 Etx.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 Etx.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

etx.ng

Open Graph data is detected on the main page of ETX. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: