https://uam.edu.ng/
36
Performance
72
Accessibility
60
Best Practices
95
SEO
Progressive Web App
0–49 50–89 90–100
Metrics
First Contentful Paint
8.0 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.
Speed Index
27.1 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
Largest Contentful Paint
12.0 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more
Time to Interactive
12.7 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Total Blocking Time
60 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.347
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
Serve images in next-gen formats
9.09 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
1,850.4 KiB
1,707.3 KiB
…img/slide-3.jpg
(uam.edu.ng)
72.7 KiB
31.4 KiB
…img/slide-1.jpg
(uam.edu.ng)
57.2 KiB
27.1 KiB
…img/slide-2.jpg
(uam.edu.ng)
43.4 KiB
18.4 KiB
12.9 KiB
8.2 KiB
Enable text compression
8.59 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
470.1 KiB
425.9 KiB
124.0 KiB
105.9 KiB
111.7 KiB
95.1 KiB
94.6 KiB
61.6 KiB
60.1 KiB
48.3 KiB
42.5 KiB
36.1 KiB
34.5 KiB
28.0 KiB
36.8 KiB
24.9 KiB
28.4 KiB
20.9 KiB
23.3 KiB
18.7 KiB
19.2 KiB
13.7 KiB
15.2 KiB
11.9 KiB
16.1 KiB
11.4 KiB
14.1 KiB
10.2 KiB
14.6 KiB
8.0 KiB
11.2 KiB
7.6 KiB
11.7 KiB
7.4 KiB
8.6 KiB
6.7 KiB
9.8 KiB
5.9 KiB
7.0 KiB
4.9 KiB
7.0 KiB
4.0 KiB
5.5 KiB
4.0 KiB
5.8 KiB
3.8 KiB
5.8 KiB
3.8 KiB
5.3 KiB
3.7 KiB
4.6 KiB
3.6 KiB
4.8 KiB
2.6 KiB
2.9 KiB
1.8 KiB
2.8 KiB
1.6 KiB
Reduce unused CSS
7.19 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
470.4 KiB
469.3 KiB
124.3 KiB
116.0 KiB
112.0 KiB
97.9 KiB
34.8 KiB
34.1 KiB
15.4 KiB
15.4 KiB
Eliminate render-blocking resources
6.38 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
…css/font-awesome.min.css
(maxcdn.bootstrapcdn.com)
7.0 KiB
1,470 ms
1.9 KiB
660 ms
/css?family=…
(fonts.googleapis.com)
1.7 KiB
1,310 ms
124.3 KiB
4,710 ms
8.9 KiB
1,260 ms
1.7 KiB
960 ms
15.4 KiB
1,560 ms
4.9 KiB
1,110 ms
34.8 KiB
2,610 ms
112.0 KiB
4,410 ms
5.7 KiB
960 ms
470.4 KiB
5,610 ms
94.9 KiB
3,360 ms
10.1 KiB
1,260 ms
23.6 KiB
1,710 ms
6.1 KiB
1,110 ms
6.1 KiB
1,110 ms
Use HTTP/2
4.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
…img/slide-2.jpg
(uam.edu.ng)
http/1.1
…img/slide-1.jpg
(uam.edu.ng)
http/1.1
…img/slide-3.jpg
(uam.edu.ng)
http/1.1
http/1.1
…img/vc.jpg
(uam.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
…img/vc@2x.jpg
(uam.edu.ng)
http/1.1
Reduce initial server response time
4.29 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,390 ms
Defer offscreen images
1.95 s
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.
URL
Resource Size
Potential Savings
1,850.4 KiB
1,850.4 KiB
…img/vc.jpg
(uam.edu.ng)
15.6 KiB
15.6 KiB
7.7 KiB
7.7 KiB
Reduce unused JavaScript
1.37 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
94.9 KiB
41.8 KiB
42.8 KiB
41.2 KiB
…7a/util.js
(maps.googleapis.com)
90.6 KiB
39.4 KiB
37.1 KiB
33.8 KiB
51.4 KiB
27.8 KiB
28.7 KiB
23.6 KiB
…7a/common.js
(maps.googleapis.com)
28.2 KiB
22.8 KiB
23.6 KiB
22.1 KiB
Preconnect to required origins
0.3 s
Consider adding `preconnect` or `dns-prefetch` resource hints to establish early connections to important third-party origins. Learn more.FCPLCP
URL
Potential Savings
300 ms
300 ms
Minify CSS
0.15 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
124.3 KiB
20.5 KiB
112.0 KiB
20.5 KiB
34.8 KiB
5.1 KiB
15.4 KiB
2.4 KiB
8.9 KiB
2.1 KiB
Minify JavaScript
0.15 s
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
23.6 KiB
14.3 KiB
14.4 KiB
3.6 KiB
7.2 KiB
2.8 KiB
DiagnosticsMore information about the performance of your application. These numbers don't directly affect the Performance score.
Serve static assets with an efficient cache policy 42 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.
URL
Cache TTL
Transfer Size
None
1,851 KiB
None
470 KiB
None
124 KiB
None
112 KiB
None
95 KiB
…img/slide-3.jpg
(uam.edu.ng)
None
73 KiB
None
65 KiB
…img/slide-1.jpg
(uam.edu.ng)
None
57 KiB
…img/slide-2.jpg
(uam.edu.ng)
None
44 KiB
None
43 KiB
None
37 KiB
None
35 KiB
None
29 KiB
None
24 KiB
None
20 KiB
None
16 KiB
None
15 KiB
None
15 KiB
None
14 KiB
None
13 KiB
None
12 KiB
None
11 KiB
None
10 KiB
None
9 KiB
None
8 KiB
None
7 KiB
None
7 KiB
None
6 KiB
None
6 KiB
None
6 KiB
None
6 KiB
None
5 KiB
None
5 KiB
None
3 KiB
None
3 KiB
None
2 KiB
None
2 KiB
None
2 KiB
None
2 KiB
None
1 KiB
30 m
51 KiB
/js
(static.getclicky.com)
7 d
6 KiB
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
…v23/JTUSjIg1_….woff2
(fonts.gstatic.com)
1,090 ms
660 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
Image elements do not have explicit width and height
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn moreCLS
URL
Failing Elements
…img/slide-2.jpg
(uam.edu.ng)
div.slide > div.col-md-8 > div.image-carousel-slide > img
<img src="assets/img/slide-2.jpg" alt="">
…img/slide-1.jpg
(uam.edu.ng)
div.slide > div.col-md-8 > div.image-carousel-slide > img
<img src="assets/img/slide-1.jpg" alt="">
…img/slide-3.jpg
(uam.edu.ng)
div.slide > div.col-md-8 > div.image-carousel-slide > img
<img src="assets/img/slide-3.jpg" alt="">
div.navbar-header > div#brand > a.logo > img
<img src="https://uam.edu.ng/wp-content/uploads/2019/06/fuam-logo.png" alt="">
Avoid enormous network payloads Total size was 3,560 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
1,850.7 KiB
470.4 KiB
124.3 KiB
112.0 KiB
94.9 KiB
…7a/util.js
(maps.googleapis.com)
90.6 KiB
…img/slide-3.jpg
(uam.edu.ng)
73.0 KiB
65.3 KiB
60.4 KiB
…img/slide-1.jpg
(uam.edu.ng)
57.5 KiB
Minimize main-thread work 2.3 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
Other
908 ms
Script Evaluation
694 ms
Style & Layout
328 ms
Parse HTML & CSS
176 ms
Rendering
139 ms
Script Parsing & Compilation
37 ms
Garbage Collection
11 ms
Avoid chaining critical requests 35 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: 14,090 ms
Initial Navigation
…css/font-awesome.min.css
(maxcdn.bootstrapcdn.com)
- 1,190 ms, 6.99 KiB
- 620 ms, 1.92 KiB
/css?family=…
(fonts.googleapis.com)
…v23/JTUSjIg1_….woff2
(fonts.gstatic.com)
- 1,090 ms, 30.83 KiB
- 3,160 ms, 124.30 KiB
- 2,030 ms, 8.91 KiB
- 1,890 ms, 1.70 KiB
- 2,190 ms, 15.43 KiB
- 1,890 ms, 4.88 KiB
- 660 ms, 65.34 KiB
- 1,510 ms, 111.97 KiB
- 2,900 ms, 5.70 KiB
- 4,180 ms, 470.36 KiB
- 3,400 ms, 94.89 KiB
- 2,390 ms, 10.11 KiB
- 2,520 ms, 23.56 KiB
- 2,840 ms, 6.07 KiB
- 2,980 ms, 6.06 KiB
- 360 ms, 2.18 KiB
- 320 ms, 14.39 KiB
- 1,340 ms, 51.35 KiB
- 330 ms, 28.72 KiB
- 320 ms, 3.07 KiB
- 320 ms, 7.32 KiB
- 320 ms, 1.47 KiB
- 340 ms, 37.09 KiB
- 1,150 ms, 42.77 KiB
- 290 ms, 5.11 KiB
- 290 ms, 5.63 KiB
- 300 ms, 16.42 KiB
- 280 ms, 11.49 KiB
- 290 ms, 14.85 KiB
- 300 ms, 3.22 KiB
- 300 ms, 7.24 KiB
- 330 ms, 1.64 KiB
- 580 ms, 19.53 KiB
Keep request counts low and transfer sizes small 60 requests • 3,560 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
60
3,559.7 KiB
Image
9
2,061.6 KiB
Stylesheet
13
790.8 KiB
Script
26
548.3 KiB
Font
2
96.2 KiB
Document
1
60.4 KiB
Other
9
2.5 KiB
Media
0
0.0 KiB
Third-party
11
215.3 KiB
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport. Learn MoreLCP
Element
Welcome to University of Agriculture, Makurdi, Website
<h1>
Avoid large layout shifts 5 elements found
These DOM elements contribute most to the CLS of the page.CLS
Element
CLS Contribution
Important News!! 2021/2022 POST UTME/DIRECT ENTRY SCREENING EXERCISE ADMISSION …
<div class="wpb_column vc_col-sm-12">
0.237
Admission Status Fees Portal Webmail
<ul data-breakpoint="800" id="menu-top-menu" class="secondary-navigation list-unstyled pull-right">
0.041
header#top > div.container > div.navbar-header > div#brand
<div class="navbar-brand nav" id="brand">
0.023
Well Equiped with great selection of Books and titles Our library provides a w…
<div class="col-md-4 col-sm-4">
0.016
Well Equiped with great selection of Books and titles
<h1>
0.015
Avoid long main-thread tasks 7 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
4,013 ms
340 ms
Unattributable
1,480 ms
99 ms
9,765 ms
83 ms
10,524 ms
75 ms
8,422 ms
74 ms
15,629 ms
70 ms
1,579 ms
61 ms
Passed audits (17)
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.
Efficiently encode images
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.
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
Avoid serving legacy JavaScript to modern browsers
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
Preload Largest Contentful Paint image
Preload the image used by the LCP element in order to improve your LCP time. Learn more.LCP
Avoids an excessive DOM size 641 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
641
Maximum DOM Depth
div.slide > div.col-md-8 > div.image-carousel-slide > img
<img src="assets/img/slide-2.jpg" alt="">
22
Maximum Child Elements
body.home
<body class="home page-template page-template-page-templates page-template-template-can…">
22
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.
JavaScript execution time 0.6 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
978 ms
343 ms
6 ms
Unattributable
699 ms
20 ms
1 ms
208 ms
150 ms
4 ms
70 ms
0 ms
0 ms
70 ms
55 ms
5 ms
Minimize third-party usage Third-party code blocked the main thread for 0 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
170 KiB
0 ms
…7a/util.js
(maps.googleapis.com)
91 KiB
0 ms
51 KiB
0 ms
…7a/common.js
(maps.googleapis.com)
28 KiB
0 ms
33 KiB
0 ms
…v23/JTUSjIg1_….woff2
(fonts.gstatic.com)
31 KiB
0 ms
7 KiB
0 ms
…css/font-awesome.min.css
(maxcdn.bootstrapcdn.com)
7 KiB
0 ms
6 KiB
0 ms
/js
(static.getclicky.com)
6 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.
Avoid non-composited animations
Animations which are not composited can be janky and increase 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.
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.
Buttons do not 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.
Failing Elements
div.search > form.input-group > span.input-group-btn > button#search-submit
<button type="submit" id="search-submit" class="btn">
form > div.input-group > span.input-group-btn > button.btn
<button type="submit" class="btn">
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
Important News!!
<div id="br-title" class="br-title">
updated!
<span style="color: red; font-size: 10px;">
2020/2021 Calendar!
<span style="color: red; font-size: 10px;">
updated!
<span style="color: red; font-size: 10px;">
Open!
<span style="color: red; font-size: 10px;">
new!
<span style="color: red; font-size: 10px;">
09-02-2022
<figure class="date">
03-02-2022
<figure class="date">
20-01-2022
<figure class="date">
14-01-2022
<figure class="date">
NavigationThese are opportunities to improve keyboard navigation in your application.
Heading elements are not 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.
Failing Elements
About FUAM
<h4>
Best practicesThese items highlight common accessibility best practices.
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is 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.
Failing Elements
head > meta
<meta name="viewport" content="width=device-width, initial-scale=1, maximum-scale=1">
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.
[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.
[role] values are valid
ARIA roles must have valid values in order to perform their intended accessibility functions. 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.
<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.
Form elements have associated labels
Labels ensure that form controls are announced properly by assistive technologies, like screen readers. 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.
Not applicable (27)
[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-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.
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.
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.
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.
<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.
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
Does not use HTTPS 1 insecure request found
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.
Insecure URL
Request Resolution
Automatically upgraded to HTTPS
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.footer-inner > div.footer-social > div.icons > a.social-icon
<a target="_blank" href="https://twitter.com/" class="social-icon sb-icon-twitter">
div.footer-inner > div.footer-social > div.icons > a.social-icon
<a target="_blank" href="https://www.linkedin.com/" class="social-icon sb-icon-linkedin">
Includes front-end JavaScript libraries with known security vulnerabilities 4 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers. Learn more.
Library Version
Vulnerability Count
Highest Severity
4
Medium
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
Displays images with incorrect aspect ratio
Image display dimensions should match natural aspect ratio. Learn more.
URL
Aspect Ratio (Displayed)
Aspect Ratio (Actual)
130 x 154 (0.84)
150 x 150 (1.00)
General
Detected JavaScript libraries
All front-end JavaScript libraries detected on the page. Learn more.
Name
Version
Google Maps
3.47.7a
jQuery
1.12.4
FlexSlider
WordPress
4.9.19
Browser errors were 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
Source
Description
Failed to load resource: net::ERR_CONNECTION_RESET
Failed to load resource: net::ERR_CONNECTION_RESET
…img/vc.jpg:1:0
(uam.edu.ng)
Failed to load resource: the server responded with a status of 404 (Not Found)
Failed to load resource: the server responded with a status of 404 (Not Found)
Failed to load resource: the server responded with a status of 404 (Not Found)
Failed to load resource: the server responded with a status of 404 (Not Found)
Failed to load resource: the server responded with a status of 404 (Not Found)
Failed to load resource: the server responded with a status of 404 (Not Found)
Failed to load resource: the server responded with a status of 404 (Not Found)
Failed to load resource: the server responded with a status of 404 (Not Found)
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
Mixed content
Passed audits (10)
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.
Allows users to paste into password fields
Preventing password pasting undermines good security policy. Learn more.
Serves images with appropriate resolution
Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. 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.
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.
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 37% 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
News
<a href="https://uam.edu.ng/category/news/">
38x14
Latest News
<a href="https://uam.edu.ng/category/latest-news/">
News
<a href="https://uam.edu.ng/category/news/">
38x14
Student
<a href="https://uam.edu.ng/category/student/">
Events
<a href="https://uam.edu.ng/category/events/">
47x14
Bulletin
<a href="https://uam.edu.ng/category/bulletin/">
Events
<a href="https://uam.edu.ng/category/events/">
47x14
Latest News
<a href="https://uam.edu.ng/category/latest-news/">
About Us
<a href="https://uam.edu.ng/about-us/">
65x14
Affiliations
<a href="https://uam.edu.ng/academics/affiliations/">
Affiliations
<a href="https://uam.edu.ng/academics/affiliations/">
73x14
Academic Calendar
<a href="https://uam.edu.ng/academics/academic-calendar/">
Directorates
<a href="https://uam.edu.ng/directorates/">
85x14
Academic Calendar
<a href="https://uam.edu.ng/academics/academic-calendar/">
Centres
<a href="https://uam.edu.ng/directorates/centres/">
54x14
Directorates
<a href="https://uam.edu.ng/directorates/">
Centres
<a href="https://uam.edu.ng/directorates/centres/">
54x14
Resources
<a href="https://uam.edu.ng/resources/">
Resources
<a href="https://uam.edu.ng/resources/">
72x14
Student Affairs
<a href="https://uam.edu.ng/about-us/administration/student-affairs/">
Student Affairs
<a href="https://uam.edu.ng/about-us/administration/student-affairs/">
104x14
Postgraduate School
<a href="https://uam.edu.ng/academics/postgraduate-school/">
Bulletin
<a href="https://uam.edu.ng/category/bulletin/">
54x14
Breaking News
<a href="https://uam.edu.ng/category/breaking-news/">
College of Agronomy
<a href="https://uam.edu.ng/colleges-departments/agronomy/">
147x14
Agricultural Economics & Extension
<a href="https://uam.edu.ng/colleges-departments/agricultural-economics-extension/">
Agricultural Economics & Extension
<a href="https://uam.edu.ng/colleges-departments/agricultural-economics-extension/">
248x14
Agricultural & Science Education
<a href="https://uam.edu.ng/colleges-departments/agricultural-science-education/">
Agricultural & Science Education
<a href="https://uam.edu.ng/colleges-departments/agricultural-science-education/">
228x14
College of Animal Science
<a href="https://uam.edu.ng/colleges-departments/animal-science/">
College of Animal Science
<a href="https://uam.edu.ng/colleges-departments/animal-science/">
181x14
College of Engineering
<a href="https://uam.edu.ng/colleges-departments/engineering/">
College of Engineering
<a href="https://uam.edu.ng/colleges-departments/engineering/">
160x14
Food Technology & Human Ecology
<a href="https://uam.edu.ng/colleges-departments/food-technology/">
Food Technology & Human Ecology
<a href="https://uam.edu.ng/colleges-departments/food-technology/">
249x14
College of Forestry & Fisheries
<a href="https://uam.edu.ng/colleges-departments/forestry-fishries/">
College of Forestry & Fisheries
<a href="https://uam.edu.ng/colleges-departments/forestry-fishries/">
209x14
College of Management Sciences
<a href="https://uam.edu.ng/colleges-departments/management-sciences/">
College of Science
<a href="https://uam.edu.ng/colleges-departments/science/">
127x14
College of Management Sciences
<a href="https://uam.edu.ng/colleges-departments/management-sciences/">
College of Science
<a href="https://uam.edu.ng/colleges-departments/science/">
127x14
College of Veterinary Medicine
<a href="https://uam.edu.ng/colleges-departments/veterinary-medcine/">
Academic Calendar
<a href="https://www.uam.edu.ng/assets/docs/AcademicCalendar202021.pdf" target="_blank" rel="noopener">
137x26
Check Admission Status
<a href="http://entry.uam.edu.ng/checkadmission/">
Check Admission Status
<a href="http://entry.uam.edu.ng/checkadmission/">
169x26
Postgraduate Application
<a href="http://entry.uam.edu.ng/pg/">
Postgraduate Application
<a href="http://entry.uam.edu.ng/pg/">
178x26
Sandwich Application
<a href="http://entry.uam.edu.ng/sw/">
Sandwich Application
<a href="http://entry.uam.edu.ng/sw/">
153x26
Sandwich Fee Schedule
<a href="https://uam.edu.ng/assets/docs/SandwichSchoolFeesSchedule.pdf">
Sandwich Fee Schedule
<a href="https://uam.edu.ng/assets/docs/SandwichSchoolFeesSchedule.pdf">
167x26
JUPEB Application Form
<a href="http://entry.uam.edu.ng/jupeb">
JUPEB Application Form
<a href="http://entry.uam.edu.ng/jupeb">
173x26
Undergraduate Screening
<a href="http://zportal.uam.edu.ng/">
Undergraduate Screening
<a href="http://zportal.uam.edu.ng/">
182x26
Registration Procedure
<a href="#">
Examination Guidelines
<a href="#">
166x26
Postgraduate School
<a href="https://uam.edu.ng/academics/postgraduate-school/">
Fees Payment
<a href="http://fees.uam.edu.ng">
100x26
Remita Payments
<a href="https://login.remita.net/remita/external/OAGFCRF/collector/payments.reg" target="_blank" rel="noopener">
Remita Payments
<a href="https://login.remita.net/remita/external/OAGFCRF/collector/payments.reg" target="_blank" rel="noopener">
125x26
Student Portal
<a href="http://portal.uam.edu.ng">
Students
<a href="#">
63x26
Student Portal
<a href="http://portal.uam.edu.ng">
Transcript
<a href="#" target="_blank" rel="noopener">
69x26
Webmail
<a href="https://uam.edu.ng/webmail">
Principal Officers
<a href="https://uam.edu.ng/about-us/principal-officers/">
118x26
Office of the Vice Chancellor
<a href="https://uam.edu.ng/about-us/office-of-the-vice-chancellor/">
Registry
<a href="https://uam.edu.ng/about-us/administration/registry/">
57x26
Office of the Vice Chancellor
<a href="https://uam.edu.ng/about-us/office-of-the-vice-chancellor/">
Busary
<a href="https://uam.edu.ng/about-us/administration/bursary/">
48x26
Registry
<a href="https://uam.edu.ng/about-us/administration/registry/">
Busary
<a href="https://uam.edu.ng/about-us/administration/bursary/">
48x26
Librarian
<a href="https://uam.edu.ng/about-us/administration/librarian/">
Librarian
<a href="https://uam.edu.ng/about-us/administration/librarian/">
61x26
Student Affairs
<a href="https://uam.edu.ng/about-us/administration/student-affairs/">
div.footer-inner > div.footer-social > div.icons > a.social-icon
<a target="_blank" href="#" class="social-icon sb-icon-facebook">
30x17
div.footer-inner > div.footer-social > div.icons > a.social-icon
<a target="_blank" href="https://twitter.com/" class="social-icon sb-icon-twitter">
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 (13)
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.
robots.txt is valid
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.
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 99.48% 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
<span style="color: red; font-size: 10px;">
0.18%
10px
.events .event .date .month
0.10%
10px
<span style="color: red; font-size: 10px;">
0.07%
10px
<span style="color: red; font-size: 10px;">
0.07%
10px
<span style="color: red; font-size: 10px;">
0.05%
10px
<span style="color: red; font-size: 10px;">
0.04%
10px
<span style="color: red; font-size: 10px;">
0.01%
10px
Legible text
99.48%
≥ 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 not sized correctly for the viewport
The viewport size of 375px does not match the window size of 360px.
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
Does not provide 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.