10.5 sec in total
263 ms
2.5 sec
7.8 sec
Welcome to life.guardian.ng homepage info - get ready to check Life Guardian best content for Nigeria right away, or after learning these important things about life.guardian.ng
The Latest news in Nigeria and world news. The Guardian Nigeria Newspaper brings you the latest headlines, opinions, political news, business reports and international news.
Visit life.guardian.ngWe analyzed Life.guardian.ng page load time and found that the first response time was 263 ms and then it took 10.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
life.guardian.ng performance score
name
value
score
weighting
Value3.4 s
36/100
10%
Value12.6 s
0/100
25%
Value46.0 s
0/100
10%
Value85,690 ms
0/100
30%
Value0.083
94/100
15%
Value112.5 s
0/100
10%
263 ms
118 ms
263 ms
50 ms
113 ms
Our browser made a total of 91 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Life.guardian.ng, 60% (55 requests) were made to Guardian.ng and 5% (5 requests) were made to Static1.dmcdn.net. The less responsive or slowest element that took the longest time to load (680 ms) relates to the external source Dailymotion.com.
Page size can be reduced by 321.1 kB (54%)
595.3 kB
274.2 kB
In fact, the total size of Life.guardian.ng main page is 595.3 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. HTML takes 264.1 kB which makes up the majority of the site volume.
Potential reduce by 232.9 kB
HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 232.9 kB or 88% of the original size.
Potential reduce by 20.6 kB
Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Obviously, Life Guardian needs image optimization as it can save up to 20.6 kB or 20% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 57.0 kB
It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 57.0 kB or 30% of the original size.
Potential reduce by 10.5 kB
CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Life.guardian.ng needs all CSS files to be minified and compressed as it can save up to 10.5 kB or 28% of the original size.
Number of requests can be reduced by 66 (78%)
85
19
The browser has sent 85 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Life Guardian. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 37 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
life.guardian.ng
263 ms
118 ms
263 ms
wp-emoji-release.min.js
50 ms
style.min.css
113 ms
change_of_name.css
54 ms
exchange_rate.css
51 ms
gallery.css
97 ms
stock_ticker.css
97 ms
style.css
182 ms
gpt.js
272 ms
publishertag.js
274 ms
js
269 ms
css
210 ms
4306aab6-6613-49be-bf56-cbe85e2ec46c-async.js
273 ms
bfde51174c21f80c13d7.js
268 ms
loadmore.js
95 ms
all.js
264 ms
guardian.ng.1307213.js
195 ms
jquery.js
410 ms
gallery.min.js
120 ms
ventra-polls.js
115 ms
stock_ticker.js
135 ms
polls-js.js
135 ms
jquery-migrate.min.js
151 ms
combined.js
149 ms
serviceworker.js
180 ms
jquery.sonar.min.js
180 ms
lazy-load.js
244 ms
wp-embed.min.js
401 ms
hb_733231_16244.js
494 ms
wrapper_hb_733231_16244.js
495 ms
fbevents.js
273 ms
header-logo-life-with-tagline.png
58 ms
header-logo-life-with-tagline-white.png
58 ms
logo-Guardian.png
62 ms
header-facebook.png
58 ms
header-instagram.png
57 ms
header-twitter.png
56 ms
header-telegram.png
206 ms
header-youtube.png
205 ms
header-linkedin.png
205 ms
header-menu-button-white.png
203 ms
share-facebook-white.png
264 ms
share-twitter-white.png
263 ms
share-instagram-white.png
264 ms
header-search-button-white.png
263 ms
logo-GuardianTV.png
263 ms
logo-GuardianLife.png
262 ms
social-facebook.png
268 ms
social-instagram.png
266 ms
social-twitter.png
266 ms
social-telegram.png
266 ms
close_icon.png
264 ms
1x1.trans.gif
264 ms
share-facebook.png
274 ms
share-twitter.png
274 ms
share-whatsApp.png
272 ms
share-telegram.png
257 ms
footer-goTop.png
255 ms
social-youtube.png
255 ms
social-linkedin.png
435 ms
gtm.js
179 ms
sideMenu-arrow@2x.png
415 ms
share-generic.png
380 ms
angle_left.png
379 ms
angle_right.png
446 ms
Qw3PZQNVED7rKGKxtqIqX5E-AVSJrOCfjY46_DjQbMZhKibpUVz0Eg.ttf
445 ms
Qw3PZQNVED7rKGKxtqIqX5E-AVSJrOCfjY46_LjQbMZhKibpUVz0Eg.ttf
535 ms
Qw3PZQNVED7rKGKxtqIqX5E-AVSJrOCfjY46_ObXbMZhKibpUVz0Eg.ttf
536 ms
pubads_impl_2022092701.js
152 ms
ppub_config
327 ms
analytics.js
232 ms
js
229 ms
247107802609931
268 ms
rz81sbzi7.js
261 ms
atrk.js
262 ms
js
122 ms
x8dd55t
680 ms
guardian.ng.1307213.es5.js
135 ms
syncframe
376 ms
atrk.gif
371 ms
IMG_3287-1-e1612982409436-531x299.jpg
259 ms
collect
286 ms
collect
92 ms
ga-audiences
92 ms
dmp.jq_flight.3033f0d7176196134921.js
222 ms
dmp.photon_manifest.9bb335b35e27b781622a.js
238 ms
dmp.photon_vendor.cb0d857b291806973621.js
241 ms
dmp.photon_boot.9c5efe50cb6241221259.js
239 ms
dmp.ie_error.1fd0b9b45ff1af9525c1.js
9 ms
life.guardian.ng accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
life.guardian.ng best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
life.guardian.ng SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).
Impact
Issue
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Life.guardian.ng can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Life.guardian.ng main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.
life.guardian.ng
Open Graph description is not detected on the main page of Life Guardian. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: