https://atbu.edu.ng/web/front
60
Performance
73
Accessibility
87
Best Practices
69
SEO
Progressive Web App
60
Performance
73
Accessibility
87
Best Practices
69
SEO
Progressive Web App
0–49 50–89 90–100

There were issues affecting this run of Lighthouse:

  • The page may not be loading as expected because your test URL (https://atbu.edu.ng/) was redirected to https://atbu.edu.ng/web/front. Try testing the second URL directly.
60
Performance
Metrics
First Contentful Paint
3.2 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.
Speed Index
8.7 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
Largest Contentful Paint
5.6 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more
Time to Interactive
3.2 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Total Blocking Time
0 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.188
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
2.26 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.
URL
Resource Size
Potential Savings
…slides/5.jpg
(atbu.edu.ng)
202.7 KiB
94.2 KiB
…slides/4.jpg
(atbu.edu.ng)
186.9 KiB
91.4 KiB
…slides/6.jpg
(atbu.edu.ng)
111.2 KiB
58.4 KiB
…slides/3.jpg
(atbu.edu.ng)
108.1 KiB
57.2 KiB
…slides/7.jpg
(atbu.edu.ng)
104.6 KiB
55.7 KiB
…slides/2.jpg
(atbu.edu.ng)
103.7 KiB
55.5 KiB
…slides/1.jpg
(atbu.edu.ng)
107.6 KiB
19.1 KiB
…images/atbu_logo.png
(atbu.edu.ng)
12.0 KiB
10.0 KiB
Eliminate render-blocking resources
2.06 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
URL
Transfer Size
Potential Savings
…css/w3.css
(atbu.edu.ng)
5.4 KiB
640 ms
…css/app.css
(atbu.edu.ng)
0.8 KiB
790 ms
…css/w3-theme-blue-grey.css
(atbu.edu.ng)
0.5 KiB
790 ms
…css/fontawesome-all.min.css
(atbu.edu.ng)
11.8 KiB
1,090 ms
/css2?family=Eczar:wght@800&display=swap
(fonts.googleapis.com)
0.9 KiB
1,150 ms
Use HTTP/2
1.52 s
HTTP/2 offers many benefits over HTTP/1.1, including binary headers and multiplexing. Learn more.
URL
Protocol
https://atbu.edu.ng
http/1.1
/web/front
(atbu.edu.ng)
http/1.1
…css/w3.css
(atbu.edu.ng)
http/1.1
…css/app.css
(atbu.edu.ng)
http/1.1
…css/w3-theme-blue-grey.css
(atbu.edu.ng)
http/1.1
…css/fontawesome-all.min.css
(atbu.edu.ng)
http/1.1
…images/atbu_logo.png
(atbu.edu.ng)
http/1.1
…images/atbu_header_title_1_1.png
(atbu.edu.ng)
http/1.1
…images/atbu_header_title_2_2.png
(atbu.edu.ng)
http/1.1
…slides/1.jpg
(atbu.edu.ng)
http/1.1
…slides/2.jpg
(atbu.edu.ng)
http/1.1
…slides/3.jpg
(atbu.edu.ng)
http/1.1
…slides/4.jpg
(atbu.edu.ng)
http/1.1
…slides/5.jpg
(atbu.edu.ng)
http/1.1
…slides/6.jpg
(atbu.edu.ng)
http/1.1
…slides/7.jpg
(atbu.edu.ng)
http/1.1
…js/w3.js
(atbu.edu.ng)
http/1.1
…webfonts/fa-solid-900.woff2
(atbu.edu.ng)
http/1.1
Reduce unused CSS
0.15 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
URL
Transfer Size
Potential Savings
…css/fontawesome-all.min.css
(atbu.edu.ng)
11.8 KiB
11.7 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
…webfonts/fa-solid-900.woff2
(atbu.edu.ng)
1,280 ms
…v15/mem8YaGs1….woff2
(fonts.gstatic.com)
1,130 ms
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
…slides/1.jpg
(atbu.edu.ng)
div > div.w3-display-container > div.w3-display-container > img
<img src="/public/assets/slides/1.jpg" style="width:100%;height:inherit;object-fit:cover;object-position:top">
…images/atbu_header_title_2_2.png
(atbu.edu.ng)
div#topNav > div.w3-bar > a.w3-bar-item > img
<img src="../public/assets/images/atbu_header_title_2_2.png" style="height:35px; margin-left: -10px;" alt="">
…images/atbu_logo.png
(atbu.edu.ng)
div#topNav > div.w3-bar > a.w3-bar-item > img
<img src="../public/assets/images/atbu_logo.png" style="height:61px;" alt="">
Serve static assets with an efficient cache policy 16 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.
URL
Cache TTL
Transfer Size
…slides/5.jpg
(atbu.edu.ng)
None
203 KiB
…slides/4.jpg
(atbu.edu.ng)
None
187 KiB
…slides/6.jpg
(atbu.edu.ng)
None
111 KiB
…slides/3.jpg
(atbu.edu.ng)
None
108 KiB
…slides/1.jpg
(atbu.edu.ng)
None
108 KiB
…slides/7.jpg
(atbu.edu.ng)
None
105 KiB
…slides/2.jpg
(atbu.edu.ng)
None
104 KiB
…webfonts/fa-solid-900.woff2
(atbu.edu.ng)
None
73 KiB
…images/atbu_logo.png
(atbu.edu.ng)
None
12 KiB
…css/fontawesome-all.min.css
(atbu.edu.ng)
None
12 KiB
…css/w3.css
(atbu.edu.ng)
None
5 KiB
…images/atbu_header_title_1_1.png
(atbu.edu.ng)
None
4 KiB
…js/w3.js
(atbu.edu.ng)
None
3 KiB
…images/atbu_header_title_2_2.png
(atbu.edu.ng)
None
2 KiB
…css/app.css
(atbu.edu.ng)
None
1 KiB
…css/w3-theme-blue-grey.css
(atbu.edu.ng)
None
1 KiB
Minimize main-thread work 2.2 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
833 ms
Rendering
664 ms
Style & Layout
643 ms
Parse HTML & CSS
43 ms
Script Evaluation
39 ms
Script Parsing & Compilation
6 ms
Avoid chaining critical requests 6 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: 5,330 ms
Initial Navigation
https://atbu.edu.ng
/web/front
(atbu.edu.ng)
…css/w3.css
(atbu.edu.ng)
- 330 ms, 5.38 KiB
…css/app.css
(atbu.edu.ng)
…v15/mem8YaGs1….woff2
(fonts.gstatic.com)
- 1,130 ms, 14.34 KiB
…css/w3-theme-blue-grey.css
(atbu.edu.ng)
- 1,240 ms, 0.54 KiB
…css/fontawesome-all.min.css
(atbu.edu.ng)
…webfonts/fa-solid-900.woff2
(atbu.edu.ng)
- 1,280 ms, 72.86 KiB
/css2?family=Eczar:wght@800&display=swap
(fonts.googleapis.com)
…v13/BXRovF3Pi….woff2
(fonts.gstatic.com)
- 1,220 ms, 11.13 KiB
…js/w3.js
(atbu.edu.ng)
- 1,240 ms, 3.29 KiB
Keep request counts low and transfer sizes small 21 requests • 1,076 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
21
1,075.9 KiB
Image
10
944.7 KiB
Font
3
98.3 KiB
Stylesheet
5
19.5 KiB
Document
1
9.6 KiB
Script
1
3.3 KiB
Other
1
0.4 KiB
Media
0
0.0 KiB
Third-party
3
26.4 KiB
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport. Learn MoreLCP
Element
div > div.w3-display-container > div.w3-display-container > img
<img src="/public/assets/slides/1.jpg" style="width:100%;height:inherit;object-fit:cover;object-position:top">
Avoid large layout shifts 3 elements found
These DOM elements contribute most to the CLS of the page.CLS
Element
CLS Contribution
…
<div class="w3-display-container mySlides w3-animate-right" style="height: inherit; display: none;">
0.187
Welcome to ATBU Official Website
<b>
0.001
DOCTRINA MATER ARTIUM
<i>
0
Avoid long main-thread tasks 3 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
Unattributable
1,715 ms
85 ms
/web/front
(atbu.edu.ng)
1,650 ms
65 ms
/web/front
(atbu.edu.ng)
1,586 ms
64 ms
Avoid non-composited animations 8 animated elements found
Animations which are not composited can be janky and increase CLS. Learn moreCLS
Element
Name
<div class="w3-display-container mySlides w3-animate-right" style="height: inherit; display: none;">
Unsupported CSS Property: right
animateright
…
<div class="w3-display-container mySlides w3-animate-right" style="height: inherit; display: none;">
Unsupported CSS Property: right
animateright
<div class="w3-display-container mySlides w3-animate-right" style="height: inherit; display: none;">
Unsupported CSS Property: right
animateright
SENATE APPROVED ACADEMIC CALENDAR FOR 2020/2021 ACADEMIC SESSION. Click here to…
<ul>
Unsupported CSS Property: margin-top
ticker
div.fcol2 > div > div.w3-display-container > div.w3-display-container
<div class="w3-display-container mySlides w3-animate-right" style="height: inherit; display: block;">
Unsupported CSS Property: right
animateright
…
<div class="w3-display-container mySlides w3-animate-right" style="height: inherit; display: none;">
Unsupported CSS Property: right
animateright
…
<div class="w3-display-container mySlides w3-animate-right" style="height: inherit; display: none;">
Unsupported CSS Property: right
animateright
…
<div class="w3-display-container mySlides w3-animate-right" style="height: inherit; display: none;">
Unsupported CSS Property: right
animateright
Passed audits (25)
Properly size images
Serve images that are appropriately-sized to save cellular data and improve load time. 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.
Minify CSS
Minifying CSS files can reduce network payload sizes. Learn more.FCPLCP
Minify JavaScript
Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.FCPLCP
Reduce unused JavaScript
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn more.LCP
Efficiently encode images
Optimized images load faster and consume less cellular data. Learn more.
Enable text compression
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.FCPLCP
Preconnect to required origins
Consider adding `preconnect` or `dns-prefetch` resource hints to establish early connections to important third-party origins. Learn more.FCPLCP
Initial server response time was short Root document took 400 ms
Keep the server response time for the main document short because all other requests depend on it. Learn more.FCPLCP
URL
Time Spent
/web/front
(atbu.edu.ng)
400 ms
Avoid multiple page redirects Potential savings of 1,090 ms
Redirects introduce additional delays before the page can be loaded. Learn more.FCPLCP
URL
Time Spent
https://atbu.edu.ng
1,090 ms
/web/front
(atbu.edu.ng)
0 ms
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
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 enormous network payloads Total size was 1,076 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.LCP
URL
Transfer Size
…slides/5.jpg
(atbu.edu.ng)
202.9 KiB
…slides/4.jpg
(atbu.edu.ng)
187.1 KiB
…slides/6.jpg
(atbu.edu.ng)
111.5 KiB
…slides/3.jpg
(atbu.edu.ng)
108.4 KiB
…slides/1.jpg
(atbu.edu.ng)
107.8 KiB
…slides/7.jpg
(atbu.edu.ng)
104.9 KiB
…slides/2.jpg
(atbu.edu.ng)
103.9 KiB
…webfonts/fa-solid-900.woff2
(atbu.edu.ng)
72.9 KiB
…v15/mem8YaGs1….woff2
(fonts.gstatic.com)
14.3 KiB
…images/atbu_logo.png
(atbu.edu.ng)
12.2 KiB
Avoids an excessive DOM size 265 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
265
Maximum DOM Depth
Welcome to ATBU Official Website
<b>
11
Maximum Child Elements
Physical Infrastructure/Program Upgrade Academ…
<div onmouseover="show('menu2child')" onmouseout="hide('menu2child')" id="menu2child" style="left:100%;top: 34px;display:none;width:300px" class="w3-dropdown-content w3-bar-block w3-card-4">
12
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.0 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
/web/front
(atbu.edu.ng)
1,839 ms
18 ms
5 ms
Unattributable
349 ms
21 ms
1 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
Google Fonts
26 KiB
0 ms
…v15/mem8YaGs1….woff2
(fonts.gstatic.com)
14 KiB
0 ms
…v13/BXRovF3Pi….woff2
(fonts.gstatic.com)
11 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.
Element
div > div.w3-display-container > div.w3-display-container > img
<img src="/public/assets/slides/1.jpg" style="width:100%;height:inherit;object-fit:cover;object-position:top">
Uses 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.
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.
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
73
Accessibility
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
Latest News
<span>
POSTGRADUATE ACADEMIC CALENDAR FOR 2020/2021 ACADEMIC SESSION. Click here to vi…
<a href="/public/assets/files/2020-2021 PG Calendar.pdf" target="_blank">
Providing relevant and high quality education, preparing individuals for work, …
<p class="w3-large w3-text-white" style="text-shadow: 1px 1px 0 #444;">
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
Contact us:
<h4>
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.
Image elements do not have [alt] attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more.
Failing Elements
div > div.w3-display-container > div.w3-display-container > img
<img src="/public/assets/slides/2.jpg" style="width:100%;height:inherit;object-fit:cover;object-position:top">
Links do not have a discernible name
Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn more.
Failing Elements
div.topnav > div#topNav > div.w3-bar > a.w3-bar-item
<a href="/" class="w3-bar-item w3-padding-small w3-button">
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 (9)
[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.
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.
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.
<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.
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 (31)
[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.
[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.
<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.
[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.
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.
87
Best Practices
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
Profile
<a href="https://www.youtube.com/watch?v=TYoKzq8kUZk&amp;feature=youtu.be" target="_blank" class="w3-btn w3-round w3-theme-d3 w3-block">
TETFund
<a style="text-decoration:none; text-align:left" class="w3-button w3-block" target="_blank" href="http://tetfund.gov.ng">
NUC
<a style="text-decoration:none; text-align:left" class="w3-button w3-block" target="_blank" href="http://nuc.edu.ng">
Ministry of Education
<a style="text-decoration:none; text-align:left" class="w3-button w3-block" target="_blank" href="http://education.gov.ng">
Facebook
<a href="https://www.facebook.com/ATBU-Bauchi-320790967982358/" target="_blank" style="text-decoration:none">
Twitter
<a href="https://twitter.com/ATBUBauchi3" target="_blank" style="text-decoration:none">
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
…images/atbu_logo.png
(atbu.edu.ng)
67 x 61
66 x 60
134 x 122
Passed audits (14)
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.
No issues 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.
Not applicable (2)
Fonts with font-display: optional are preloaded
Preload `optional` fonts so first-time visitors may use them. Learn more
Detected JavaScript libraries
All front-end JavaScript libraries detected on the page. Learn more.
69
SEO
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.
Content Best PracticesFormat your HTML in a way that enables crawlers to better understand your app’s content.
Document does not have a meta description
Meta descriptions may be included in search results to concisely summarize page content. Learn more.
Image elements do not have [alt] attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more.
Failing Elements
div > div.w3-display-container > div.w3-display-container > img
<img src="/public/assets/slides/2.jpg" style="width:100%;height:inherit;object-fit:cover;object-position:top">
Crawling and IndexingTo appear in search results, crawlers need access to your app.
Links are not 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
Uncrawlable Link
div.topnav > div#topNav > div.w3-bar > a.w3-bar-item
<a class="w3-bar-item w3-button w3-hide-large w3-right w3-hover-white w3-large w3-th…" href="javascript:void(0);" onclick="openNav()" style="padding:20.5px 20px">
Motto: DOCTRINA MATER ARTIUM Education is the mot…
<a class="w3-bar-item w3-padding-small w3-hide-small">
Motto: DOCTRINA MATER ARTIUM
<a class="w3-bar-item w3-padding-small w3-hide-large w3-hide-medium" style="padding-left:0px !important; padding-right:0px !important">
Portals  
<a onclick="javascript:void(0)" class="w3-padding w3-button">
robots.txt is not valid 494 errors found
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.
Line #
Content
Error
1
<!DOCTYPE html>
Syntax not understood
2
<html lang="en">
Syntax not understood
4
<head>
Syntax not understood
5
  <meta http-equiv="content-type" content="text/html; charset=UTF-8">
Syntax not understood
6
  <meta charset="UTF-8">
Syntax not understood
7
  <meta name="viewport" content="width=device-width, initial-scale=1">
Syntax not understood
9
  <title>ATBU Portal - Page Not Found (404) Error!</title>
Syntax not understood
11
  <link rel="stylesheet" href="public/assets/css/w3.css">
Syntax not understood
12
  <link rel="stylesheet" href="public/assets/css/app.css">
Syntax not understood
13
  <link rel="stylesheet" href="public/assets/css/w3-theme-blue-grey.css">
Syntax not understood
14
  <link rel="stylesheet" href="public/assets/css/fontawesome-all.min.css">
Syntax not understood
15
    <link href="https://fonts.googleapis.com/css2?family=Eczar:wght@800&display=swap" rel="stylesheet">
Unknown directive
18
  <style>
Syntax not understood
19
.w3-eczar { font-family: 'Eczar', serif; }
Unknown directive
20
.full-vh {
Syntax not understood
21
  height: 100vh;
Unknown directive
22
}
Syntax not understood
23
.full-height {
Syntax not understood
24
  height: 100%
Unknown directive
25
}
Syntax not understood
26
.flex-row {
Syntax not understood
27
  display: flex;
Unknown directive
28
  flex-direction: row;
Unknown directive
29
}
Syntax not understood
30
.flex-col {
Syntax not understood
31
  display: flex;
Unknown directive
32
  flex-direction: column;
Unknown directive
33
}
Syntax not understood
34
.icons {
Syntax not understood
35
  display:inline;
Unknown directive
36
}
Syntax not understood
37
.icon-cell {
Syntax not understood
38
  padding: 24px 48px;
Unknown directive
39
}
Syntax not understood
40
.footer-cell {
Syntax not understood
41
  flex: 50%;
Unknown directive
42
}
Syntax not understood
43
@media (max-width: 600px) {
Unknown directive
44
  .icons {
Syntax not understood
45
    display: block;
Unknown directive
46
    width: 100%;
Unknown directive
47
    float: left !important;
Unknown directive
48
  }
Syntax not understood
49
  .icons-with-bottom-margin {
Syntax not understood
50
    margin-bottom: 12px;
Unknown directive
51
  }
Syntax not understood
52
  .icon-cell {
Syntax not understood
53
    padding: 0 48px 24px !important;
Unknown directive
54
  }
Syntax not understood
55
  .footer-cell {
Syntax not understood
56
    flex: 100%;
Unknown directive
57
  }
Syntax not understood
58
}
Syntax not understood
59
/* accordion styles */
Syntax not understood
60
.accordion:after {
Unknown directive
61
  content: '\02795'; /* Unicode character for "plus" sign (+) */
Unknown directive
62
  color: #777;
Unknown directive
63
  float: right;
Unknown directive
64
  margin-left: 5px;
Unknown directive
65
}
Syntax not understood
66
.accordion-panel {
Syntax not understood
67
  background-color: white;
Unknown directive
68
  max-height: 0;
Unknown directive
69
  overflow: hidden;
Unknown directive
70
  transition: max-height 0.2s ease-out;
Unknown directive
71
}
Syntax not understood
72
.accordion.active:after {
Unknown directive
73
  content: "\2796"; /* Unicode character for "minus" sign (-) */
Unknown directive
74
}
Syntax not understood
76
/* modal styles */
Syntax not understood
77
.dom-modal { 
Syntax not understood
78
  display: none; 
Unknown directive
79
  position: fixed; 
Unknown directive
80
  top:0; 
Unknown directive
81
  left:0; 
Unknown directive
82
  width:100%; 
Unknown directive
83
  height:100%; 
Unknown directive
84
  z-index:999; 
Unknown directive
85
  background-color: rgb(0,0,0); /* Fallback color */
Unknown directive
86
  background-color: rgba(0,0,0,0.4); /* Black w/ opacity */
Unknown directive
87
}
Syntax not understood
88
.dom-modal .modal-wrapper { 
Syntax not understood
89
  position: fixed; 
Unknown directive
90
  top: 50%; 
Unknown directive
91
  left: 50%; 
Unknown directive
92
  transform: translate(-50%, -50%);
Unknown directive
93
  max-height:90%; 
Unknown directive
94
  max-width:90%; 
Unknown directive
95
  background-color: #fefefe;
Unknown directive
96
}
Syntax not understood
97
.dom-modal .modal-header {}
Syntax not understood
98
.dom-modal .modal-body { overflow: auto; min-width:400px; flex-grow:1; }
Unknown directive
99
.dom-modal .modal-footer {}
Syntax not understood
100
</style>
Syntax not understood
102
<style>
Syntax not understood
103
  .main-content-container {
Syntax not understood
104
      flex-grow:1;
Unknown directive
105
      padding:4px;
Unknown directive
106
      height:0;
Unknown directive
107
      min-height:0;
Unknown directive
108
      align-items:stretch;
Unknown directive
109
  }
Syntax not understood
110
  .sidebar {
Syntax not understood
111
      flex-grow:0;
Unknown directive
112
      flex-shrink:0;
Unknown directive
113
      padding:0px !important;
Unknown directive
114
      min-height:0;
Unknown directive
115
      margin-right:4px !important;
Unknown directive
116
  }
Syntax not understood
118
      width:277px;
Unknown directive
119
  }
Syntax not understood
121
      flex-grow:1;
Unknown directive
122
      overflow:auto;
Unknown directive
123
  }
Syntax not understood
124
  .page-header {
Syntax not understood
125
      flex-shrink:0;
Unknown directive
126
  }
Syntax not understood
127
  .page-content {
Syntax not understood
128
      flex-grow:1;
Unknown directive
129
      min-height:0;
Unknown directive
130
  }
Syntax not understood
131
</style>
Syntax not understood
133
</head>
Syntax not understood
135
<body class="w3-theme-l5 full-vh" style="width:100%;">
Unknown directive
136
  <div class="flex-col full-height">
Syntax not understood
137
    <!-- Top Navigation -->
Syntax not understood
138
    <div class="topnav">
Syntax not understood
139
        <!-- Navbar -->
Syntax not understood
140
  <div id="topNav" class="w3-block">
Syntax not understood
141
    <div class="w3-bar w3-theme-d2 w3-left-align">
Syntax not understood
142
            <a href="/" class="w3-bar-item w3-padding-small w3-button">
Syntax not understood
143
        <img src="public/assets/images/atbu_logo.png" style="height:61px;" alt="">
Unknown directive
144
      </a>
Syntax not understood
145
      <a class="w3-bar-item w3-padding-small w3-hide-small">
Syntax not understood
146
        <img src="public/assets/images/atbu_header_title_1_1.png" style="height:35px; margin-left: -10px;" alt="">
Unknown directive
147
        <div style="margin-left:0px;font-size:12px;margin-top:-10px">
Unknown directive
148
          Motto: <i>DOCTRINA MATER ARTIUM</i> <br/> Education is the mother of all practical arts
Unknown directive
149
        </div>
Syntax not understood
150
      </a>
Syntax not understood
151
      <a class="w3-bar-item w3-padding-small w3-hide-large w3-hide-medium" style="padding-left:0px !important; padding-right:0px !important">
Unknown directive
152
        <img src="public/assets/images/atbu_header_title_2_2.png" style="height:35px; margin-left: -10px;" alt="">
Unknown directive
153
        <div style="margin-left:0px;font-size:16px">Motto: <i>DOCTRINA MATER ARTIUM</i></div>
Unknown directive
154
      </a>
Syntax not understood
155
          </div>
Syntax not understood
156
    <!-- Navbar on small screens -->
Syntax not understood
157
        <!-- End Navbar on small screens -->
Syntax not understood
158
  </div>
Syntax not understood
159
    </div>
Syntax not understood
160
    <!-- End Top Navigation -->
Syntax not understood
162
    <!-- Page Container -->
Syntax not understood
163
    <div class="main-content-container flex-row">
Syntax not understood
164
                <!-- The Content Area -->
Syntax not understood
165
        <div id="page-container" class="w3-card w3-border w3-white flex-col">
Syntax not understood
166
          <div class="page-header w3-container w3-theme-d4">
Syntax not understood
167
            <h4><a href="/" class="w3-padding-small w3-round w3-border w3-margin-right w3-hover-white" title="Main website" style="text-decoration:none"><i class="fa fa-globe w3-large"></i></a>Page Not Found (404) Error!</h4>
Unknown directive
168
          </div>
Syntax not understood
169
          <div class="page-content flex-row">
Syntax not understood
170
            <div class="flex-col" style="overflow:auto;flex-grow:1">
Unknown directive
171
                <div class="w3-container w3-red" style="margin:2px">
Unknown directive
172
        <p class="">The page you are looking for was not found or is still under construction!</p>
Syntax not understood
173
  </div>
Syntax not understood
174
            </div>
Syntax not understood
175
          </div>
Syntax not understood
176
        </div>
Syntax not understood
177
    <!-- End Page Container -->
Syntax not understood
178
    </div>
Syntax not understood
180
    <!-- Footer -->    
Syntax not understood
181
    <div class="footer" style="flex-basis:53px">
Unknown directive
182
        <!-- Footer -->
Syntax not understood
183
<footer class="w3-bottoms" style="">
Syntax not understood
184
  <div class="flex-row w3-theme-d5" style="flex-wrap: wrap-reverse;">
Unknown directive
185
    <div class="footer-cell flex-row" style="align-items:center; padding:8px 48px;"><span>Copyright &copy; 2022, <a href="https://atbu.edu.ng" target="_blank" style="text-decoration:none">Abubakar Tafawa Balewa University, Bauchi</a></span>
Unknown directive
186
</div>
Syntax not understood
187
    <div class="footer-cell flex-row w3-hide-small" style="justify-content:flex-end; padding: 8px 48px;"><div class="icons w3-center">
Unknown directive
188
  <a href="https://www.facebook.com/ATBU-Bauchi-320790967982358/" target="_blank" style="text-decoration:none"><i class="fab fa-facebook-square w3-xlarge w3-hover-text-yellow w3-circle" style="line-height:revert"> <span class="w3-large" style="vertical-align:middle"><em>Facebook</em></span></i></a>
Unknown directive
189
  <a href="https://twitter.com/ATBUBauchi3" target="_blank" style="text-decoration:none"><i class="fab fa-twitter-square w3-xlarge w3-hover-text-yellow w3-circle w3-margin-left" style="line-height:revert"> <span class="w3-large" style="vertical-align:middle"><em>Twitter</em></span></i></a>
Unknown directive
190
</div>
Syntax not understood
191
</div>
Syntax not understood
192
  </div>
Syntax not understood
193
</footer>    </div>
Syntax not understood
194
    <!-- End Footer Footer -->    
Syntax not understood
195
  </div>
Syntax not understood
196
<script src="public/assets/js/w3.js"></script>
Syntax not understood
197
<script>
Syntax not understood
198
    var portal = {};
Syntax not understood
199
    portal.title = 'ATBU Portal';
Syntax not understood
200
    portal.ajax = {};
Syntax not understood
201
    portal.isJson = function(str)
Syntax not understood
202
    {
Syntax not understood
203
        try {
Syntax not understood
204
            JSON.parse(str);
Syntax not understood
205
        } catch (e) {
Syntax not understood
206
            return false;
Syntax not understood
207
        }
Syntax not understood
208
        return true;
Syntax not understood
209
    }
Syntax not understood
210
    portal.ajax.Send = function (data,onsuccess,onerror=null,method='POST',url='') {
Syntax not understood
211
        var ajax = new XMLHttpRequest();
Syntax not understood
212
        //ajax.responseType = 'json';
Syntax not understood
213
        // Define what happens on successful data submission
Syntax not understood
214
        ajax.onload = function(event) {
Syntax not understood
215
          var data = ajax.response;
Syntax not understood
216
          if(portal.isJson(data)) data = JSON.parse(data);
Syntax not understood
217
          if(data && data.csrf) {
Syntax not understood
218
            var csrf = data.csrf;
Syntax not understood
219
            var tnk = document.getElementById('csrf_name');
Syntax not understood
220
            if(tnk) tnk.value = csrf.csrf_name;
Syntax not understood
221
            var tvk = document.getElementById('csrf_value');
Syntax not understood
222
            if(tvk) tvk.value = csrf.csrf_value;              
Syntax not understood
223
          }
Syntax not understood
224
          if(onsuccess) onsuccess(data); 
Syntax not understood
225
        };
Syntax not understood
226
        // Define what happens in case of error
Syntax not understood
227
        ajax.onerror = function(event) { if(onerror) onerror(ajax.response); };
Syntax not understood
228
        // Set up our request
Syntax not understood
229
        ajax.open(method, url);
Syntax not understood
230
        //set ajax request header
Syntax not understood
231
        ajax.setRequestHeader('X-Requested-With','XMLHttpRequest');
Syntax not understood
232
        // The data sent is what the user provided in the form
Syntax not understood
233
        ajax.send(data);
Syntax not understood
234
    }
Syntax not understood
235
    portal.ajax.SendFormData = function (form,onsuccess,onerror=null,method='POST',url='') {
Syntax not understood
236
        // Bind the FormData object and the form element
Syntax not understood
237
        var FD = new FormData(form);
Syntax not understood
239
        portal.ajax.Send(FD, onsuccess, onerror, method, url);
Syntax not understood
240
    }
Syntax not understood
241
    portal.ajax.SendData = function (data,onsuccess,onerror=null,method='POST',url='') {
Syntax not understood
242
        // Bind the FormData object and the form element
Syntax not understood
243
        var FD = new FormData();
Syntax not understood
244
        // Push our data into our FormData object
Syntax not understood
245
        for(name in data) {
Syntax not understood
246
          FD.append(name, data[name]);
Syntax not understood
247
        }
Syntax not understood
249
        portal.ajax.Send(FD, onsuccess, onerror, method, url);
Syntax not understood
250
    }
Syntax not understood
251
    portal.dom = {};
Syntax not understood
252
    portal.dom.PopulateSelectTag = function (select_elt, options, selected_value = null, prompt = null, list_key_property = null, list_desc_property = null)
Syntax not understood
253
    {
Syntax not understood
254
        if(select_elt && options && Array.isArray(options))
Syntax not understood
255
        {
Syntax not understood
256
            var opts = prompt ? '<option value="">'+(options && options.length>0?prompt:'')+'</option>' : '';
Unknown directive
257
            var id = select_elt.id ? ' id='+select_elt.id+'_' : null;
Unknown directive
258
            for(var i=0; i<options.length; i++)
Syntax not understood
259
            {
Syntax not understood
260
                var option = options[i];
Syntax not understood
261
                var opt_val = (typeof option == 'object') && list_key_property && option[list_key_property] ? option[list_key_property] : option;
Unknown directive
262
                var opt_des = (typeof option == 'object') && list_desc_property && option[list_desc_property] ? option[list_desc_property] : option;
Unknown directive
263
                opts += '<option'+(id?id+opt_val:'')+' value="'+opt_val+'"'+(selected_value==opt_val ? ' selected ':'')+'>'+opt_des+'</option>';
Unknown directive
264
            }
Syntax not understood
265
            select_elt.innerHTML = opts;
Syntax not understood
266
        }
Syntax not understood
267
    }
Syntax not understood
268
    portal.dom.CreateAccordions = function()
Syntax not understood
269
    {
Syntax not understood
270
        var acc = document.getElementsByClassName("accordion");
Syntax not understood
271
        var i;
Syntax not understood
273
        for (i = 0; i < acc.length; i++) {
Syntax not understood
274
          acc[i].addEventListener("click", function() {
Syntax not understood
275
            /* Toggle between adding and removing the "active" class,
Syntax not understood
276
            to highlight the button that controls the panel */
Syntax not understood
277
            this.classList.toggle("active");
Syntax not understood
279
          var panel = this.nextElementSibling;
Syntax not understood
280
          if (panel.style.maxHeight){
Syntax not understood
281
              panel.style.maxHeight = null;
Syntax not understood
282
            } else {
Syntax not understood
283
              panel.style.maxHeight = panel.scrollHeight + "px";
Syntax not understood
284
            } 
Syntax not understood
285
          });
Syntax not understood
286
        }
Syntax not understood
287
    }
Syntax not understood
288
    portal.dom.ShowModal = function(options)
Syntax not understood
289
    {
Syntax not understood
290
      var defaultOptions = {
Syntax not understood
291
        modalId:null, modalTitle:portal.title, 
Unknown directive
292
        modalButtons:null, isClosable:true,
Unknown directive
293
        content:null,
Unknown directive
294
      };
Syntax not understood
295
      options = options || defaultOptions;
Syntax not understood
296
      if(typeof options === 'string') { 
Syntax not understood
297
        defaultOptions.modalId = options; options = defaultOptions; 
Syntax not understood
298
      }
Syntax not understood
299
      options = Object.assign(defaultOptions, options);
Syntax not understood
301
      var modalId = options.modalId, modalTitle = options.modalTitle, 
Syntax not understood
302
          modalButtons = options.modalButtons, isClosable = options.isClosable;
Syntax not understood
304
      var dlg = document.getElementById(modalId);
Syntax not understood
305
      if(dlg == null)
Syntax not understood
306
      {
Syntax not understood
307
        modalId = 'temp_modal_01';
Syntax not understood
308
        dlg = document.getElementById(modalId);
Syntax not understood
309
        if(dlg == null) {
Syntax not understood
310
          dlg = document.createElement('div');
Syntax not understood
311
          dlg.id = modalId;
Syntax not understood
312
          dlg.style.zIndex = 1 + portal.dom.GetHighestZIndex('div.dom-modal');
Syntax not understood
313
          document.getElementsByClassName('page-content')[0].children[0].insertAdjacentElement('beforeend',dlg);
Syntax not understood
314
        }
Syntax not understood
315
        if(dlg.querySelector('.modal-body') != null) dlg.querySelector('.modal-body').innerHTML = null;
Syntax not understood
316
      }
Syntax not understood
317
      dlg.classList.add('dom-modal');
Syntax not understood
319
      var mdc;
Syntax not understood
320
      var closeFunc = function() { portal.dom.HideModal(modalId); };
Syntax not understood
322
      var wrp = dlg.querySelector('div.modal-wrapper');
Syntax not understood
323
      if(wrp == null)
Syntax not understood
324
      {
Syntax not understood
325
        var wrp = document.createElement('div');
Syntax not understood
326
        wrp.classList.add('modal-wrapper', 'w3-card-4', 'w3-border', 'w3-round', 'flex-col');
Syntax not understood
327
        while(dlg.children.length > 0) {
Syntax not understood
328
          wrp.appendChild(dlg.children[0]);
Syntax not understood
329
        }
Syntax not understood
330
        dlg.appendChild(wrp);
Syntax not understood
331
      }
Syntax not understood
332
      mdc = dlg.querySelector('.modal-wrapper');
Syntax not understood
333
      //check if there is header. If there is none, add it
Syntax not understood
334
      var hd = dlg.querySelector('.modal-header');
Syntax not understood
335
      if(hd == null)
Syntax not understood
336
      {
Syntax not understood
337
        var hd = document.createElement('div');
Syntax not understood
338
        hd.setAttribute('class',"modal-header w3-container w3-theme-d1");
Syntax not understood
339
        if(isClosable) {
Syntax not understood
340
          var closer = document.createElement('span');
Syntax not understood
341
          closer.setAttribute('class',"w3-button w3-red w3-display-topright");
Syntax not understood
342
          closer.innerHTML = '&times';
Syntax not understood
343
          closer.addEventListener("click",closeFunc);
Syntax not understood
344
          hd.appendChild(closer);
Syntax not understood
345
        }
Syntax not understood
346
        var hdTitle = document.createElement('h2');
Syntax not understood
347
        hdTitle.innerHTML = modalTitle ? modalTitle : portal.title;
Unknown directive
348
        hd.appendChild(hdTitle);
Syntax not understood
349
        mdc.insertBefore(hd,mdc.children[0]);
Syntax not understood
350
      }
Syntax not understood
351
      //check if there is no indicated modal-body then setup one if can
Syntax not understood
352
      var con = dlg.querySelector('.modal-body');
Syntax not understood
353
      if(con == null)
Syntax not understood
354
      {
Syntax not understood
355
        con = document.createElement('div');
Syntax not understood
356
        con.classList.add('modal-body');
Syntax not understood
357
        if(hd.nextElementSibling != null) con.appendChild(hd.nextElementSibling);
Syntax not understood
358
        hd.insertAdjacentElement("afterend", con);
Syntax not understood
359
      }
Syntax not understood
360
      if(options.content != null && typeof options.content==='string')
Syntax not understood
361
      {
Syntax not understood
362
        con.classList.add('w3-padding-large');
Syntax not understood
363
        con.innerHTML = options.content;
Syntax not understood
364
      }
Syntax not understood
365
      //if buttons param is present and is an array of objects then
Syntax not understood
366
      if(modalButtons && Array.isArray(modalButtons))
Syntax not understood
367
      {
Syntax not understood
368
        var foot = dlg.querySelector('.modal-footer');
Syntax not understood
369
        if(foot == null) {
Syntax not understood
370
          foot = document.createElement('div');
Syntax not understood
371
          mdc.insertAdjacentElement("beforeend",foot);
Syntax not understood
372
        }
Syntax not understood
373
        foot.classList.add('modal-footer','w3-container','w3-theme-d1','w3-padding');
Syntax not understood
374
        for(var i=modalButtons.length-1; i>=0; i--) {
Syntax not understood
375
          var btnId = modalId + '_btn' + i;
Syntax not understood
376
          if(dlg.querySelector('#'+btnId)==null) {
Syntax not understood
377
            option = modalButtons[i];
Syntax not understood
378
            var btn = document.createElement('button');
Syntax not understood
379
            btn.classList.add('w3-button','w3-margin-left','w3-right','w3-border','w3-round');
Syntax not understood
380
            btn.style.minWidth = '90px';
Syntax not understood
381
            btn.id = btnId;
Syntax not understood
382
            btn.innerHTML = option.caption;
Syntax not understood
383
            btn.addEventListener('click', option.action=='cancel' ? closeFunc : function() { 
Unknown directive
384
              if(typeof option.action ==='function') { 
Syntax not understood
385
                this.disabled = 'disabled';
Syntax not understood
386
                option.action(this.innerHTML, closeFunc);
Syntax not understood
387
                this.removeAttribute('disabled'); 
Syntax not understood
388
              } 
Syntax not understood
389
            });
Syntax not understood
390
            foot.appendChild(btn);
Syntax not understood
391
          }
Syntax not understood
392
        };
Syntax not understood
393
      }
Syntax not understood
394
      dlg.style.display = 'block';
Syntax not understood
395
      return closeFunc;
Syntax not understood
396
    }
Syntax not understood
397
    portal.dom.HideModal = function(modalId)
Syntax not understood
398
    {
Syntax not understood
399
      var dlg = document.getElementById(modalId);
Syntax not understood
400
      dlg.style.display = 'none';
Syntax not understood
401
      return false;
Syntax not understood
402
    }
Syntax not understood
403
    portal.dom.Alert = function(msg)
Syntax not understood
404
    {
Syntax not understood
405
      return portal.dom.ShowModal({content:msg,modalButtons:[{caption:'OK',action:'cancel'}]});
Unknown directive
406
    }
Syntax not understood
407
    portal.dom.Confirm = function(msg, title, buttons, action)
Syntax not understood
408
    {
Syntax not understood
409
      if(!msg) return;
Syntax not understood
410
      var yesNo = ['Yes','No'], okCancel = ['Ok','Cancel'];
Syntax not understood
411
      if(!title) title = portal.title;
Syntax not understood
412
      var options = {isClosable:false, modalTitle:title, content:msg, modalButtons:[]};
Unknown directive
413
      if(!buttons) buttons = yesNo;
Syntax not understood
414
      if(typeof buttons==='string')
Syntax not understood
415
      {
Syntax not understood
416
        var c = buttons.toUpperCase();
Syntax not understood
417
        if(c=="YESNO" || c=="NOYES") buttons = yesNo;
Syntax not understood
418
        else if(c=="OKCANCEL" || c=="CANCELOK") buttons = okCancel;
Syntax not understood
419
        else buttons = [ buttons ];
Syntax not understood
420
      }
Syntax not understood
421
      if(!action) action = 'cancel';
Syntax not understood
422
      if(Array.isArray(buttons)) {
Syntax not understood
423
        buttons.forEach(function(caption) {
Syntax not understood
424
          var func = (caption=='Yes'||caption=='Ok') ? action : 'cancel';
Unknown directive
425
          options.modalButtons.push({'caption':caption,'action':action/*func*/});
Unknown directive
426
        });
Syntax not understood
427
      }
Syntax not understood
428
      return portal.dom.ShowModal(options);
Syntax not understood
429
    }
Syntax not understood
430
    portal.dom.GetHighestZIndex = function(selector)
Syntax not understood
431
    {
Syntax not understood
432
      var elems = document.querySelectorAll(selector);
Syntax not understood
433
      var highest = 0;
Syntax not understood
434
      for (var i = 0; i < elems.length; i++)
Syntax not understood
435
      {
Syntax not understood
436
        var zindex = document.defaultView.getComputedStyle(elems[i],null).getPropertyValue("z-index");
Syntax not understood
437
        zindex = parseInt(zindex);
Syntax not understood
438
        if ((zindex > highest) && (! isNaN(zindex)))
Syntax not understood
439
        {
Syntax not understood
440
          highest = zindex;
Syntax not understood
441
        }
Syntax not understood
442
      }
Syntax not understood
443
      return highest;
Syntax not understood
444
    }
Syntax not understood
445
    portal.dom.ValueOf = function(inputId) {
Syntax not understood
446
        var elt = document.getElementById(inputId);
Syntax not understood
447
        return elt ? elt.value : null;
Unknown directive
448
    }
Syntax not understood
449
    portal.dom.ExtractJson = function(str) {
Syntax not understood
450
        var firstOpen, firstClose, candidate;
Syntax not understood
451
        firstOpen = str.indexOf('{', firstOpen + 1);
Syntax not understood
452
        do {
Syntax not understood
453
            firstClose = str.lastIndexOf('}');
Syntax not understood
454
            console.log('firstOpen: ' + firstOpen, 'firstClose: ' + firstClose);
Unknown directive
455
            if(firstClose <= firstOpen) {
Syntax not understood
456
                return null;
Syntax not understood
457
            }
Syntax not understood
458
            do {
Syntax not understood
459
                candidate = str.substring(firstOpen, firstClose + 1);
Syntax not understood
460
                console.log('candidate: ' + candidate);
Unknown directive
461
                try {
Syntax not understood
462
                    var res = JSON.parse(candidate);
Syntax not understood
463
                    console.log('...found');
Syntax not understood
464
                    return [res, firstOpen, firstClose + 1];
Syntax not understood
465
                }
Syntax not understood
466
                catch(e) {
Syntax not understood
467
                    console.log('...failed');
Syntax not understood
468
                }
Syntax not understood
469
                firstClose = str.substr(0, firstClose).lastIndexOf('}');
Syntax not understood
470
            } while(firstClose > firstOpen);
Syntax not understood
471
            firstOpen = str.indexOf('{', firstOpen + 1);
Syntax not understood
472
        } while(firstOpen != -1);
Syntax not understood
473
    }
Syntax not understood
474
</script>
Syntax not understood
476
<script>
Syntax not understood
477
    //used to toggle the sidebar
Syntax not understood
478
    function toggleSideBar()
Syntax not understood
479
    {
Syntax not understood
480
      w3.toggleClass('#sidebar-nav','w3-hide');
Syntax not understood
481
      w3.toggleClass('#sidebar-handle','fa-angle-double-right','fa-angle-double-left');
Syntax not understood
482
      portal.ajax.Send(null,null,null,'POST','/api-v2/settings/togglesidebar');
Syntax not understood
483
    }
Syntax not understood
484
    // Used to toggle the menu on smaller screens when clicking on the menu button
Syntax not understood
485
    function openNav() {
Syntax not understood
486
      var x = document.getElementById("navDemo");
Syntax not understood
487
      var c = document.getElementById("main-content-container");
Syntax not understood
488
      var marginTop = 80;
Syntax not understood
489
      var navHeight = 78;
Syntax not understood
490
      if (x.className.indexOf("w3-show") == -1) {
Syntax not understood
491
        x.className += " w3-show";
Syntax not understood
492
        //c.style.marginTop = marginTop + navHeight + "px";
Syntax not understood
493
      } else {
Syntax not understood
494
        x.className = x.className.replace(" w3-show", "");
Syntax not understood
495
        //c.style.marginTop = marginTop + "px";
Syntax not understood
496
      }
Syntax not understood
497
    }
Syntax not understood
498
    //used to filter navigation items
Syntax not understood
499
    function myFilterItems() {
Syntax not understood
500
      var input, filter, ul, li, parent, i;
Syntax not understood
501
      input = document.getElementById("searchNavItemsInput");
Syntax not understood
502
      filter = input.value.toUpperCase();
Syntax not understood
503
      ul = document.getElementById("navItems");
Syntax not understood
504
      li = ul.getElementsByClassName("navItems-item");
Syntax not understood
505
      for (i = 0; i < li.length; i++) {
Syntax not understood
506
        parent = li[i].parentElement.parentElement.parentElement;
Syntax not understood
507
        if (li[i].innerHTML.toUpperCase().indexOf(filter) > -1) {
Syntax not understood
508
          parent.style.display = "";
Syntax not understood
509
        } else {
Syntax not understood
510
          parent.style.display = "none";
Syntax not understood
511
        }
Syntax not understood
512
      }
Syntax not understood
513
    }
Syntax not understood
514
  </script>
Syntax not understood
515
</body>
Syntax not understood
517
</html>
Syntax not understood
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 (9)
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.
Page has successful HTTP status code
Pages with unsuccessful HTTP status codes may not be indexed properly. Learn more.
Links have descriptive text
Descriptive link text helps search engines understand your content. 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.
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 uses legible font sizes 100% 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
Legible text
100.00%
≥ 12px
 
 
  
   Document avoids plugins   
     
 
  
Search engines can't index plugin content, and many devices restrict plugins or don't support them. Learn more.
 
 
 
 
  
   Tap targets are sized appropriately 100% 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.
 
 
 
  
 
 Not applicable (1)   
      
  
 
  
   Document has a valid rel=canonical   
     
 
  
Canonical links suggest which URL to show in search results. Learn more.
 
 
 
 
                                  
Progressive Web App
 
 
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
 
 
 
 
  
   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.