Tools & Wizards About Us
sesewa.org screenshot

Report Summary

  • 29

    Performance

    Renders faster than
    49% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 74% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

sesewa.org

SESEWA – Connecting Opportunities

Page Load Speed

5.4 sec in total

First Response

730 ms

Resources Loaded

4.2 sec

Page Rendered

444 ms

sesewa.org screenshot

About Website

Visit sesewa.org now to see the best up-to-date SESEWA content for Nigeria and also check out these interesting facts you probably never knew about sesewa.org

Visit sesewa.org

Key Findings

We analyzed Sesewa.org page load time and found that the first response time was 730 ms and then it took 4.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

sesewa.org performance score

29

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.3 s

3/100

10%

LCP (Largest Contentful Paint)

Value43.1 s

0/100

25%

SI (Speed Index)

Value21.8 s

0/100

10%

TBT (Total Blocking Time)

Value650 ms

46/100

30%

CLS (Cumulative Layout Shift)

Value0.053

98/100

15%

TTI (Time to Interactive)

Value29.1 s

0/100

10%

Network Requests Diagram

sesewa.org

730 ms

style.min.css

245 ms

styles.css

183 ms

hide-admin-bar-based-on-user-roles-public.css

184 ms

magnific-popup.css

185 ms

Our browser made a total of 107 requests to load all elements on the main page. We found that 95% of them (102 requests) were addressed to the original Sesewa.org, 3% (3 requests) were made to Fonts.googleapis.com and 1% (1 request) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (970 ms) relates to the external source Fonts.googleapis.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 450.0 kB (12%)

Content Size

3.6 MB

After Optimization

3.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Sesewa.org main page is 3.6 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. 70% of websites need less resources to load. Images take 2.7 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 99.8 kB

  • Original 121.0 kB
  • After minification 112.0 kB
  • After compression 21.2 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 99.8 kB or 82% of the original size.

Image Optimization

-8%

Potential reduce by 223.9 kB

  • Original 2.7 MB
  • After minification 2.5 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. SESEWA images are well optimized though.

JavaScript Optimization

-12%

Potential reduce by 56.0 kB

  • Original 470.1 kB
  • After minification 469.6 kB
  • After compression 414.1 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 56.0 kB or 12% of the original size.

CSS Optimization

-23%

Potential reduce by 70.2 kB

  • Original 299.3 kB
  • After minification 299.0 kB
  • After compression 229.1 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. Sesewa.org needs all CSS files to be minified and compressed as it can save up to 70.2 kB or 23% of the original size.

Requests Breakdown

Number of requests can be reduced by 81 (81%)

Requests Now

100

After Optimization

19

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

sesewa.org

sesewa.org

730 ms

style.min.css

style.min.css

245 ms

styles.css

styles.css

183 ms

hide-admin-bar-based-on-user-roles-public.css

hide-admin-bar-based-on-user-roles-public.css

184 ms

magnific-popup.css

magnific-popup.css

185 ms

perfect-scrollbar.css

perfect-scrollbar.css

185 ms

leaflet.css

leaflet.css

248 ms

elementor-icons.min.css

elementor-icons.min.css

249 ms

frontend-lite.min.css

frontend-lite.min.css

307 ms

swiper.min.css

swiper.min.css

251 ms

post-8603.css

post-8603.css

293 ms

frontend-lite.min.css

frontend-lite.min.css

305 ms

post-7187.css

post-7187.css

303 ms

css

css

970 ms

all-awesome.css

all-awesome.css

367 ms

flaticon.css

flaticon.css

310 ms

themify-icons.css

themify-icons.css

354 ms

animate.css

animate.css

370 ms

bootstrap.css

bootstrap.css

425 ms

slick.css

slick.css

372 ms

magnific-popup.css

magnific-popup.css

372 ms

perfect-scrollbar.css

perfect-scrollbar.css

415 ms

sliding-menu.min.css

sliding-menu.min.css

434 ms

template.css

template.css

548 ms

update.css

update.css

433 ms

style.css

style.css

437 ms

style.css

style.css

476 ms

css

css

34 ms

fontawesome.min.css

fontawesome.min.css

488 ms

solid.min.css

solid.min.css

491 ms

jquery.min.js

jquery.min.js

567 ms

jquery-migrate.min.js

jquery-migrate.min.js

492 ms

hide-admin-bar-based-on-user-roles-public.js

hide-admin-bar-based-on-user-roles-public.js

537 ms

js

js

74 ms

widget-nav-menu.min.css

widget-nav-menu.min.css

489 ms

widget-icon-list.min.css

widget-icon-list.min.css

352 ms

post-7845.css

post-7845.css

345 ms

dashicons.min.css

dashicons.min.css

435 ms

select2.min.css

select2.min.css

385 ms

cmb2-front.min.css

cmb2-front.min.css

389 ms

style.min.css

style.min.css

388 ms

post-7892.css

post-7892.css

389 ms

animations.min.css

animations.min.css

390 ms

brands.min.css

brands.min.css

447 ms

bootstrap.min.js

bootstrap.min.js

431 ms

slick.min.js

slick.min.js

429 ms

jquery.magnific-popup.min.js

jquery.magnific-popup.min.js

427 ms

jquery.unveil.js

jquery.unveil.js

428 ms

perfect-scrollbar.jquery.min.js

perfect-scrollbar.jquery.min.js

430 ms

waypoints.min.js

waypoints.min.js

433 ms

sticky.min.js

sticky.min.js

435 ms

sliding-menu.js

sliding-menu.js

431 ms

functions.js

functions.js

430 ms

index.js

index.js

386 ms

index.js

index.js

416 ms

jquery.magnific-popup.min.js

jquery.magnific-popup.min.js

441 ms

core.min.js

core.min.js

441 ms

mouse.min.js

mouse.min.js

428 ms

slider.min.js

slider.min.js

398 ms

jquery.ui.touch-punch.min.js

jquery.ui.touch-punch.min.js

381 ms

main.js

main.js

427 ms

perfect-scrollbar.jquery.min.js

perfect-scrollbar.jquery.min.js

426 ms

main.js

main.js

447 ms

jquery.highlight.js

jquery.highlight.js

409 ms

leaflet.js

leaflet.js

689 ms

Control.Geocoder.js

Control.Geocoder.js

394 ms

leaflet.markercluster.js

leaflet.markercluster.js

433 ms

LeafletHtmlIcon.js

LeafletHtmlIcon.js

388 ms

Leaflet.GoogleMutant.js

Leaflet.GoogleMutant.js

392 ms

job.js

job.js

391 ms

job-map.js

job-map.js

381 ms

jquery.smartmenus.min.js

jquery.smartmenus.min.js

610 ms

select2.min.js

select2.min.js

611 ms

hide-show.min.js

hide-show.min.js

574 ms

cmb2.min.js

cmb2.min.js

571 ms

webpack-pro.runtime.min.js

webpack-pro.runtime.min.js

570 ms

webpack.runtime.min.js

webpack.runtime.min.js

571 ms

frontend-modules.min.js

frontend-modules.min.js

570 ms

hooks.min.js

hooks.min.js

525 ms

i18n.min.js

i18n.min.js

511 ms

frontend.min.js

frontend.min.js

510 ms

frontend.min.js

frontend.min.js

510 ms

elements-handlers.min.js

elements-handlers.min.js

511 ms

Sesewa-logo-high.png

Sesewa-logo-high.png

259 ms

job-seeking.gif

job-seeking.gif

500 ms

africa-globe.png

africa-globe.png

98 ms

inheritance.gif

inheritance.gif

393 ms

teach-1.gif

teach-1.gif

289 ms

learning.gif

learning.gif

488 ms

creativity.gif

creativity.gif

493 ms

image-home08-5.png

image-home08-5.png

261 ms

slider16.jpg

slider16.jpg

497 ms

Jennifer-Onuorah.png

Jennifer-Onuorah.png

350 ms

Evet-Vodunu.png

Evet-Vodunu.png

412 ms

Emmanuel-Afolabi.png

Emmanuel-Afolabi.png

456 ms

tab1.jpg

tab1.jpg

474 ms

cross.png

cross.png

518 ms

sesewa-footer-logo.png

sesewa-footer-logo.png

535 ms

bg-h15.jpg

bg-h15.jpg

629 ms

css

css

26 ms

font

font

151 ms

fa-solid-900.woff

fa-solid-900.woff

521 ms

fa-solid-900.woff

fa-solid-900.woff

520 ms

fa-regular-400.woff

fa-regular-400.woff

521 ms

fa-brands-400.woff

fa-brands-400.woff

518 ms

fa-brands-400.woff

fa-brands-400.woff

504 ms

themify.woff

themify.woff

566 ms

Accessibility Review

sesewa.org accessibility score

90

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

ARIA IDs are not unique

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

sesewa.org 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

sesewa.org SEO score

86

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

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 Sesewa.org 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 Sesewa.org 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

sesewa.org

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