https://fukashere.edu.ng/
32
Performance
94
Accessibility
80
Best Practices
79
SEO
Progressive Web App
0–49 50–89 90–100
Metrics
First Contentful Paint
12.4 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.
Speed Index
24.2 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
Largest Contentful Paint
20.1 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more
Time to Interactive
36.0 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Total Blocking Time
520 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.052
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
Use HTTP/2
17.29 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
…css/styles.css?ver=5.5.4
(fukashere.edu.ng)
http/1.1
http/1.1
http/1.1
http/1.1
http/1.1
http/1.1
http/1.1
http/1.1
http/1.1
http/1.1
http/1.1
http/1.1
http/1.1
http/1.1
http/1.1
http/1.1
http/1.1
http/1.1
http/1.1
http/1.1
http/1.1
http/1.1
http/1.1
http/1.1
http/1.1
http/1.1
http/1.1
http/1.1
http/1.1
http/1.1
http/1.1
http/1.1
http/1.1
…js/index.js?ver=5.5.4
(fukashere.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
…07/ENTRANCE.jpg
(fukashere.edu.ng)
http/1.1
…03/FUK.jpg
(fukashere.edu.ng)
http/1.1
…07/ICT-FACILITIES.jpg
(fukashere.edu.ng)
http/1.1
…03/DSC8651-scaled.jpg
(fukashere.edu.ng)
http/1.1
…03/DSC8544-scaled.jpg
(fukashere.edu.ng)
http/1.1
…08/Picture1-1.jpg
(fukashere.edu.ng)
http/1.1
http/1.1
…08/Picture2.jpg
(fukashere.edu.ng)
http/1.1
…03/head2.jpg
(fukashere.edu.ng)
http/1.1
http/1.1
http/1.1
http/1.1
http/1.1
http/1.1
…02/Kashere-VC.jpeg
(fukashere.edu.ng)
http/1.1
…01/cd205c7….jpg
(fukashere.edu.ng)
http/1.1
…01/52gqbTh0c….jpeg
(fukashere.edu.ng)
http/1.1
http/1.1
http/1.1
…01/52gqbTh0c….jpeg
(fukashere.edu.ng)
http/1.1
…04/BG.png
(fukashere.edu.ng)
http/1.1
http/1.1
…08/LOGO-WITH….png
(fukashere.edu.ng)
http/1.1
Defer offscreen images
9.84 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
…03/DSC8544-scaled.jpg
(fukashere.edu.ng)
503.5 KiB
503.5 KiB
390.0 KiB
390.0 KiB
…03/DSC8651-scaled.jpg
(fukashere.edu.ng)
369.6 KiB
369.6 KiB
…08/Picture1-1.jpg
(fukashere.edu.ng)
356.8 KiB
356.8 KiB
…08/Picture2.jpg
(fukashere.edu.ng)
306.6 KiB
306.6 KiB
Serve images in next-gen formats
9.55 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
390.0 KiB
271.9 KiB
…08/Picture2.jpg
(fukashere.edu.ng)
306.6 KiB
261.9 KiB
…03/DSC8544-scaled.jpg
(fukashere.edu.ng)
503.5 KiB
218.0 KiB
…03/head2.jpg
(fukashere.edu.ng)
615.5 KiB
216.2 KiB
…03/DSC8651-scaled.jpg
(fukashere.edu.ng)
369.6 KiB
174.8 KiB
…03/FUK.jpg
(fukashere.edu.ng)
368.6 KiB
162.1 KiB
…08/Picture1-1.jpg
(fukashere.edu.ng)
356.8 KiB
155.7 KiB
142.8 KiB
132.1 KiB
…08/LOGO-WITH….png
(fukashere.edu.ng)
38.9 KiB
33.3 KiB
…01/cd205c7….jpg
(fukashere.edu.ng)
69.8 KiB
28.8 KiB
…07/ENTRANCE.jpg
(fukashere.edu.ng)
98.6 KiB
28.2 KiB
…07/ICT-FACILITIES.jpg
(fukashere.edu.ng)
75.6 KiB
26.6 KiB
…04/BG.png
(fukashere.edu.ng)
35.3 KiB
24.8 KiB
44.9 KiB
23.9 KiB
…02/Kashere-VC.jpeg
(fukashere.edu.ng)
108.2 KiB
21.1 KiB
…01/52gqbTh0c….jpeg
(fukashere.edu.ng)
31.4 KiB
15.5 KiB
59.8 KiB
14.0 KiB
Enable text compression
8.64 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
205.9 KiB
183.3 KiB
204.7 KiB
178.6 KiB
134.0 KiB
116.9 KiB
151.9 KiB
115.6 KiB
135.9 KiB
101.2 KiB
85.9 KiB
69.3 KiB
77.4 KiB
66.7 KiB
73.9 KiB
66.4 KiB
70.1 KiB
58.4 KiB
87.4 KiB
57.2 KiB
60.2 KiB
56.0 KiB
58.0 KiB
45.4 KiB
56.6 KiB
44.3 KiB
55.3 KiB
38.4 KiB
33.4 KiB
30.2 KiB
42.0 KiB
29.4 KiB
36.0 KiB
25.5 KiB
32.9 KiB
24.6 KiB
30.1 KiB
23.2 KiB
57.6 KiB
22.7 KiB
26.1 KiB
21.9 KiB
24.2 KiB
19.1 KiB
24.6 KiB
17.6 KiB
18.0 KiB
15.5 KiB
18.6 KiB
14.8 KiB
16.6 KiB
14.8 KiB
20.2 KiB
13.5 KiB
17.8 KiB
12.9 KiB
13.5 KiB
12.6 KiB
18.8 KiB
12.0 KiB
13.3 KiB
11.7 KiB
14.7 KiB
10.6 KiB
13.9 KiB
9.4 KiB
10.9 KiB
9.3 KiB
11.9 KiB
9.0 KiB
11.0 KiB
8.5 KiB
10.2 KiB
7.5 KiB
10.4 KiB
7.1 KiB
11.0 KiB
6.9 KiB
…js/index.js?ver=5.5.4
(fukashere.edu.ng)
9.5 KiB
6.3 KiB
6.4 KiB
4.6 KiB
6.3 KiB
4.0 KiB
5.5 KiB
3.7 KiB
5.4 KiB
3.0 KiB
4.1 KiB
3.0 KiB
5.0 KiB
2.8 KiB
4.8 KiB
2.7 KiB
…css/styles.css?ver=5.5.4
(fukashere.edu.ng)
2.7 KiB
1.7 KiB
2.2 KiB
1.6 KiB
2.5 KiB
1.4 KiB
Eliminate render-blocking resources
8.13 s
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.FCPLCP
WordPressThere are a number of WordPress plugins that can help you inline critical assets or defer less important resources. Beware that optimizations provided by these plugins may break features of your theme or plugins, so you will likely need to make code changes.
URL
Transfer Size
Potential Savings
70.3 KiB
4,440 ms
0.8 KiB
970 ms
57.9 KiB
3,690 ms
1.0 KiB
680 ms
77.6 KiB
4,740 ms
11.2 KiB
1,280 ms
4.3 KiB
980 ms
…css/styles.css?ver=5.5.4
(fukashere.edu.ng)
2.9 KiB
830 ms
1.1 KiB
680 ms
1.2 KiB
680 ms
1.0 KiB
680 ms
18.8 KiB
1,580 ms
13.7 KiB
1,280 ms
134.3 KiB
7,750 ms
1.2 KiB
680 ms
206.1 KiB
9,410 ms
58.2 KiB
3,690 ms
26.3 KiB
2,040 ms
60.4 KiB
3,840 ms
33.7 KiB
2,340 ms
74.1 KiB
4,590 ms
16.8 KiB
1,430 ms
24.4 KiB
1,880 ms
30.4 KiB
2,190 ms
13.6 KiB
1,280 ms
11.2 KiB
1,130 ms
5.2 KiB
830 ms
/css?family=…
(fonts.googleapis.com)
2.7 KiB
150 ms
56.8 KiB
3,540 ms
0.9 KiB
680 ms
0.9 KiB
680 ms
0.9 KiB
680 ms
86.1 KiB
4,290 ms
18.3 KiB
1,580 ms
87.7 KiB
4,290 ms
11.2 KiB
1,130 ms
15.0 KiB
1,430 ms
Reduce unused JavaScript
6.25 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
…en_US/base.js
(www.youtube.com)
536.0 KiB
387.5 KiB
152.1 KiB
94.1 KiB
136.1 KiB
72.3 KiB
/en_US/sdk.js?hash=05812fa…
(connect.facebook.net)
81.6 KiB
56.2 KiB
84.9 KiB
42.3 KiB
47.3 KiB
34.0 KiB
87.7 KiB
32.7 KiB
42.3 KiB
31.6 KiB
33.1 KiB
29.3 KiB
55.6 KiB
25.8 KiB
Reduce unused CSS
5.48 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
206.1 KiB
193.1 KiB
134.3 KiB
118.7 KiB
86.1 KiB
85.4 KiB
77.6 KiB
77.2 KiB
74.1 KiB
74.1 KiB
70.3 KiB
66.1 KiB
58.2 KiB
57.5 KiB
57.9 KiB
57.0 KiB
56.8 KiB
56.2 KiB
60.4 KiB
55.4 KiB
46.7 KiB
44.5 KiB
30.4 KiB
29.9 KiB
26.3 KiB
26.3 KiB
24.4 KiB
24.4 KiB
html{font-size:93.75%;} ...
26.5 KiB
23.5 KiB
18.8 KiB
18.5 KiB
18.3 KiB
18.2 KiB
@-webkit-keyframes ha_fadeIn{0%{opacity:0} ...
18.2 KiB
18.0 KiB
13.7 KiB
13.6 KiB
11.2 KiB
11.2 KiB
Efficiently encode images
1.2 s
Optimized images load faster and consume less cellular data. Learn more.
WordPressConsider using an image optimization WordPress plugin that compresses your images while retaining quality.
URL
Resource Size
Potential Savings
…08/Picture2.jpg
(fukashere.edu.ng)
306.6 KiB
194.1 KiB
390.0 KiB
74.7 KiB
Reduce initial server response time
0.99 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
1,090 ms
Properly size images
0.45 s
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.
URL
Resource Size
Potential Savings
…02/Kashere-VC.jpeg
(fukashere.edu.ng)
108.2 KiB
66.3 KiB
15.3 KiB
12.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
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
33.1 KiB
7.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 84 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.
URL
Cache TTL
Transfer Size
…03/head2.jpg
(fukashere.edu.ng)
None
616 KiB
…03/DSC8544-scaled.jpg
(fukashere.edu.ng)
None
504 KiB
None
390 KiB
…03/DSC8651-scaled.jpg
(fukashere.edu.ng)
None
370 KiB
…03/FUK.jpg
(fukashere.edu.ng)
None
369 KiB
…08/Picture1-1.jpg
(fukashere.edu.ng)
None
357 KiB
…08/Picture2.jpg
(fukashere.edu.ng)
None
307 KiB
None
206 KiB
None
152 KiB
None
143 KiB
None
136 KiB
None
134 KiB
…02/Kashere-VC.jpeg
(fukashere.edu.ng)
None
108 KiB
…07/ENTRANCE.jpg
(fukashere.edu.ng)
None
99 KiB
None
90 KiB
None
88 KiB
None
86 KiB
None
78 KiB
None
77 KiB
…07/ICT-FACILITIES.jpg
(fukashere.edu.ng)
None
76 KiB
None
75 KiB
None
74 KiB
None
70 KiB
…01/cd205c7….jpg
(fukashere.edu.ng)
None
70 KiB
None
60 KiB
None
60 KiB
None
58 KiB
None
58 KiB
None
57 KiB
None
56 KiB
None
42 KiB
…08/LOGO-WITH….png
(fukashere.edu.ng)
None
39 KiB
None
36 KiB
…04/BG.png
(fukashere.edu.ng)
None
36 KiB
None
34 KiB
None
33 KiB
…01/52gqbTh0c….jpeg
(fukashere.edu.ng)
None
32 KiB
None
30 KiB
None
26 KiB
None
25 KiB
None
24 KiB
None
20 KiB
None
19 KiB
None
19 KiB
None
18 KiB
None
18 KiB
None
17 KiB
None
16 KiB
None
15 KiB
…01/52gqbTh0c….jpeg
(fukashere.edu.ng)
None
15 KiB
None
14 KiB
None
14 KiB
None
14 KiB
None
14 KiB
None
13 KiB
None
12 KiB
None
11 KiB
None
11 KiB
None
11 KiB
None
11 KiB
None
10 KiB
…js/index.js?ver=5.5.4
(fukashere.edu.ng)
None
10 KiB
None
7 KiB
None
7 KiB
None
6 KiB
None
6 KiB
None
5 KiB
None
5 KiB
None
4 KiB
…css/styles.css?ver=5.5.4
(fukashere.edu.ng)
None
3 KiB
None
3 KiB
None
2 KiB
None
1 KiB
None
1 KiB
None
1 KiB
None
1 KiB
None
1 KiB
None
1 KiB
None
1 KiB
None
1 KiB
/instream/ad_status.js
(static.doubleclick.net)
15 m
1 KiB
/en_US/sdk.js
(connect.facebook.net)
20 m
2 KiB
2 h
45 KiB
1 d
3 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
…v29/KFOlCnqEu….woff2
(fonts.gstatic.com)
910 ms
…v17/RrQfboBx-….woff2
(fonts.gstatic.com)
1,140 ms
670 ms
…v15/xfu_0WLxV….woff2
(fonts.gstatic.com)
1,190 ms
…v22/BngMUXZYT….woff2
(fonts.gstatic.com)
1,540 ms
…v12/MwQ5bhbm2….woff2
(fonts.gstatic.com)
1,320 ms
…v29/KFOmCnqEu….woff2
(fonts.gstatic.com)
940 ms
…v29/KFOkCnqEu….woff2
(fonts.gstatic.com)
1,230 ms
…v29/KFOlCnqEu….woff2
(fonts.gstatic.com)
1,100 ms
…v9/1cXxaUPXB….woff2
(fonts.gstatic.com)
1,520 ms
…v21/WwkbxPW1E….woff2
(fonts.gstatic.com)
1,360 ms
…v23/JTUSjIg1_….woff2
(fonts.gstatic.com)
330 ms
…v18/KFOmCnqEu….woff2
(fonts.gstatic.com)
190 ms
Reduce the impact of third-party code Third-party code blocked the main thread for 370 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
800 KiB
368 ms
…en_US/base.js
(www.youtube.com)
536 KiB
188 ms
85 KiB
180 ms
47 KiB
0 ms
47 KiB
0 ms
45 KiB
0 ms
179 KiB
0 ms
…v22/BngMUXZYT….woff2
(fonts.gstatic.com)
32 KiB
0 ms
…v23/JTUSjIg1_….woff2
(fonts.gstatic.com)
30 KiB
0 ms
…v21/WwkbxPW1E….woff2
(fonts.gstatic.com)
14 KiB
0 ms
…v15/xfu_0WLxV….woff2
(fonts.gstatic.com)
13 KiB
0 ms
…v29/KFOkCnqEu….woff2
(fonts.gstatic.com)
12 KiB
0 ms
Other resources
77 KiB
0 ms
89 KiB
0 ms
/en_US/sdk.js?hash=05812fa…
(connect.facebook.net)
82 KiB
0 ms
Other resources
7 KiB
0 ms
14 KiB
0 ms
…th/Z_dKjKIC5….js
(www.google.com)
14 KiB
0 ms
3 KiB
0 ms
1 KiB
0 ms
Some third-party resources can be lazy loaded with a facade 1 facade alternative available
Some third-party embeds can be lazy loaded. Consider replacing them with a facade until they are required. Learn more.TBT
Product
Transfer Size
Main-Thread Blocking Time
YouTube Embedded Player (Video)
800 KiB
368 ms
…en_US/base.js
(www.youtube.com)
536 KiB
188 ms
85 KiB
180 ms
47 KiB
0 ms
47 KiB
0 ms
45 KiB
0 ms
Other resources
40 KiB
0 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
…en_US/base.js:7137:673
(www.youtube.com)
Avoid enormous network payloads Total size was 7,031 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
…03/head2.jpg
(fukashere.edu.ng)
615.7 KiB
…en_US/base.js
(www.youtube.com)
536.0 KiB
…03/DSC8544-scaled.jpg
(fukashere.edu.ng)
503.8 KiB
390.2 KiB
…03/DSC8651-scaled.jpg
(fukashere.edu.ng)
369.8 KiB
…03/FUK.jpg
(fukashere.edu.ng)
368.8 KiB
…08/Picture1-1.jpg
(fukashere.edu.ng)
357.0 KiB
…08/Picture2.jpg
(fukashere.edu.ng)
306.8 KiB
206.1 KiB
205.5 KiB
Minimize main-thread work 6.4 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn moreTBT
Category
Time Spent
Script Evaluation
1,954 ms
Other
1,799 ms
Style & Layout
1,590 ms
Rendering
522 ms
Parse HTML & CSS
359 ms
Script Parsing & Compilation
107 ms
Garbage Collection
36 ms
Avoid an excessive DOM size 1,548 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn more.TBT
Statistic
Element
Value
Total DOM Elements
1,548
Maximum DOM Depth
ul#menu-1-4b03b7d > li.menu-item > a.elementor-item > i._mi
<i class="_mi _before dashicons dashicons-media-document" aria-hidden="true">
30
Maximum Child Elements
body.home > b
<b>
30
Reduce JavaScript execution time 1.8 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
2,235 ms
168 ms
7 ms
Unattributable
1,253 ms
9 ms
0 ms
703 ms
546 ms
6 ms
539 ms
435 ms
7 ms
…en_US/base.js
(www.youtube.com)
458 ms
360 ms
43 ms
209 ms
39 ms
3 ms
/en_US/sdk.js?hash=05812fa…
(connect.facebook.net)
116 ms
85 ms
7 ms
90 ms
55 ms
6 ms
87 ms
4 ms
0 ms
58 ms
51 ms
3 ms
Avoid chaining critical requests 68 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: 7,550 ms
Initial Navigation
- 1,560 ms, 70.30 KiB
…v17/RrQfboBx-….woff2
(fonts.gstatic.com)
- 1,140 ms, 8.14 KiB
- 150 ms, 30.98 KiB
- 900 ms, 1.03 KiB
- 1,340 ms, 77.61 KiB
- 840 ms, 11.23 KiB
- 990 ms, 4.32 KiB
…css/styles.css?ver=5.5.4
(fukashere.edu.ng)
- 1,070 ms, 2.90 KiB
- 1,070 ms, 1.06 KiB
- 1,200 ms, 1.19 KiB
- 1,270 ms, 0.99 KiB
- 670 ms, 90.29 KiB
- 1,280 ms, 13.72 KiB
- 1,710 ms, 134.27 KiB
- 1,370 ms, 1.23 KiB
- 2,370 ms, 206.14 KiB
- 430 ms, 76.60 KiB
- 660 ms, 75.20 KiB
- 350 ms, 13.20 KiB
- 1,380 ms, 26.31 KiB
- 1,830 ms, 60.42 KiB
- 1,600 ms, 33.68 KiB
- 1,830 ms, 74.15 KiB
- 1,830 ms, 16.82 KiB
- 1,840 ms, 24.43 KiB
- 1,940 ms, 30.37 KiB
- 2,090 ms, 13.55 KiB
- 2,080 ms, 11.18 KiB
- 2,080 ms, 5.21 KiB
/css?family=…
(fonts.googleapis.com)
…v29/KFOlCnqEu….woff2
(fonts.gstatic.com)
- 910 ms, 11.41 KiB
…v15/xfu_0WLxV….woff2
(fonts.gstatic.com)
- 1,190 ms, 13.31 KiB
…v22/BngMUXZYT….woff2
(fonts.gstatic.com)
- 1,540 ms, 32.15 KiB
…v12/MwQ5bhbm2….woff2
(fonts.gstatic.com)
- 1,320 ms, 9.47 KiB
…v29/KFOmCnqEu….woff2
(fonts.gstatic.com)
- 940 ms, 10.89 KiB
…v29/KFOkCnqEu….woff2
(fonts.gstatic.com)
- 1,230 ms, 12.47 KiB
…v29/KFOlCnqEu….woff2
(fonts.gstatic.com)
- 1,100 ms, 10.90 KiB
…v9/1cXxaUPXB….woff2
(fonts.gstatic.com)
- 1,520 ms, 11.84 KiB
…v21/WwkbxPW1E….woff2
(fonts.gstatic.com)
- 1,360 ms, 14.08 KiB
…v23/JTUSjIg1_….woff2
(fonts.gstatic.com)
- 330 ms, 30.33 KiB
- 2,290 ms, 56.79 KiB
- 2,150 ms, 0.89 KiB
- 2,290 ms, 0.89 KiB
- 2,300 ms, 0.90 KiB
- 2,510 ms, 86.12 KiB
- 2,940 ms, 87.67 KiB
- 2,510 ms, 11.21 KiB
- 2,570 ms, 14.95 KiB
- 1,900 ms, 18.27 KiB
- 2,130 ms, 10.41 KiB
- 2,130 ms, 6.59 KiB
- 2,270 ms, 19.06 KiB
…js/index.js?ver=5.5.4
(fukashere.edu.ng)
- 2,280 ms, 9.74 KiB
- 2,340 ms, 33.13 KiB
- 2,230 ms, 24.86 KiB
- 2,220 ms, 5.75 KiB
- 2,360 ms, 5.64 KiB
- 2,370 ms, 5.04 KiB
- 2,430 ms, 14.15 KiB
- 2,430 ms, 6.69 KiB
- 2,690 ms, 55.55 KiB
- 2,570 ms, 12.16 KiB
- 2,680 ms, 20.44 KiB
- 3,290 ms, 136.14 KiB
- 2,680 ms, 2.77 KiB
- 2,680 ms, 10.68 KiB
- 2,800 ms, 36.27 KiB
- 3,730 ms, 152.15 KiB
- 3,180 ms, 42.27 KiB
User Timing marks and measures 2 user timings
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more.
Name
Type
Start Time
Duration
mark_pe
Mark
10,560.83 ms
mark_fs
Mark
10,604.92 ms
Keep request counts low and transfer sizes small 118 requests • 7,031 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
118
7,030.8 KiB
Image
23
3,667.6 KiB
Script
36
1,525.9 KiB
Stylesheet
35
1,171.1 KiB
Font
16
430.8 KiB
Document
3
231.6 KiB
Other
5
3.9 KiB
Media
0
0.0 KiB
Third-party
37
1,086.6 KiB
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport. Learn MoreLCP
Element
NOTICE FOR THE RELEASE OF SECOND BATCH 2021/2022 ADMISSION LIST Click Button Be…
<div class="elementor-column-wrap elementor-element-populated">
Avoid large layout shifts 5 elements found
These DOM elements contribute most to the CLS of the page.CLS
Element
CLS Contribution
Prof. Umaru Alhaji Pate Vice-Chancellor, Federal University of Kashere
<div class="elementor-widget-wrap">
0.019
Enterprises
<a href="https://fukashere.edu.ng/enterprises/" class="elementor-item menu-link has-submenu" id="sm-16445168139620935-9" aria-haspopup="true" aria-controls="sm-16445168139620935-10" aria-expanded="false">
0.007
TETFund Interventions
<a href="https://fukashere.edu.ng/tetfund-interventions/" class="elementor-item menu-link has-submenu" id="sm-16445168139620935-1" aria-haspopup="true" aria-controls="sm-16445168139620935-2" aria-expanded="false">
0.007
Giving/Donations
<a href="https://fukashere.edu.ng/giving-donation/" class="elementor-item menu-link has-submenu" id="sm-16445168139620935-7" aria-haspopup="true" aria-controls="sm-16445168139620935-8" aria-expanded="false">
0.006
Visit TETFund
<a target="_blank" rel="noopener" href="https://www.tetfund.gov.ng/" class="elementor-item menu-link">
0.005
Avoid long main-thread tasks 17 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn moreTBT
URL
Start Time
Duration
2,180 ms
323 ms
…en_US/base.js
(www.youtube.com)
43,625 ms
252 ms
20,704 ms
235 ms
2,036 ms
144 ms
43,877 ms
141 ms
…en_US/base.js
(www.youtube.com)
45,278 ms
117 ms
13,189 ms
114 ms
20,616 ms
88 ms
20,946 ms
70 ms
14,615 ms
67 ms
Unattributable
2,503 ms
64 ms
2,567 ms
61 ms
12,508 ms
58 ms
2,628 ms
58 ms
2,760 ms
58 ms
19,429 ms
56 ms
44,018 ms
51 ms
Avoid non-composited animations 1 animated element found
Animations which are not composited can be janky and increase CLS. Learn moreCLS
Element
Name
Go to slide 1
<div class="swiper-pagination swiper-pagination-clickable swiper-pagination-bullets">
Unsupported CSS Property: color
color
Passed audits (11)
Minify CSS Potential savings of 11 KiB
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
74.1 KiB
11.0 KiB
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 Potential savings of 0 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers. Learn MoreTBT
URL
Potential Savings
0.2 KiB
@babel/plugin-transform-classes
Preload Largest Contentful Paint image
Preload the image used by the LCP element in order to improve your LCP time. Learn more.LCP
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
NOTICE FOR THE RELEASE OF SECOND BATCH 2021/2022 ADMISSION LIST Click Button Be…
<div class="elementor-column-wrap elementor-element-populated">
Avoids document.write()
For users on slow connections, external scripts dynamically injected via `document.write()` can delay page load by tens of seconds. Learn more.
Image elements have explicit width and height
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn moreCLS
Has a <meta name="viewport"> tag with width or initial-scale
A `<meta name="viewport">` not only optimizes your app for mobile screen sizes, but also prevents a 300 millisecond delay to user input. Learn more.TBT
These checks highlight opportunities to improve the accessibility of your web app. Only a subset of accessibility issues can be automatically detected so manual testing is also encouraged.
ContrastThese are opportunities to improve the legibility of your content.
Background and foreground colors do not have a sufficient contrast ratio.
Low-contrast text is difficult or impossible for many users to read. Learn more.
Failing Elements
Read More
<a href="https://fukashere.edu.ng/vision-mission/">
FUK is an institution of higher learning that is committed to excellence and in…
<p>
Live on Twitter
<span class="elementor-button-text">
We Are Social
<p>
Copyright © 2022 Federal University of Kashere | Powered by OAYASTECH | Sponsor…
<span>
OAYASTECH
<b>
TETFund
<b>
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
Prof. Umaru Alhaji Pate
<h3 class="elementor-image-box-title">
Names and labelsThese are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Additional items to manually check (10) These items address areas which an automated testing tool cannot cover. Learn more in our guide on conducting an accessibility review.
The page has a logical tab order
Tabbing through the page follows the visual layout. Users cannot focus elements that are offscreen. Learn more.
Interactive controls are keyboard focusable
Custom interactive controls are keyboard focusable and display a focus indicator. Learn more.
Interactive elements indicate their purpose and state
Interactive elements, such as links and buttons, should indicate their state and be distinguishable from non-interactive elements. Learn more.
The user's focus is directed to new content added to the page
If new content, such as a dialog, is added to the page, the user's focus is directed to it. Learn more.
User focus is not accidentally trapped in a region
A user can tab into and out of any control or region without accidentally trapping their focus. Learn more.
Custom controls have associated labels
Custom interactive controls have associated labels, provided by aria-label or aria-labelledby. Learn more.
Custom controls have ARIA roles
Custom interactive controls have appropriate ARIA roles. Learn more.
Visual order on the page follows DOM order
DOM order matches the visual order, improving navigation for assistive technology. Learn more.
Offscreen content is hidden from assistive technology
Offscreen content is hidden with display: none or aria-hidden=true. Learn more.
HTML5 landmark elements are used to improve navigation
Landmark elements (<main>, <nav>, etc.) are used to improve the keyboard navigation of the page for assistive technology. Learn more.
Passed audits (19)
[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"] is not present on the document <body>
Assistive technologies, like screen readers, work inconsistently when `aria-hidden="true"` is set on the document `<body>`. Learn more.
[aria-hidden="true"] elements do not contain focusable descendents
Focusable descendents within an `[aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn more.
[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.
[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.
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.
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.
<frame> or <iframe> elements have a title
Screen reader users rely on frame titles to describe the contents of frames. Learn more.
<html> element has a [lang] attribute
If a page doesn't specify a lang attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more.
<html> element has a valid value for its [lang] attribute
Specifying a valid BCP 47 language helps screen readers announce text properly. Learn more.
Image elements have [alt] attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more.
Lists contain only <li> elements and script supporting elements (<script> and <template>).
Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more.
List items (<li>) are contained within <ul> or <ol> parent elements
Screen readers require list items (`<li>`) to be contained within a parent `<ul>` or `<ol>` to be announced properly. Learn more.
[user-scalable="no"] is not used in the <meta name="viewport"> element and the [maximum-scale] attribute is not less than 5.
Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more.
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.
Not applicable (22)
[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 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.
Buttons have an accessible name
When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn more.
<dl>'s contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.
When definition lists are not properly marked up, screen readers may produce confusing or inaccurate output. Learn more.
Definition list items are wrapped in <dl> elements
Definition list items (`<dt>` and `<dd>`) must be wrapped in a parent `<dl>` element to ensure that screen readers can properly announce them. Learn more.
[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.
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.
<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.
Cells in a <table> element that use the [headers] attribute refer to table cells within the same table.
Screen readers have features to make navigating tables easier. Ensuring `<td>` cells using the `[headers]` attribute only refer to other cells in the same table may improve the experience for screen reader users. Learn more.
<th> elements and elements with [role="columnheader"/"rowheader"] have data cells they describe.
Screen readers have features to make navigating tables easier. Ensuring table headers always refer to some set of cells may improve the experience for screen reader users. Learn more.
[lang] attributes have a valid value
Specifying a valid BCP 47 language on elements helps ensure that text is pronounced correctly by a screen reader. Learn more.
<video> elements contain a <track> element with [kind="captions"]
When a video provides a caption it is easier for deaf and hearing impaired users to access its information. Learn more.
Trust and Safety
Links to cross-origin destinations are unsafe
Warnings:
  • Unable to determine the destination for anchor (<a class="elementor-icon elementor-social-icon elementor-social-icon-instagram eleme…" target="_blank">). If not used as a hyperlink, consider removing target=_blank.
  • Unable to determine the destination for anchor (<a class="elementor-icon elementor-social-icon elementor-social-icon-youtube element…" target="_blank">). If not used as a hyperlink, consider removing target=_blank.
Add `rel="noopener"` or `rel="noreferrer"` to any external links to improve performance and prevent security vulnerabilities. Learn more.
Failing Anchors
HR
<a href="https://fuk.greenhr.ng/" target="_blank" rel="nofollow" class="elementor-button-link elementor-button elementor-size-sm" role="button">
Portal
<a href="http://admissions.flexisaf.com:8080/fuk" target="_blank" rel="nofollow" class="elementor-button-link elementor-button elementor-size-sm" role="button">
Facebook
<a class="elementor-icon elementor-social-icon elementor-social-icon-facebook elemen…" href="https://web.facebook.com/Federal-University-of-Kashere-201529049907523/?_r…" target="_blank">
Twitter
<a class="elementor-icon elementor-social-icon elementor-social-icon-twitter element…" href="https://twitter.com/Fukashere" target="_blank">
Instagram
<a class="elementor-icon elementor-social-icon elementor-social-icon-instagram eleme…" target="_blank">
Youtube
<a class="elementor-icon elementor-social-icon elementor-social-icon-youtube element…" target="_blank">
OAYASTECH
<a href="http://www.oayastech.com" target="_blank">
TETFund
<a href="https://www.tetfund.gov.ng" target="_blank">
Ensure CSP is effective against XSS attacks
A strong Content Security Policy (CSP) significantly reduces the risk of cross-site scripting (XSS) attacks. Learn more
Description
Directive
Severity
No CSP found in enforcement mode
High
General
Detected JavaScript libraries
All front-end JavaScript libraries detected on the page. Learn more.
Name
Version
jQuery
3.6.0
jQuery UI
1.13.0
WordPress
5.9
core-js
core-js-global@3.19.1; core-js-pure@2.6.11; core-js-global@2.6.11
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
Refused to display 'https://m.facebook.com/' in a frame because it set 'X-Frame-Options' to 'deny'.
Issues were logged in the Issues panel in Chrome Devtools
Issues logged to the `Issues` panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.
Issue type
SameSite cookie
/iframe_api
(www.youtube.com)
Passed audits (13)
Uses HTTPS
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more.
Avoids requesting the geolocation permission on page load
Users are mistrustful of or confused by sites that request their location without context. Consider tying the request to a user action instead. Learn more.
Avoids requesting the notification permission on page load
Users are mistrustful of or confused by sites that request to send notifications without context. Consider tying the request to user gestures instead. Learn more.
Avoids front-end JavaScript libraries with known security vulnerabilities
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers. Learn more.
Allows users to paste into password fields
Preventing password pasting undermines good security policy. Learn more.
Displays images with correct aspect ratio
Image display dimensions should match natural aspect ratio. Learn more.
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.
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.
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
Instagram
<a class="elementor-icon elementor-social-icon elementor-social-icon-instagram eleme…" target="_blank">
Youtube
<a class="elementor-icon elementor-social-icon elementor-social-icon-youtube element…" target="_blank">
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 (11)
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.
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 93.19% 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
.elementor-52 .elementor-element.elementor-element-78f24d1 .elementor-slide-description
5.37%
9px
.elementor-77 .elementor-element.elementor-element-ad6e383 .elementor-nav-menu .elementor-item
0.60%
10px
.elementor-77 .elementor-element.elementor-element-ac8d032 .elementor-heading-title
0.26%
9px
.elementor-483 .elementor-element.elementor-element-0f7e03d .elementor-image-box-description
0.26%
11px
.elementor-widget .elementor-icon-list-icon i
0.08%
10px
.fa
0.06%
10px
a, abbr, acronym, address, applet, big, blockquote, body, caption, cite, code, dd, del, dfn, div, dl, dt, em, fieldset, font, form, h1, h2, h3, h4, h5, h6, html, iframe, ins, kbd, label, legend, li, object, ol, p, pre, q, s, samp, small, span, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, ul, var
0.01%
8px
Add'l illegible text
0.17%
< 12px
Legible text
93.19%
≥ 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.
These checks validate the aspects of a Progressive Web App. Learn more.
Installable
Web app manifest or service worker do not meet the installability requirements 1 reason
Service worker is the technology that enables your app to use many Progressive Web App features, such as offline, add to homescreen, and push notifications. With proper service worker and manifest implementations, browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement. Learn more.
Failure reason
No manifest was fetched
PWA Optimized
Does not register a service worker that controls page and start_url
The service worker is the technology that enables your app to use many Progressive Web App features, such as offline, add to homescreen, and push notifications. Learn more.
Redirects HTTP traffic to HTTPS
If you've already set up HTTPS, make sure that you redirect all HTTP traffic to HTTPS in order to enable secure web features for all your users. Learn more.
Is not configured for a custom splash screen
Failures: No manifest was fetched.
A themed splash screen ensures a high-quality experience when users launch your app from their homescreens. Learn more.
Does not set a theme color for the address bar.
Failures: No manifest was fetched, No `<meta name="theme-color">` tag found.
The browser address bar can be themed to match your site. Learn more.
Content is sized correctly for the viewport
If the width of your app's content doesn't match the width of the viewport, your app might not be optimized for mobile screens. Learn more.
Has a <meta name="viewport"> tag with width or initial-scale
A `<meta name="viewport">` not only optimizes your app for mobile screen sizes, but also prevents a 300 millisecond delay to user input. Learn more.TBT
Provides a valid apple-touch-icon
For ideal appearance on iOS when users add a progressive web app to the home screen, define an `apple-touch-icon`. It must point to a non-transparent 192px (or 180px) square PNG. Learn More.
Manifest doesn't have a maskable icon
No manifest was fetched
A maskable icon ensures that the image fills the entire shape without being letterboxed when installing the app on a device. Learn more.
Additional items to manually check (3) These checks are required by the baseline PWA Checklist but are not automatically checked by Lighthouse. They do not affect your score but it's important that you verify them manually.
Site works cross-browser
To reach the most number of users, sites should work across every major browser. Learn more.
Page transitions don't feel like they block on the network
Transitions should feel snappy as you tap around, even on a slow network. This experience is key to a user's perception of performance. Learn more.
Each page has a URL
Ensure individual pages are deep linkable via URL and that URLs are unique for the purpose of shareability on social media. Learn more.