7.6 sec in total
1.4 sec
5.4 sec
822 ms
Visit ends.ng now to see the best up-to-date ENDS content for Nigeria and also check out these interesting facts you probably never knew about ends.ng
Don't Break The Chain: Suffering ENDS Now!
Visit ends.ngWe analyzed Ends.ng page load time and found that the first response time was 1.4 sec and then it took 6.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
ends.ng performance score
name
value
score
weighting
Value2.4 s
70/100
10%
Value7.7 s
3/100
25%
Value11.9 s
4/100
10%
Value4,750 ms
0/100
30%
Value0.289
42/100
15%
Value28.5 s
0/100
10%
1362 ms
70 ms
151 ms
206 ms
138 ms
Our browser made a total of 124 requests to load all elements on the main page. We found that 21% of them (26 requests) were addressed to the original Ends.ng, 12% (15 requests) were made to Static.xx.fbcdn.net and 8% (10 requests) were made to Voahausa.com. The less responsive or slowest element that took the longest time to load (1.9 sec) relates to the external source I1.wp.com.
Page size can be reduced by 702.4 kB (41%)
1.7 MB
1.0 MB
In fact, the total size of Ends.ng main page is 1.7 MB. 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. Images take 692.0 kB which makes up the majority of the site volume.
Potential reduce by 38.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 38.9 kB or 72% of the original size.
Potential reduce by 13.0 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. ENDS images are well optimized though.
Potential reduce by 335.3 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 335.3 kB or 60% of the original size.
Potential reduce by 315.3 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. Ends.ng needs all CSS files to be minified and compressed as it can save up to 315.3 kB or 78% of the original size.
Number of requests can be reduced by 73 (62%)
118
45
The browser has sent 118 CSS, Javascripts, AJAX and image requests in order to completely render the main page of ENDS. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 54 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
ends.ng
1362 ms
wp-emoji-release.min.js
70 ms
style.css
151 ms
dashicons.min.css
206 ms
desktop_style.css
138 ms
style.css
141 ms
wpgform.css
139 ms
jetpack.css
143 ms
front.end.css
215 ms
jquery.js
335 ms
jquery-migrate.min.js
210 ms
front_end_script.js
211 ms
adsbygoogle.js
6 ms
photon.js
212 ms
navigation.js
270 ms
skip-link-focus-fix.js
275 ms
comment-reply.min.js
281 ms
devicepx-jetpack.js
4 ms
wp-embed.min.js
277 ms
reset.css
142 ms
expound.css
220 ms
march18.jpg
875 ms
DaEpBLqaO_0
342 ms
idpflier5.png
884 ms
IMG_00000642.jpg
882 ms
h4Rf-98rBzE
426 ms
A5NE8zwwu-I
425 ms
2524741.html
60 ms
idpflier2.png
442 ms
IMG_00000647.jpg
866 ms
ends-girl.png
1864 ms
09BokoHaram1-master1050-v2.jpg
865 ms
cropped-ends-header2.png
574 ms
idpbooks.png
336 ms
idpflier22221.png
414 ms
donatee-150x150.jpg
337 ms
rss.png
336 ms
top.png
413 ms
Freedom-Radio-99.5-FM.jpeg
429 ms
ca-pub-0531519584021827.js
381 ms
zrt_lookup.html
388 ms
show_ads_impl.js
294 ms
jquery-1.10.2.x.js
327 ms
TemplateC.x.js
33 ms
jsapi
438 ms
ScriptResource.axd
285 ms
ScriptResource.axd
324 ms
RFERL.UI.Web.Controls.Utilities.x.js
31 ms
Infographics.x.js
283 ms
versionhelper.x.js
323 ms
controller.x.js
362 ms
jquery.min.js
360 ms
platform.js
439 ms
all.js
785 ms
www-embed-player-vflfNyN_r.css
187 ms
www-embed-player.js
250 ms
base.js
288 ms
ads
491 ms
ga.js
51 ms
osd.js
50 ms
ads
451 ms
ads
430 ms
__utm.gif
107 ms
__utm.gif
90 ms
widgets.js
309 ms
sdk.js
560 ms
collect
546 ms
fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js
144 ms
ad_status.js
396 ms
Multimedia.Playlist.x.js
239 ms
cb=gapi.loaded_0
110 ms
cb=gapi.loaded_1
210 ms
fastbutton
289 ms
2UX7WLTfW3W8TclTUvlFyQ.woff
289 ms
RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff
338 ms
15519260706633516500
363 ms
abg.js
366 ms
m_js_controller.js
372 ms
googlelogo_color_112x36dp.png
331 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
108 ms
337 ms
xd_arbiter.php
373 ms
xd_arbiter.php
560 ms
postmessageRelay
180 ms
cb=gapi.loaded_0
93 ms
cb=gapi.loaded_1
92 ms
grlryt2bdKIyfMSOhzd1eA.woff
73 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.en.html
47 ms
203 ms
x_button_blue2.png
41 ms
s
34 ms
3193398744-postmessagerelay.js
111 ms
rpc:shindig_random.js
71 ms
fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js
11 ms
jot
75 ms
cb=gapi.loaded_0
3 ms
share_button.php
71 ms
qeKvIRsJabD.js
480 ms
LVx-xkvaJ0b.png
545 ms
ui
12 ms
xd_arbiter.php
140 ms
like.php
76 ms
like.php
68 ms
like_box.php
356 ms
qeKvIRsJabD.js
205 ms
qeKvIRsJabD.js
408 ms
qeKvIRsJabD.js
431 ms
ebiMDO3r-8l.css
70 ms
jGc-59L_9lo.css
139 ms
q68gy-v_YMF.js
152 ms
FJmpeSpHpjS.js
220 ms
0wM5s1Khldu.js
207 ms
1bNoFZUdlYZ.js
206 ms
402393_600081806688483_1672850576_n.jpg
339 ms
10172663_847829185247076_171770493066825238_n.png
359 ms
11403490_671575732943502_1104855416729840503_n.jpg
431 ms
12821389_1533131390316895_5444953331113528767_n.jpg
536 ms
11846761_427760634095625_3971488360860115104_n.jpg
498 ms
12410575_154548101586849_4790318332135188540_n.jpg
497 ms
10294455_1668420093409044_6186572560460569921_n.jpg
498 ms
wL6VQj7Ab77.png
69 ms
s7jcwEQH7Sx.png
69 ms
I6-MnjEovm5.js
81 ms
pQrUxxo5oQp.js
69 ms
ends.ng accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
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
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
ends.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
Issues were logged in the Issues panel in Chrome Devtools
ends.ng SEO score
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 Ends.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 Ends.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.
ends.ng
Open Graph data is detected on the main page of ENDS. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: