https://futo.edu.ng/
25
Performance
90
Accessibility
80
Best Practices
88
SEO
Progressive Web App
0–49 50–89 90–100
Metrics
First Contentful Paint
16.1 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.
Speed Index
38.0 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
Largest Contentful Paint
18.4 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more
Time to Interactive
35.3 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Total Blocking Time
840 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more.
Cumulative Layout Shift
0.051
Cumulative Layout Shift measures the movement of visible elements within the viewport. Learn more.
Values are estimated and may vary. The performance score is calculated directly from these metrics.See calculator.
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Show audits relevant to:
OpportunitiesThese suggestions can help your page load faster. They don't directly affect the Performance score.
Opportunity
Estimated Savings
Enable text compression
18.49 s
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.FCPLCP
WordPressYou can enable text compression in your web server configuration.
URL
Transfer Size
Potential Savings
434.1 KiB
385.3 KiB
376.8 KiB
268.2 KiB
293.1 KiB
255.0 KiB
224.8 KiB
198.3 KiB
134.0 KiB
116.9 KiB
117.7 KiB
105.3 KiB
135.9 KiB
101.2 KiB
142.9 KiB
99.9 KiB
110.6 KiB
94.4 KiB
108.7 KiB
91.4 KiB
91.3 KiB
80.3 KiB
108.0 KiB
70.5 KiB
108.0 KiB
70.5 KiB
79.8 KiB
65.4 KiB
59.1 KiB
55.0 KiB
56.7 KiB
52.7 KiB
63.4 KiB
45.8 KiB
63.4 KiB
45.8 KiB
54.7 KiB
45.8 KiB
57.2 KiB
44.8 KiB
55.7 KiB
42.5 KiB
54.5 KiB
40.5 KiB
40.6 KiB
33.2 KiB
38.9 KiB
32.9 KiB
38.9 KiB
29.6 KiB
42.0 KiB
29.3 KiB
29.6 KiB
26.5 KiB
36.0 KiB
25.5 KiB
26.7 KiB
24.2 KiB
25.0 KiB
23.0 KiB
26.1 KiB
21.9 KiB
28.4 KiB
21.7 KiB
25.5 KiB
18.6 KiB
18.0 KiB
15.5 KiB
18.6 KiB
14.8 KiB
17.8 KiB
12.9 KiB
13.5 KiB
12.6 KiB
16.0 KiB
11.7 KiB
11.3 KiB
9.6 KiB
13.9 KiB
9.4 KiB
11.9 KiB
9.0 KiB
11.6 KiB
8.4 KiB
11.6 KiB
7.9 KiB
10.7 KiB
7.5 KiB
10.4 KiB
7.1 KiB
8.8 KiB
5.8 KiB
8.1 KiB
5.6 KiB
6.2 KiB
4.0 KiB
…lity/lity.min.js
(futo.edu.ng)
6.5 KiB
3.6 KiB
4.1 KiB
3.1 KiB
4.9 KiB
2.9 KiB
5.0 KiB
2.8 KiB
4.8 KiB
2.7 KiB
3.6 KiB
2.1 KiB
2.7 KiB
1.7 KiB
2.5 KiB
1.4 KiB
2.0 KiB
1.4 KiB
Eliminate render-blocking resources
13.13 s
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.FCPLCP
WordPressThere are a number of WordPress plugins that can help you inline critical assets or defer less important resources. Beware that optimizations provided by these plugins may break features of your theme or plugins, so you will likely need to make code changes.
URL
Transfer Size
Potential Savings
1.0 KiB
560 ms
10.3 KiB
1,560 ms
14.9 KiB
910 ms
13.7 KiB
760 ms
0.7 KiB
150 ms
3.5 KiB
300 ms
1.7 KiB
1,010 ms
59.5 KiB
4,020 ms
57.6 KiB
3,870 ms
26.4 KiB
2,210 ms
2.4 KiB
150 ms
1.0 KiB
150 ms
57.0 KiB
3,870 ms
3.0 KiB
1,010 ms
2.4 KiB
1,010 ms
/css?family=…
(fonts.googleapis.com)
1.0 KiB
960 ms
111.0 KiB
6,580 ms
225.2 KiB
10,790 ms
39.2 KiB
2,820 ms
2.4 KiB
860 ms
11.7 KiB
1,460 ms
118.1 KiB
7,030 ms
5.3 KiB
1,010 ms
4.4 KiB
1,010 ms
19.0 KiB
1,760 ms
13.8 KiB
1,460 ms
134.4 KiB
7,180 ms
1.4 KiB
860 ms
25.3 KiB
2,060 ms
27.1 KiB
2,210 ms
109.1 KiB
6,280 ms
91.6 KiB
5,520 ms
434.5 KiB
8,530 ms
29.9 KiB
2,360 ms
/css?family=…
(fonts.googleapis.com)
2.2 KiB
150 ms
15.8 KiB
910 ms
/css?family=…
(fonts.googleapis.com)
1.0 KiB
150 ms
29.7 KiB
1,660 ms
4.0 KiB
150 ms
11.9 KiB
1,460 ms
1.9 KiB
860 ms
4.0 KiB
1,010 ms
…lity/lity.min.js
(futo.edu.ng)
6.9 KiB
1,160 ms
108.3 KiB
3,870 ms
63.8 KiB
2,970 ms
5.3 KiB
1,010 ms
Reduce unused CSS
8.72 s
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn more.FCPLCP
WordPressConsider reducing, or switching, the number of WordPress plugins loading unused CSS in your page. To identify plugins that are adding extraneous CSS, try running code coverage in Chrome DevTools. You can identify the theme/plugin responsible from the URL of the stylesheet. Look out for plugins that have many stylesheets in the list which have a lot of red in code coverage. A plugin should only enqueue a stylesheet if it is actually used on the page.
URL
Transfer Size
Potential Savings
434.5 KiB
431.6 KiB
225.2 KiB
224.0 KiB
134.4 KiB
129.5 KiB
118.1 KiB
116.8 KiB
111.0 KiB
110.4 KiB
109.1 KiB
101.8 KiB
91.6 KiB
85.7 KiB
59.5 KiB
59.5 KiB
57.0 KiB
57.0 KiB
57.6 KiB
56.9 KiB
40.9 KiB
40.6 KiB
39.2 KiB
39.2 KiB
39.2 KiB
35.0 KiB
29.9 KiB
29.9 KiB
26.4 KiB
25.7 KiB
25.3 KiB
24.4 KiB
19.0 KiB
19.0 KiB
18.4 KiB
18.4 KiB
15.8 KiB
15.7 KiB
14.9 KiB
14.9 KiB
13.8 KiB
13.7 KiB
13.7 KiB
13.6 KiB
27.1 KiB
12.9 KiB
10.3 KiB
10.3 KiB
Reduce unused JavaScript
5.99 s
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn more.LCP
WordPressConsider reducing, or switching, the number of WordPress plugins loading unused JavaScript in your page. To identify plugins that are adding extraneous JS, try running code coverage in Chrome DevTools. You can identify the theme/plugin responsible from the URL of the script. Look out for plugins that have many scripts in the list which have a lot of red in code coverage. A plugin should only enqueue a script if it is actually used on the page.
URL
Transfer Size
Potential Savings
377.1 KiB
307.8 KiB
136.3 KiB
122.4 KiB
143.2 KiB
110.8 KiB
108.3 KiB
81.9 KiB
63.8 KiB
61.3 KiB
80.2 KiB
59.5 KiB
77.5 KiB
56.8 KiB
55.1 KiB
53.9 KiB
108.3 KiB
42.4 KiB
…7a/util.js
(maps.google.com)
90.7 KiB
39.4 KiB
56.1 KiB
35.0 KiB
42.4 KiB
33.4 KiB
…api/js?libraries=…
(maps.google.com)
55.1 KiB
30.0 KiB
…7a/common.js
(maps.google.com)
28.5 KiB
23.0 KiB
/gtag/js?id=UA-111…-1
(www.googletagmanager.com)
35.7 KiB
22.2 KiB
Reduce initial server response time
4.17 s
Keep the server response time for the main document short because all other requests depend on it. Learn more.FCPLCP
WordPressThemes, plugins, and server specifications all contribute to server response time. Consider finding a more optimized theme, carefully selecting an optimization plugin, and/or upgrading your server.
URL
Time Spent
4,270 ms
Use HTTP/2
3.46 s
HTTP/2 offers many benefits over HTTP/1.1, including binary headers and multiplexing. Learn more.
URL
Protocol
http/1.1
http/1.1
http/1.1
http/1.1
http/1.1
http/1.1
http/1.1
http/1.1
http/1.1
http/1.1
http/1.1
http/1.1
http/1.1
http/1.1
http/1.1
http/1.1
http/1.1
http/1.1
http/1.1
http/1.1
http/1.1
http/1.1
http/1.1
http/1.1
http/1.1
http/1.1
http/1.1
http/1.1
http/1.1
http/1.1
http/1.1
…lity/lity.min.js
(futo.edu.ng)
http/1.1
http/1.1
http/1.1
http/1.1
http/1.1
http/1.1
…16/en.png
(futo.edu.ng)
http/1.1
http/1.1
http/1.1
http/1.1
http/1.1
http/1.1
http/1.1
http/1.1
http/1.1
http/1.1
http/1.1
http/1.1
http/1.1
http/1.1
http/1.1
http/1.1
http/1.1
http/1.1
http/1.1
http/1.1
http/1.1
http/1.1
http/1.1
http/1.1
http/1.1
http/1.1
http/1.1
http/1.1
http/1.1
http/1.1
http/1.1
http/1.1
http/1.1
http/1.1
http/1.1
http/1.1
http/1.1
http/1.1
http/1.1
http/1.1
http/1.1
http/1.1
http/1.1
http/1.1
http/1.1
http/1.1
Serve images in next-gen formats
1.05 s
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more.
WordPressConsider using a plugin or service that will automatically convert your uploaded images to the optimal formats.
URL
Resource Size
Potential Savings
150.0 KiB
114.7 KiB
117.0 KiB
66.5 KiB
28.6 KiB
25.1 KiB
113.2 KiB
20.1 KiB
Avoid serving legacy JavaScript to modern browsers
0.33 s
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers. Learn MoreTBT
URL
Potential Savings
21.3 KiB
Date.prototype.toJSON
19.1 KiB
Date.now
19.1 KiB
Date.now
0.2 KiB
@babel/plugin-transform-classes
Minify CSS
0.23 s
Minifying CSS files can reduce network payload sizes. Learn more.FCPLCP
WordPressA number of WordPress plugins can speed up your site by concatenating, minifying, and compressing your styles. You may also want to use a build process to do this minification up-front if possible.
URL
Transfer Size
Potential Savings
225.2 KiB
19.3 KiB
109.1 KiB
11.5 KiB
39.2 KiB
11.3 KiB
39.2 KiB
7.5 KiB
91.6 KiB
6.4 KiB
40.9 KiB
5.6 KiB
Efficiently encode images
0.15 s
Optimized images load faster and consume less cellular data. Learn more.
WordPressConsider using an image optimization WordPress plugin that compresses your images while retaining quality.
URL
Resource Size
Potential Savings
117.0 KiB
4.4 KiB
DiagnosticsMore information about the performance of your application. These numbers don't directly affect the Performance score.
Ensure text remains visible during webfont load
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more.FCPLCP
URL
Potential Savings
950 ms
…v19/pxiEyp8kv….woff2
(fonts.gstatic.com)
1,820 ms
…v19/pxiByp8kv….woff2
(fonts.gstatic.com)
760 ms
…v19/pxiByp8kv….woff2
(fonts.gstatic.com)
820 ms
…v29/KFOmCnqEu….woff2
(fonts.gstatic.com)
420 ms
…v29/KFOlCnqEu….woff2
(fonts.gstatic.com)
670 ms
…v19/pxiByp8kv….woff2
(fonts.gstatic.com)
710 ms
660 ms
…v27/memvYaGs1….woff2
(fonts.gstatic.com)
810 ms
…v29/KFOlCnqEu….woff2
(fonts.gstatic.com)
640 ms
…v14/oY1Z8e7Ou….woff2
(fonts.gstatic.com)
710 ms
370 ms
Does not use passive listeners to improve scrolling performance
Consider marking your touch and wheel event listeners as `passive` to improve your page's scroll performance. Learn more.
Source
Minimize main-thread work 13.0 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn moreTBT
Category
Time Spent
Script Evaluation
3,958 ms
Other
3,574 ms
Style & Layout
3,264 ms
Rendering
1,354 ms
Parse HTML & CSS
576 ms
Script Parsing & Compilation
186 ms
Garbage Collection
68 ms
Avoid enormous network payloads Total size was 5,483 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.LCP
WordPressConsider showing excerpts in your post lists (e.g. via the more tag), reducing the number of posts shown on a given page, breaking your long posts into multiple pages, or using a plugin to lazy-load comments.
URL
Transfer Size
434.5 KiB
432.8 KiB
377.1 KiB
294.1 KiB
225.2 KiB
150.3 KiB
143.2 KiB
136.3 KiB
134.4 KiB
118.1 KiB
Serve static assets with an efficient cache policy 76 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.
URL
Cache TTL
Transfer Size
…api/js?libraries=…
(maps.google.com)
30 m
55 KiB
…css/translateelement.css
(translate.googleapis.com)
1 h
4 KiB
…ua/linkid.js
(www.google-analytics.com)
1 h
1 KiB
/analytics.js
(www.google-analytics.com)
2 h
20 KiB
30 d
434 KiB
30 d
433 KiB
30 d
377 KiB
30 d
225 KiB
30 d
143 KiB
30 d
136 KiB
30 d
134 KiB
30 d
118 KiB
30 d
111 KiB
30 d
109 KiB
30 d
108 KiB
30 d
108 KiB
30 d
92 KiB
30 d
80 KiB
30 d
76 KiB
30 d
76 KiB
30 d
75 KiB
30 d
64 KiB
30 d
64 KiB
30 d
59 KiB
30 d
58 KiB
30 d
57 KiB
30 d
56 KiB
30 d
55 KiB
30 d
42 KiB
30 d
41 KiB
30 d
39 KiB
30 d
39 KiB
30 d
36 KiB
30 d
30 KiB
30 d
27 KiB
30 d
26 KiB
30 d
25 KiB
30 d
19 KiB
30 d
18 KiB
30 d
18 KiB
30 d
16 KiB
30 d
14 KiB
30 d
14 KiB
30 d
12 KiB
30 d
12 KiB
30 d
12 KiB
30 d
12 KiB
30 d
11 KiB
30 d
9 KiB
30 d
8 KiB
…lity/lity.min.js
(futo.edu.ng)
30 d
7 KiB
30 d
7 KiB
30 d
5 KiB
30 d
5 KiB
30 d
5 KiB
30 d
4 KiB
30 d
4 KiB
30 d
3 KiB
30 d
3 KiB
30 d
3 KiB
30 d
2 KiB
30 d
2 KiB
30 d
2 KiB
30 d
2 KiB
30 d
2 KiB
30 d
2 KiB
30 d
2 KiB
30 d
1 KiB
30 d
1 KiB
30 d
1 KiB
30 d
1 KiB
30 d
1 KiB
30 d
1 KiB
30 d
0 KiB
…plugin/plugin-api-min.js
(www.researchgate.net)
60 d
2 KiB
…favicon/favicon.ico
(www.researchgate.net)
60 d
2 KiB
Avoid an excessive DOM size 1,989 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn more.TBT
Statistic
Element
Value
Total DOM Elements
1,989
Maximum DOM Depth
div.tp-mask-wrap > div#slide-226-layer-10 > a > i.fa-icon-chevron-right
<i class="fa-icon-chevron-right" style="transition: none 0s ease 0s; text-align: inherit; line-height: 4px; border…">
33
Maximum Child Elements
Selecteer een taalNederlandsAfrikaansAlbaneesAmharischArabischArmeensAzerbeidzj…
<select class="goog-te-combo" aria-label="Widget Language Translate">
109
Reduce JavaScript execution time 3.7 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.TBT
URL
Total CPU Time
Script Evaluation
Script Parse
4,084 ms
1,359 ms
6 ms
2,935 ms
263 ms
20 ms
Unattributable
1,760 ms
10 ms
0 ms
1,036 ms
543 ms
2 ms
889 ms
648 ms
0 ms
581 ms
263 ms
29 ms
182 ms
134 ms
15 ms
/gtag/js?id=UA-111…-1
(www.googletagmanager.com)
117 ms
86 ms
21 ms
108 ms
62 ms
2 ms
101 ms
71 ms
15 ms
78 ms
4 ms
3 ms
…api/js?libraries=…
(maps.google.com)
78 ms
64 ms
7 ms
69 ms
0 ms
0 ms
66 ms
46 ms
7 ms
…ua/linkid.js
(www.google-analytics.com)
50 ms
49 ms
1 ms
Avoid chaining critical requests 93 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn more.FCPLCP
Maximum critical path latency: 22,430 ms
Initial Navigation
- 1,550 ms, 1.04 KiB
- 1,140 ms, 10.30 KiB
- 1,300 ms, 14.89 KiB
- 1,320 ms, 13.67 KiB
- 1,320 ms, 0.72 KiB
- 1,320 ms, 0.24 KiB
- 1,320 ms, 3.49 KiB
- 1,510 ms, 1.72 KiB
- 2,280 ms, 59.45 KiB
- 1,190 ms, 75.18 KiB
- 2,280 ms, 26.44 KiB
- 1,320 ms, 2.39 KiB
- 1,360 ms, 1.01 KiB
- 2,520 ms, 57.02 KiB
- 1,620 ms, 3.03 KiB
- 2,130 ms, 2.45 KiB
/css?family=…
(fonts.googleapis.com)
…v19/pxiEyp8kv….woff2
(fonts.gstatic.com)
- 1,820 ms, 7.79 KiB
…v19/pxiByp8kv….woff2
(fonts.gstatic.com)
- 760 ms, 7.68 KiB
…v19/pxiByp8kv….woff2
(fonts.gstatic.com)
- 820 ms, 7.75 KiB
…v19/pxiByp8kv….woff2
(fonts.gstatic.com)
- 710 ms, 7.93 KiB
- 950 ms, 75.71 KiB
- 5,060 ms, 225.18 KiB
- 370 ms, 7.72 KiB
- 2,510 ms, 2.36 KiB
- 3,110 ms, 11.69 KiB
- 2,250 ms, 432.85 KiB
- 3,110 ms, 5.33 KiB
- 3,560 ms, 4.44 KiB
- 3,640 ms, 18.96 KiB
- 3,640 ms, 13.84 KiB
- 4,600 ms, 134.40 KiB
- 4,040 ms, 1.45 KiB
- 4,210 ms, 25.34 KiB
- 4,600 ms, 27.08 KiB
- 5,150 ms, 109.10 KiB
- 5,000 ms, 91.63 KiB
- 6,050 ms, 434.47 KiB
- 4,980 ms, 29.93 KiB
/css?family=…
(fonts.googleapis.com)
…v29/KFOmCnqEu….woff2
(fonts.gstatic.com)
- 420 ms, 11.39 KiB
…v29/KFOlCnqEu….woff2
(fonts.gstatic.com)
- 670 ms, 10.90 KiB
…v29/KFOlCnqEu….woff2
(fonts.gstatic.com)
- 640 ms, 10.82 KiB
- 1,130 ms, 15.76 KiB
- 5,320 ms, 1.93 KiB
- 5,320 ms, 3.97 KiB
…lity/lity.min.js
(futo.edu.ng)
- 5,340 ms, 6.86 KiB
- 5,760 ms, 108.35 KiB
- 5,820 ms, 63.80 KiB
- 5,650 ms, 5.32 KiB
/css?family=…
(fonts.googleapis.com)
…v27/memvYaGs1….woff2
(fonts.gstatic.com)
- 810 ms, 38.66 KiB
…v14/oY1Z8e7Ou….woff2
(fonts.gstatic.com)
- 710 ms, 11.70 KiB
- 970 ms, 108.35 KiB
- 470 ms, 63.80 KiB
- 1,900 ms, 26.61 KiB
- 660 ms, 75.71 KiB
/css?family=Josefin+Sans
(fonts.googleapis.com)
- 200 ms, 0.44 KiB
- 460 ms, 1.18 KiB
- 1,000 ms, 18.39 KiB
- 250 ms, 0.41 KiB
- 200 ms, 2.38 KiB
- 200 ms, 6.70 KiB
- 360 ms, 11.96 KiB
- 360 ms, 1.51 KiB
- 1,830 ms, 377.13 KiB
- 1,440 ms, 80.22 KiB
- 370 ms, 0.41 KiB
- 1,880 ms, 143.23 KiB
…api/js?libraries=…
(maps.google.com)
- 1,410 ms, 55.09 KiB
- 860 ms, 55.05 KiB
- 420 ms, 2.66 KiB
- 220 ms, 6.25 KiB
- 450 ms, 56.11 KiB
- 360 ms, 1.56 KiB
- 360 ms, 5.16 KiB
- 410 ms, 14.27 KiB
- 740 ms, 12.29 KiB
- 210 ms, 6.46 KiB
- 690 ms, 136.27 KiB
- 360 ms, 2.89 KiB
- 360 ms, 10.80 KiB
- 440 ms, 36.40 KiB
- 360 ms, 1.16 KiB
- 820 ms, 16.34 KiB
- 380 ms, 42.37 KiB
- 410 ms, 1.62 KiB
- 270 ms, 7.12 KiB
- 410 ms, 1.28 KiB
- 270 ms, 0.69 KiB
- 410 ms, 1.11 KiB
- 1,240 ms, 29.70 KiB
- 1,240 ms, 3.96 KiB
- 4,970 ms, 11.94 KiB
Keep request counts low and transfer sizes small 159 requests • 5,483 KiB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.
Resource Type
Requests
Transfer Size
Total
159
5,482.8 KiB
Script
55
1,824.8 KiB
Stylesheet
44
1,782.8 KiB
Font
14
781.8 KiB
Image
37
665.9 KiB
Document
2
298.0 KiB
Other
7
129.5 KiB
Media
0
0.0 KiB
Third-party
76
876.6 KiB
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport. Learn MoreLCP
Element
Notice For Candidates Offered Supplementary Admission in Departments other than…
<div class="gdlr-core-recent-post-widget-title">
Avoid large layout shifts 3 elements found
These DOM elements contribute most to the CLS of the page.CLS
Element
CLS Contribution
Additional Merit Admission List has been Published for the 2021/2022 Academic S…
<div class="elementor-widget-wrap">
0.033
English
<div style="position:absolute;bottom:0px;right:8%;z-index:999999;" id="gtranslate_wrapper">
0.018
Advertisement for 2021/2022 FUTO 2nd Supplementary Admissions Exercise JANUARY …
<div class="elementor-widget-wrap">
0.018
Avoid long main-thread tasks 17 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn moreTBT
URL
Start Time
Duration
37,061 ms
487 ms
26,611 ms
172 ms
27,397 ms
155 ms
2,667 ms
150 ms
/e-202206.js
(stats.wp.com)
36,715 ms
145 ms
17,447 ms
140 ms
31,382 ms
118 ms
36,600 ms
115 ms
36,872 ms
114 ms
19,535 ms
88 ms
36,986 ms
75 ms
Unattributable
2,860 ms
73 ms
31,785 ms
69 ms
27,273 ms
69 ms
31,202 ms
67 ms
19,623 ms
66 ms
/gtag/js?id=UA-111…-1
(www.googletagmanager.com)
26,783 ms
54 ms
Avoid non-composited animations 2 animated elements found
Animations which are not composited can be janky and increase CLS. Learn moreCLS
Element
Name
div.goog-te-spinner-pos > div.goog-te-spinner-animation > svg.goog-te-spinner > circle.goog-te-spinner-path
<circle class="goog-te-spinner-path" fill="none" stroke-width="6" stroke-linecap="round" cx="33" cy="33" r="30">
Unsupported CSS Property: stroke-dashoffset
goog-te-spinner-dash
div.tp-mask-wrap > div#slide-226-layer-10 > a > i.fa-icon-chevron-right
<i class="fa-icon-chevron-right" style="transition: none 0s ease 0s; text-align: inherit; line-height: 4px; border…">
Unsupported CSS Property: font-size
font-size
Unsupported CSS Property: visibility
visibility
Passed audits (16)
Properly size images
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.
WordPressUpload images directly through the media library to ensure that the required image sizes are available, and then insert them from the media library or use the image widget to ensure the optimal image sizes are used (including those for the responsive breakpoints). Avoid using `Full Size` images unless the dimensions are adequate for their usage. Learn More.
Defer offscreen images
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn more.
WordPressInstall a lazy-load WordPress plugin that provides the ability to defer any offscreen images, or switch to a theme that provides that functionality. Also consider using the AMP plugin.
Minify JavaScript Potential savings of 54 KiB
Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.FCPLCP
WordPressA number of WordPress plugins can speed up your site by concatenating, minifying, and compressing your scripts. You may also want to use a build process to do this minification up front if possible.
URL
Transfer Size
Potential Savings
55.1 KiB
23.9 KiB
80.2 KiB
18.6 KiB
56.1 KiB
9.1 KiB
inline: 
				var em_version = '7.3.3';
				var e...
5.7 KiB
2.3 KiB
Preconnect to required origins
Consider adding `preconnect` or `dns-prefetch` resource hints to establish early connections to important third-party origins. Learn more.FCPLCP
Avoid multiple page redirects
Redirects introduce additional delays before the page can be loaded. Learn more.FCPLCP
Preload key requests
Consider using `<link rel=preload>` to prioritize fetching resources that are currently requested later in page load. Learn more.FCPLCP
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Learn moreLCP
WordPressConsider uploading your GIF to a service which will make it available to embed as an HTML5 video.
Remove duplicate modules in JavaScript bundles
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity. TBT
Preload Largest Contentful Paint image
Preload the image used by the LCP element in order to improve your LCP time. Learn more.LCP
User Timing marks and measures
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more.
Minimize third-party usage Third-party code blocked the main thread for 120 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn more.TBT
Third-Party
Transfer Size
Main-Thread Blocking Time
340 KiB
94 ms
30 KiB
94 ms
48 KiB
0 ms
47 KiB
0 ms
44 KiB
0 ms
31 KiB
0 ms
Other resources
141 KiB
0 ms
108 KiB
30 ms
78 KiB
30 ms
27 KiB
0 ms
175 KiB
0 ms
…7a/util.js
(maps.google.com)
91 KiB
0 ms
…api/js?libraries=…
(maps.google.com)
55 KiB
0 ms
…7a/common.js
(maps.google.com)
29 KiB
0 ms
119 KiB
0 ms
…v27/memvYaGs1….woff2
(fonts.gstatic.com)
39 KiB
0 ms
…v14/oY1Z8e7Ou….woff2
(fonts.gstatic.com)
12 KiB
0 ms
…v29/KFOmCnqEu….woff2
(fonts.gstatic.com)
11 KiB
0 ms
…v29/KFOlCnqEu….woff2
(fonts.gstatic.com)
11 KiB
0 ms
…v29/KFOlCnqEu….woff2
(fonts.gstatic.com)
11 KiB
0 ms
Other resources
36 KiB
0 ms
36 KiB
0 ms
/gtag/js?id=UA-111…-1
(www.googletagmanager.com)
36 KiB
0 ms
21 KiB
0 ms
/analytics.js
(www.google-analytics.com)
20 KiB
0 ms
4 KiB
0 ms
3 KiB
0 ms
Lazy load third-party resources with facades
Some third-party embeds can be lazy loaded. Consider replacing them with a facade until they are required. Learn more.TBT
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint. Learn more.
Avoids document.write()
For users on slow connections, external scripts dynamically injected via `document.write()` can delay page load by tens of seconds. Learn more.
Image elements have explicit width and height
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn moreCLS
Has a <meta name="viewport"> tag with width or initial-scale
A `<meta name="viewport">` not only optimizes your app for mobile screen sizes, but also prevents a 300 millisecond delay to user input. Learn more.TBT
These checks highlight opportunities to improve the accessibility of your web app. Only a subset of accessibility issues can be automatically detected so manual testing is also encouraged.
ContrastThese are opportunities to improve the legibility of your content.
Background and foreground colors do not have a sufficient contrast ratio.
Low-contrast text is difficult or impossible for many users to read. Learn more.
Failing Elements
ORACLE/IBM Academy
<span class="ekit_page_list_title_title">
Enroll Today
<span class="ekit_menu_subtitle">
Best in CISCO Academy
<span class="ekit_page_list_title_title">
First in Professional Enrollment & Best Training
<span class="ekit_menu_subtitle">
Postgraduate Studies
<span class="ekit_page_list_title_title">
Enroll Today
<span class="ekit_menu_subtitle">
FUTO News
<span class="ekit_page_list_title_title">
Read All News
<span class="ekit_menu_subtitle">
Upcoming Events
<span class="ekit_page_list_title_title">
Executive Short Courses
<span class="ekit_page_list_title_title">
Advanced Diploma Certificates
<span class="ekit_menu_subtitle">
© 2021. All rights reserved. Federal University of Technology, Owerri
<div class="kingster-copyright-left kingster-item-pdlr">
Powered by: Pioneer Ind. Ltd.
<div class="kingster-copyright-right kingster-item-pdlr">
Names and labelsThese 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.
Additional items to manually check (10) These items address areas which an automated testing tool cannot cover. Learn more in our guide on conducting an accessibility review.
The page has a logical tab order
Tabbing through the page follows the visual layout. Users cannot focus elements that are offscreen. Learn more.
Interactive controls are keyboard focusable
Custom interactive controls are keyboard focusable and display a focus indicator. Learn more.
Interactive elements indicate their purpose and state
Interactive elements, such as links and buttons, should indicate their state and be distinguishable from non-interactive elements. Learn more.
The user's focus is directed to new content added to the page
If new content, such as a dialog, is added to the page, the user's focus is directed to it. Learn more.
User focus is not accidentally trapped in a region
A user can tab into and out of any control or region without accidentally trapping their focus. Learn more.
Custom controls have associated labels
Custom interactive controls have associated labels, provided by aria-label or aria-labelledby. Learn more.
Custom controls have ARIA roles
Custom interactive controls have appropriate ARIA roles. Learn more.
Visual order on the page follows DOM order
DOM order matches the visual order, improving navigation for assistive technology. Learn more.
Offscreen content is hidden from assistive technology
Offscreen content is hidden with display: none or aria-hidden=true. Learn more.
HTML5 landmark elements are used to improve navigation
Landmark elements (<main>, <nav>, etc.) are used to improve the keyboard navigation of the page for assistive technology. Learn more.
Passed audits (12)
[aria-hidden="true"] is not present on the document <body>
Assistive technologies, like screen readers, work inconsistently when `aria-hidden="true"` is set on the document `<body>`. Learn more.
[aria-hidden="true"] elements do not contain focusable descendents
Focusable descendents within an `[aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn more.
The page contains a heading, skip link, or landmark region
Adding ways to bypass repetitive content lets keyboard users navigate the page more efficiently. Learn more.
Document has a <title> element
The title gives screen reader users an overview of the page, and search engine users rely on it heavily to determine if a page is relevant to their search. Learn more.
[id] attributes on active, focusable elements are unique
All focusable elements must have a unique `id` to ensure that they're visible to assistive technologies. Learn more.
Heading elements appear in a sequentially-descending order
Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more.
<html> element has a [lang] attribute
If a page doesn't specify a lang attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more.
<html> element has a valid value for its [lang] attribute
Specifying a valid BCP 47 language helps screen readers announce text properly. Learn more.
Image elements have [alt] attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more.
Lists contain only <li> elements and script supporting elements (<script> and <template>).
Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more.
List items (<li>) are contained within <ul> or <ol> parent elements
Screen readers require list items (`<li>`) to be contained within a parent `<ul>` or `<ol>` to be announced properly. Learn more.
[user-scalable="no"] is not used in the <meta name="viewport"> element and the [maximum-scale] attribute is not less than 5.
Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more.
Not applicable (30)
[accesskey] values are unique
Access keys let users quickly focus a part of the page. For proper navigation, each access key must be unique. Learn more.
[aria-*] attributes match their roles
Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn more.
button, link, and menuitem elements have accessible names
When an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more.
ARIA input fields have accessible names
When an input field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more.
ARIA meter elements have accessible names
When an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more.
ARIA progressbar elements have accessible names
When a `progressbar` element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more.
[role]s have all required [aria-*] attributes
Some ARIA roles have required attributes that describe the state of the element to screen readers. Learn more.
Elements with an ARIA [role] that require children to contain a specific [role] have all required children.
Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more.
[role]s are contained by their required parent element
Some ARIA child roles must be contained by specific parent roles to properly perform their intended accessibility functions. Learn more.
[role] values are valid
ARIA roles must have valid values in order to perform their intended accessibility functions. Learn more.
ARIA toggle fields have accessible names
When a toggle field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more.
ARIA tooltip elements have accessible names
When an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more.
ARIA treeitem elements have accessible names
When an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more.
[aria-*] attributes have valid values
Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more.
[aria-*] attributes are valid and not misspelled
Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid names. Learn more.
Buttons have an accessible name
When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn more.
<dl>'s contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.
When definition lists are not properly marked up, screen readers may produce confusing or inaccurate output. Learn more.
Definition list items are wrapped in <dl> elements
Definition list items (`<dt>` and `<dd>`) must be wrapped in a parent `<dl>` element to ensure that screen readers can properly announce them. Learn more.
ARIA IDs are unique
The value of an ARIA ID must be unique to prevent other instances from being overlooked by assistive technologies. Learn more.
No form fields have multiple labels
Form fields with multiple labels can be confusingly announced by assistive technologies like screen readers which use either the first, the last, or all of the labels. Learn more.
<frame> or <iframe> elements have a title
Screen reader users rely on frame titles to describe the contents of frames. Learn more.
<input type="image"> elements have [alt] text
When an image is being used as an `<input>` button, providing alternative text can help screen reader users understand the purpose of the button. Learn more.
Form elements have associated labels
Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more.
The document does not use <meta http-equiv="refresh">
Users do not expect a page to refresh automatically, and doing so will move focus back to the top of the page. This may create a frustrating or confusing experience. Learn more.
<object> elements have [alt] text
Screen readers cannot translate non-text content. Adding alt text to `<object>` elements helps screen readers convey meaning to users. Learn more.
No element has a [tabindex] value greater than 0
A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more.
Cells in a <table> element that use the [headers] attribute refer to table cells within the same table.
Screen readers have features to make navigating tables easier. Ensuring `<td>` cells using the `[headers]` attribute only refer to other cells in the same table may improve the experience for screen reader users. Learn more.
<th> elements and elements with [role="columnheader"/"rowheader"] have data cells they describe.
Screen readers have features to make navigating tables easier. Ensuring table headers always refer to some set of cells may improve the experience for screen reader users. Learn more.
[lang] attributes have a valid value
Specifying a valid BCP 47 language on elements helps ensure that text is pronounced correctly by a screen reader. Learn more.
<video> elements contain a <track> element with [kind="captions"]
When a video provides a caption it is easier for deaf and hearing impaired users to access its information. Learn more.
Trust and Safety
Links to cross-origin destinations are unsafe
Add `rel="noopener"` or `rel="noreferrer"` to any external links to improve performance and prevent security vulnerabilities. Learn more.
Failing Anchors
div.kingster-top-bar-container-inner > div.kingster-top-bar-right > div.kingster-top-bar-right-social > a.kingster-top-bar-social-icon
<a href="https://facebook.com/F.U.T.O.Nigeria" target="_blank" class="kingster-top-bar-social-icon">
div.kingster-top-bar-container-inner > div.kingster-top-bar-right > div.kingster-top-bar-right-social > a.kingster-top-bar-social-icon
<a href="https://twitter.com/Futoweb" target="_blank" class="kingster-top-bar-social-icon">
div.kingster-top-bar-container-inner > div.kingster-top-bar-right > div.kingster-top-bar-right-social > a.kingster-top-bar-social-icon
<a href="https://youtube.com/channel/UCuVgpEWaFAutM2kFoSuGg2Q" target="_blank" class="kingster-top-bar-social-icon">
Apply Now
<a class="kingster-top-bar-right-button" href="https://portal.futo.edu.ng/ApplicationsInfo.aspx" target="_blank">
div.elementor-widget-container > ul.elementor-icon-list-items > li.elementor-icon-list-item > a
<a href="https://futospace.futo.edu.ng/" target="_blank">
div.elementor-widget-container > ul.elementor-icon-list-items > li.elementor-icon-list-item > a
<a href="https://portal.futo.edu.ng/Modules/IWOGDS/Landing.aspx" target="_blank">
div.elementor-widget-container > ul.elementor-icon-list-items > li.elementor-icon-list-item > a
<a href="https://tps.futo.edu.ng/" target="_blank">
div.kingster-copyright-container > div.kingster-copyright-right > div.gdlr-core-social-network-item > a.gdlr-core-social-network-icon
<a href="https://facebook.com/F.U.T.O.Nigeria" target="_blank" class="gdlr-core-social-network-icon">
div.kingster-copyright-container > div.kingster-copyright-right > div.gdlr-core-social-network-item > a.gdlr-core-social-network-icon
<a href="https://twitter.com/Futoweb" target="_blank" class="gdlr-core-social-network-icon">
div.kingster-copyright-container > div.kingster-copyright-right > div.gdlr-core-social-network-item > a.gdlr-core-social-network-icon
<a href="https://youtube.com/channel/UCuVgpEWaFAutM2kFoSuGg2Q" target="_blank" class="gdlr-core-social-network-icon">
Translate
<a class="goog-logo-link" href="https://translate.google.com" target="_blank">
Ensure CSP is effective against XSS attacks
A strong Content Security Policy (CSP) significantly reduces the risk of cross-site scripting (XSS) attacks. Learn more
Description
Directive
Severity
No CSP found in enforcement mode
High
User Experience
Serves images with low resolution
Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn more.
URL
Displayed size
Actual size
Expected size
220 x 238
220 x 238
440 x 476
General
Detected JavaScript libraries
All front-end JavaScript libraries detected on the page. Learn more.
Name
Version
Google Maps
3.47.7a
jQuery
3.6.0
jQuery UI
1.13.0
Underscore
1.13.1
Isotope
WordPress
5.9
core-js
core-js-global@3.19.1
Issues were logged in the Issues panel in Chrome Devtools
Issues logged to the `Issues` panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.
Issue type
SameSite cookie
/v1/supportedLanguages?client=…
(translate-pa.googleapis.com)
…favicon/favicon.ico
(www.researchgate.net)
Passed audits (13)
Uses HTTPS
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more.
Avoids requesting the geolocation permission on page load
Users are mistrustful of or confused by sites that request their location without context. Consider tying the request to a user action instead. Learn more.
Avoids requesting the notification permission on page load
Users are mistrustful of or confused by sites that request to send notifications without context. Consider tying the request to user gestures instead. Learn more.
Avoids front-end JavaScript libraries with known security vulnerabilities
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers. Learn more.
Allows users to paste into password fields
Preventing password pasting undermines good security policy. Learn more.
Displays images with correct aspect ratio
Image display dimensions should match natural aspect ratio. Learn more.
Page has the HTML doctype
Specifying a doctype prevents the browser from switching to quirks-mode. Learn more.
Properly defines charset
A character encoding declaration is required. It can be done with a `<meta>` tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header. Learn more.
Avoids unload event listeners
The `unload` event does not fire reliably and listening for it can prevent browser optimizations like the Back-Forward Cache. Consider using the `pagehide` or `visibilitychange` events instead. Learn more
Avoids Application Cache
Application Cache is deprecated. Learn more.
Avoids deprecated APIs
Deprecated APIs will eventually be removed from the browser. Learn more.
No browser errors logged to the console
Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more
Page has valid source maps
Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more.
Not applicable (1)
Fonts with font-display: optional are preloaded
Preload `optional` fonts so first-time visitors may use them. Learn more
These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more.
Crawling and IndexingTo appear in search results, crawlers need access to your app.
robots.txt is not valid
Lighthouse was unable to download a robots.txt file
If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more.
Mobile FriendlyMake sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. Learn more.
Tap targets are not sized appropriately 40% appropriately sized tap targets
Interactive elements like buttons and links should be large enough (48x48px), and have enough space around them, to be easy enough to tap without overlapping onto other elements. Learn more.
Tap Target
Size
Overlapping Target
JANUARY 31, 2022
<a href="https://futo.edu.ng/2022/01/31/">
125x18
Advertisement for 2021/2022 FUTO 2nd Supplementary Admissions Exercise
<a href="https://futo.edu.ng/auto-draft/">
JANUARY 21, 2022
<a href="https://futo.edu.ng/2022/01/21/">
125x18
Pre-Degree Programme Admission List Batch One (1)
<a href="https://futo.edu.ng/pre-degree-programme-admission-list-batch-one-1/">
JANUARY 20, 2022
<a href="https://futo.edu.ng/2022/01/20/">
129x18
Notice For Candidates Offered Supplementary Admission in Departments other than…
<a href="https://futo.edu.ng/notice-for-candidates-offered-supplementary-admission-…">
JANUARY 20, 2022
<a href="https://futo.edu.ng/2022/01/20/">
129x18
Additional Merit List
<a href="https://futo.edu.ng/additional-merit-list/">
JANUARY 19, 2022
<a href="https://futo.edu.ng/2022/01/19/">
126x18
List of Pre-Degree Candidates Admitted into Regular Programme
<a href="https://futo.edu.ng/list-of-pre-degree-candidates-admitted-into-regular-pr…">
JANUARY 13, 2022
<a href="https://futo.edu.ng/2022/01/13/">
125x18
Batch Nine (9) of JUPEB Programme Admission List
<a href="https://futo.edu.ng/batch-nine-9-of-jupeb-programme-admission-list/">
FAQ
<a href="https://futo.edu.ng/frequently-asked-questions/">
25x18
Careers
<a href="https://futo.edu.ng/careers/">
div.kingster-copyright-container > div.kingster-copyright-right > div.gdlr-core-social-network-item > a.gdlr-core-social-network-icon
<a href="https://youtube.com/channel/UCuVgpEWaFAutM2kFoSuGg2Q" target="_blank" class="gdlr-core-social-network-icon">
21x26
English
<a href="#" onclick="return false;">
TETFund
<a href="https://tetfund.gov.ng/">
52x18
World Bank
<a href="https://www.worldbank.org/">
World Bank
<a href="https://www.worldbank.org/">
73x18
ResearchGate
<a href="https://www.researchgate.net/institution/Federal_University_of_Technology_…">
ResearchGate
<a href="https://www.researchgate.net/institution/Federal_University_of_Technology_…">
92x18
Federal Ministry of Education
<a href="https://education.gov.ng/">
Federal Ministry of Education
<a href="https://education.gov.ng/">
185x18
Africa Union Network of Science
<a href="https://austrc.org/network.html">
Africa Union Network of Science
<a href="https://austrc.org/network.html">
204x18
National Universities Commission
<a href="https://nuc.edu.ng/">
Careers
<a href="https://futo.edu.ng/careers/">
51x18
Staff Email
<a href="https://mail.office365.com/">
Staff Email
<a href="https://mail.office365.com/">
68x18
Contact Us
<a href="https://futo.edu.ng/contact-us/">
Contact Us
<a href="https://futo.edu.ng/contact-us/">
71x18
FUTO Portal
<a href="https://portal.futo.edu.ng">
FUTO Portal
<a href="https://portal.futo.edu.ng">
73x18
Give to FUTO
<a href="https://futo.edu.ng/linkages-and-advancement/">
Give to FUTO
<a href="https://futo.edu.ng/linkages-and-advancement/">
81x18
Achievements
<a href="https://futo.edu.ng/achievements-of-the-7th-substantive-vice-chancellor/">
Achievements
<a href="https://futo.edu.ng/achievements-of-the-7th-substantive-vice-chancellor/">
92x18
Join a Local Chapter
<a href="https://futo.edu.ng/alumni/alumni-chapters/">
Additional items to manually check (1) Run these additional validators on your site to check additional SEO best practices.
Structured data is valid
Run the Structured Data Testing Tool and the Structured Data Linter to validate structured data. Learn more.
Passed audits (12)
Has a <meta name="viewport"> tag with width or initial-scale
A `<meta name="viewport">` not only optimizes your app for mobile screen sizes, but also prevents a 300 millisecond delay to user input. Learn more.TBT
Document has a <title> element
The title gives screen reader users an overview of the page, and search engine users rely on it heavily to determine if a page is relevant to their search. Learn more.
Document has a meta description
Meta descriptions may be included in search results to concisely summarize page content. Learn more.
Page has successful HTTP status code
Pages with unsuccessful HTTP status codes may not be indexed properly. Learn more.
Links are crawlable
Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn More
Page isn’t blocked from indexing
Search engines are unable to include your pages in search results if they don't have permission to crawl them. Learn more.
Image elements have [alt] attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more.
Document has a valid hreflang
hreflang links tell search engines what version of a page they should list in search results for a given language or region. Learn more.
Document has a valid rel=canonical
Canonical links suggest which URL to show in search results. Learn more.
Document uses legible font sizes 97.94% legible text
Font sizes less than 12px are too small to be legible and require mobile visitors to “pinch to zoom” in order to read. Strive to have >60% of page text ≥12px. Learn more.
Source
Selector
% of Page Text
Font Size
<div class="tp-caption tp-resizeme" id="slide-226-layer-4" data-x="['center','center','center','center']" data-hoffset="['41','47','47','47']" data-y="['top','middle','middle','middle']" data-voffset="['122','-24','-24','-24']" data-width="none" data-height="none" data-whitespace="nowrap" data-type="text" data-responsive_offset="on" data-frames="[{"delay":1100,"speed":300,"frame":"0","from":"opacity:0;","to":"o:1;","ease":"Power3.easeInOut"},{"delay":"wait","speed":300,"frame":"999","to":"opacity:0;","ease":"Power3.easeInOut"}]" data-textalign="['inherit','inherit','inherit','inherit']" data-paddingtop="[0,0,0,0]" data-paddingright="[0,0,0,0]" data-paddingbottom="[0,0,0,0]" data-paddingleft="[0,0,0,0]" style="z-index: 6; white-space: nowrap; font-size: 8px; line-height: 12px; font-weight: 600; color: rgb(255, 255, 255); letter-spacing: 0px; font-family: "Open Sans"; cursor: pointer; visibility: inherit; transition: none 0s ease 0s; text-align: inherit; border-width: 0px; margin: 0px; padding: 0px; min-height: 0px; min-width: 0px; max-height: none; max-width: none; opacity: 1; transform: matrix3d(1, 0, 0, 0, 0, 1, 0, 0, 0, 0, 1, 0, 0, 0, 0, 1); transform-origin: 50% 50% 0px;">
1.07%
8px
.ekit-wid-con .ekit_menu_label
0.60%
10px
<div class="tp-caption tp-resizeme" id="slide-226-layer-5" data-x="['center','center','center','center']" data-hoffset="['42','43','43','43']" data-y="['top','top','top','top']" data-voffset="['53','102','102','102']" data-fontsize="['33','38','38','38']" data-fontweight="['700','600','600','600']" data-width="none" data-height="none" data-whitespace="nowrap" data-type="text" data-responsive_offset="on" data-frames="[{"delay":100,"speed":300,"frame":"0","to":"o:1;","ease":"Power3.easeInOut"},{"delay":"wait","speed":300,"frame":"999","ease":"Power3.easeInOut"}]" data-textalign="['inherit','inherit','inherit','inherit']" data-paddingtop="[0,0,0,0]" data-paddingright="[0,0,0,0]" data-paddingbottom="[0,0,0,0]" data-paddingleft="[0,0,0,0]" style="z-index: 7; white-space: nowrap; font-size: 10px; line-height: 12px; font-weight: 600; color: rgb(255, 255, 255); letter-spacing: 0px; font-family: "Open Sans"; text-decoration: underline; cursor: pointer; visibility: inherit; transition: none 0s ease 0s; text-align: inherit; border-width: 0px; margin: 0px; padding: 0px; min-height: 0px; min-width: 0px; max-height: none; max-width: none; opacity: 1; transform: matrix3d(1, 0, 0, 0, 0, 1, 0, 0, 0, 0, 1, 0, 0, 0, 0, 1); transform-origin: 50% 50% 0px;">
0.26%
10px
<a href="https://futo.edu.ng/pre-degree-programme-admission-list-batch-one-1/" style="transition: none 0s ease 0s; text-align: inherit; line-height: 2px; border-width: 0px; margin: 0px; padding: 0px; letter-spacing: 0px; font-weight: 500; font-size: 8px;">
0.13%
8px
<i class="fa-icon-chevron-right" style="transition: none 0s ease 0s; text-align: inherit; line-height: 4px; border-width: 0px; margin: 0px; padding: 0px; letter-spacing: 0px; font-weight: 400; font-size: 4px;">
0.01%
4px
Legible text
97.94%
≥ 12px
Document avoids plugins
Search engines can't index plugin content, and many devices restrict plugins or don't support them. Learn more.
These checks validate the aspects of a Progressive Web App. Learn more.
Installable
Web app manifest or service worker do not meet the installability requirements 1 reason
Service worker is the technology that enables your app to use many Progressive Web App features, such as offline, add to homescreen, and push notifications. With proper service worker and manifest implementations, browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement. Learn more.
Failure reason
No manifest was fetched
PWA Optimized
Does not register a service worker that controls page and start_url
The service worker is the technology that enables your app to use many Progressive Web App features, such as offline, add to homescreen, and push notifications. Learn more.
Redirects HTTP traffic to HTTPS
If you've already set up HTTPS, make sure that you redirect all HTTP traffic to HTTPS in order to enable secure web features for all your users. Learn more.
Is not configured for a custom splash screen
Failures: No manifest was fetched.
A themed splash screen ensures a high-quality experience when users launch your app from their homescreens. Learn more.
Does not set a theme color for the address bar.
Failures: No manifest was fetched, No `<meta name="theme-color">` tag found.
The browser address bar can be themed to match your site. Learn more.
Content is sized correctly for the viewport
If the width of your app's content doesn't match the width of the viewport, your app might not be optimized for mobile screens. Learn more.
Has a <meta name="viewport"> tag with width or initial-scale
A `<meta name="viewport">` not only optimizes your app for mobile screen sizes, but also prevents a 300 millisecond delay to user input. Learn more.TBT
Provides a valid apple-touch-icon
For ideal appearance on iOS when users add a progressive web app to the home screen, define an `apple-touch-icon`. It must point to a non-transparent 192px (or 180px) square PNG. Learn More.
Manifest doesn't have a maskable icon
No manifest was fetched
A maskable icon ensures that the image fills the entire shape without being letterboxed when installing the app on a device. Learn more.
Additional items to manually check (3) These checks are required by the baseline PWA Checklist but are not automatically checked by Lighthouse. They do not affect your score but it's important that you verify them manually.
Site works cross-browser
To reach the most number of users, sites should work across every major browser. Learn more.
Page transitions don't feel like they block on the network
Transitions should feel snappy as you tap around, even on a slow network. This experience is key to a user's perception of performance. Learn more.
Each page has a URL
Ensure individual pages are deep linkable via URL and that URLs are unique for the purpose of shareability on social media. Learn more.