Citytrend.Com.Ng - Info receives about 5,443 unique visitors and 11,431 (2.10 per visitor) page views per day which should earn about $29.95/day from advertising revenue. Estimated site value is $21,863.59. According to Alexa Traffic Rank is ranked number 421,045 in the world and 0.00012% of global Internet users visit it. Site is hosted in Los Angeles, California, 90064, United States and links to network IP address This server supports HTTPS and HTTP/2.

About -

Technologies used on Website

All in One SEO Pack
Web Servers
Font Scripts
Font Awesome
Google Font API
Google Analytics
Programming Languages
JavaScript Libraries
jQuery Migrate
MySQL Profile

Title: CitytrendTv v2.0 (Your No. 1 Infotainment Music and Entertainment Hub) | Latest Naija Music, South Africa, Ghana, Videos, Movies, Latest Mixtape, Entertainment Gist, Free Beatz
Description: [Mp3] DJ Ozzytee ft. KSolar Ibile – Lobatan : Download and Stream DJ Ozzytee, KSolar Ibile Mp3 Songs Audio Djozzytee Ent.World Is Here Again With A New Tune
Keywords: dj ozzytee,ksolar ibile,lobatan,naija music,utang akwa ibom mourns victor olaiya,mourns victor olaiya,utang akwa ibom,stories,abasi,feelingz,king eddy,richy b,hisword,oje,seriki poly,everywhere,veekyfreshy,gospel songs,ay gold,owo ni daddy (2tboyz),professional,pr music,amin,coblaze,love song,retaw da rapper,og,yomi blaze,buga,dj xclusive,t classic,n2easy,package,wazzy
Last update was 10 days ago
This can take up to 60 seconds. Please wait...

* is not linking to, promoting or affiliated with in any way. Only publicly available statistics data are displayed.

How popular is

5.4K daily visitors
Is this your site?
Verify your site's metrics.
Daily Unique Visitors:
Monthly Unique Visitors:
Pages per Visit:
Daily Pageviews:
Alexa Rank:
421,045 visit alexa
Alexa Reach:
0.00012%   (of global internet users)
Avg. visit duration:
Bounce rate:
*All traffic values are estimates only.

Alexa Traffic Ranks
Search Traffic

Traffic sources


Visitors by country

Nigeria 100.0%100.0%5240

Where do visitors go on this site?


Competitive Data

(Rank based on keywords, cost and organic traffic)
Organic Keywords:
(Number of keywords in top 20 Google SERP)
Organic Traffic:
(Number of visitors coming from top 20 search results)
Organic Cost:
((How much need to spend if get same number of visitors from Google Adwords)
Adwords Keywords:
(Keywords a website is buying in Google AdWords for ads that appear in paid search results)
Adwords Traffic:
(Number of visitors brought to the website via paid search results)
Adwords Cost:
(Estimated budget spent for buying keywords in Google AdWords for ads that appear in paid search results - monthly estimation)

+ Moz Data

Domain Authority:
Page Authority:

+ How socially engaged is

Google +:

+ Ad Experience Report

Summary of the ad experience rating of a site for a specific platform.

Desktop summary

Root domain:
(The Ad Standard region to which this site has been assigned.)
Ad filtering:
(Chrome is not filtering ads on your site.)
(The status of the site that is reviewed for the Better Ads Standards.)
Not reviewed

Mobile summary

(The Ad Standard region to which this site has been assigned.)
Ad filtering:
(Chrome is not filtering ads on your site.)
(The status of the site that is reviewed for the Better Ads Standards.)
Not reviewed

+ Abusive Experience Report

Root domain:
(Chrome is not preventing your site from opening new windows or tabs.)
(The status of the site reviewed for the abusive experiences.)
Not reviewed

+ How much can earn?

Daily Revenue:
Monthly Revenue:
Yearly Revenue:
*All earnings values are estimates only.

Daily earning by country

Nigeria 11,431$29.95

How much money do lose due to Adblock?

Daily Revenue Loss:
Monthly Revenue Loss:
Yearly Revenue Loss:
Daily Pageviews Blocked:
Monthly Pageviews Blocked:
Yearly Pageviews Blocked:
*All earnings values are estimates only.

Daily revenue loss by country

BlockedLost Money
Nigeria 229$0.60

How much is worth?

Website Value:

+ Where is hosted?

Server IP:
Namecheap, Inc. 
Server Location:
Los Angeles
California, CA
United States, US

Other sites hosted on

+ How fast does load?

Average Load Time:
n/a ms n/a % of sites are slower

Page Speed (Google PageSpeed Insights) - Desktop

0-49 50-89 90-100 i

Field Data

Over the last 30 days, the field data shows that this page has a speed compared to other pages in the Chrome User Experience Report.We are showing the 90th percentile of FCP and the 95th percentile of FID.

Origin Data

All pages served from this origin have an speed compared to other pages in the Chrome User Experience Report. over the last 30 days.To view suggestions tailored to each page, analyze individual page URLs.

Lab Data

Max Potential First Input Delay 30 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task. Learn more.
Time to Interactive 1.0 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Estimated Input Latency 10 ms
Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy. 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.
Speed Index 1.0 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 1.0 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. Learn more.
First Contentful Paint 0.9 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.
Performance budget
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more.
First Meaningful Paint 1.0 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more.

Screenshot Thumbnails

This is what the load of your site looked like.

Network Requests
Lists the network requests that were made during page load.

Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
0 ms102 ms0 KB0 KB301text/html
102 ms450 ms12 KB82 KB200text/htmlDocument
464 ms469 ms18 KB44 KB200text/javascriptScript
465 ms559 ms1 KB1 KB200text/cssStylesheet
465 ms484 ms6 KB40 KB200text/cssStylesheet
465 ms560 ms3 KB19 KB200text/cssStylesheet,400italic,700,600
466 ms486 ms2 KB10 KB200text/cssStylesheet
466 ms565 ms9 KB44 KB200text/cssStylesheet
466 ms563 ms7 KB30 KB200text/cssStylesheet
466 ms489 ms12 KB70 KB200text/cssStylesheet
466 ms501 ms32 KB95 KB200application/javascriptScript
467 ms483 ms4 KB10 KB200application/javascriptScript
467 ms564 ms1 KB2 KB200application/x-javascriptScript
467 ms562 ms10 KB30 KB200application/x-javascriptScript
467 ms676 ms2 KB4 KB200text/cssStylesheet
468 ms483 ms18 KB18 KB200image/webpImage
604 ms789 ms0 KB0 KB301text/html
604 ms790 ms0 KB0 KB301text/html
604 ms788 ms0 KB0 KB301text/html
604 ms789 ms0 KB0 KB301text/html
605 ms789 ms0 KB0 KB301text/html
605 ms834 ms0 KB0 KB301text/html
605 ms790 ms0 KB0 KB301text/html
605 ms788 ms0 KB0 KB301text/html
605 ms873 ms62 KB62 KB200image/pngImage
605 ms961 ms131 KB131 KB200image/pngImage
605 ms875 ms57 KB57 KB200image/pngImage
606 ms700 ms6 KB6 KB200image/pngImage
606 ms959 ms80 KB80 KB200image/pngImage
606 ms834 ms0 KB0 KB301text/html
606 ms834 ms0 KB0 KB301text/html
607 ms835 ms0 KB0 KB301text/html
607 ms791 ms0 KB0 KB301text/html
607 ms625 ms17 KB16 KB200image/webpImage
607 ms625 ms14 KB14 KB200image/webpImage
607 ms626 ms9 KB8 KB200image/webpImage
607 ms627 ms7 KB6 KB200image/webpImage
607 ms635 ms18 KB17 KB200image/webpImage
607 ms626 ms10 KB10 KB200image/webpImage
607 ms626 ms13 KB12 KB200image/webpImage
608 ms630 ms11 KB11 KB200image/webpImage
608 ms624 ms12 KB11 KB200image/webpImage
608 ms640 ms15 KB14 KB200image/webpImage
608 ms641 ms17 KB17 KB200image/webpImage
609 ms631 ms2 KB2 KB200image/webpImage
609 ms633 ms1 KB1 KB200image/webpImage
609 ms628 ms2 KB2 KB200image/webpImage
609 ms629 ms2 KB2 KB200image/webpImage
610 ms628 ms3 KB2 KB200image/webpImage
610 ms633 ms3 KB2 KB200image/webpImage
610 ms629 ms3 KB2 KB200image/webpImage
610 ms637 ms3 KB2 KB200image/webpImage
610 ms630 ms3 KB2 KB200image/jpegImage
610 ms706 ms5 KB14 KB200application/x-javascriptScript
610 ms633 ms2 KB1 KB200image/webpImage
610 ms631 ms2 KB2 KB200image/webpImage
610 ms637 ms2 KB1 KB200image/webpImage
610 ms632 ms3 KB3 KB200image/webpImage
611 ms631 ms2 KB1 KB200image/webpImage
611 ms633 ms2 KB1 KB200image/webpImage
611 ms638 ms3 KB2 KB200image/webpImage
611 ms632 ms2 KB2 KB200image/webpImage
611 ms791 ms0 KB0 KB301text/html
611 ms835 ms0 KB0 KB301text/html
523 ms544 ms1 KB1 KB200application/javascriptScript
529 ms624 ms4 KB8 KB200application/x-javascriptScript
577 ms592 ms1 KB1 KB200application/javascriptScript
611 ms634 ms3 KB9 KB200application/x-javascriptScript
611 ms617 ms1 KB0 KB200image/gifImage
678 ms708 ms3 KB3 KB200application/x-javascriptScript
694 ms694 ms0 KB0 KB200image/pngImage
704 ms707 ms15 KB14 KB200font/woff2Font
705 ms708 ms15 KB15 KB200font/woff2Font
707 ms1061 ms76 KB75 KB200application/font-woff2Font
711 ms714 ms14 KB13 KB200font/woff2Font
789 ms969 ms29 KB29 KB200image/pngImage
789 ms1674 ms943 KB942 KB200image/pngImage
789 ms1144 ms168 KB167 KB200image/pngImage
789 ms970 ms27 KB26 KB200image/gifImage
790 ms1153 ms159 KB159 KB200image/pngImage
791 ms1581 ms1152 KB1151 KB200image/pngImage
791 ms884 ms2 KB2 KB200image/pngImage
791 ms971 ms17 KB16 KB200image/pngImage
791 ms887 ms10 KB10 KB200image/pngImage
833 ms847 ms0 KB0 KB200image/gifImage
834 ms1274 ms38 KB37 KB200image/pngImage
834 ms1549 ms1311 KB1311 KB200image/pngImage
835 ms1106 ms6 KB5 KB200image/pngImage
835 ms1017 ms38 KB38 KB200image/pngImage
835 ms1103 ms7 KB7 KB200image/pngImage
850 ms865 ms1 KB2 KB200image/svg+xmlImage
853 ms874 ms56 KB187 KB200application/x-javascriptScript
918 ms953 ms1 KB0 KB200text/plainFetch
Uses efficient cache policy on static assets - 2 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.

Cache TTLSize
1200000 ms3 KB
7200000 ms18 KB
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.

SizeMain-Thread Blocking Time
60 KB0 ms
58 KB0 ms
19 KB0 ms
3 KB0 ms
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
475 ms
7 ms
486 ms
55 ms
555 ms
34 ms
599 ms
33 ms
699 ms
12 ms
711 ms
56 ms
767 ms
43 ms
820 ms
32 ms
862 ms
10 ms
910 ms
18 ms
932 ms
9 ms
1004 ms
8 ms
1084 ms
7 ms
1091 ms
28 ms
1587 ms
7 ms
1609 ms
25 ms
1701 ms
13 ms
1721 ms
32 ms
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.

Potential Savings
3 ms
3 ms
354 ms
3 ms
JavaScript execution time - 0.1 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

Total CPU TimeScript EvaluationScript Parse
386 ms10 ms1 ms
53 ms46 ms2 ms
Properly size images - Potential savings of 402 KB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.

SizePotential Savings
131 KB130 KB
80 KB79 KB
62 KB60 KB
57 KB55 KB
17 KB8 KB
17 KB8 KB
16 KB8 KB
18 KB7 KB
14 KB7 KB
14 KB7 KB
12 KB6 KB
11 KB5 KB
6 KB5 KB
11 KB5 KB
10 KB5 KB
8 KB4 KB
6 KB3 KB
Remove unused CSS - Potential savings of 12 KB
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity. Learn more.

SizePotential Savings
12 KB12 KB
Avoid enormous network payloads - Total size was 4,765 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

1311 KB
1152 KB
943 KB
168 KB
159 KB
131 KB
80 KB
76 KB
62 KB
57 KB
Minimizes main-thread work - 0.6 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

Time Spent
Script Evaluation
187 ms
119 ms
116 ms
Style & Layout
111 ms
Parse HTML & CSS
38 ms
Script Parsing & Compilation
18 ms
Serve images in next-gen formats - Potential savings of 3,709 KB
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more.

SizePotential Savings
1311 KB1189 KB
1151 KB1047 KB
942 KB847 KB
167 KB142 KB
159 KB135 KB
131 KB108 KB
80 KB67 KB
62 KB52 KB
57 KB48 KB
37 KB28 KB
38 KB23 KB
29 KB21 KB
Avoids an excessive DOM size - 713 elements
A large DOM will increase memory usage, cause longer [style calculations](, and produce costly [layout reflows]( Learn more.

Total DOM Elements
Maximum DOM Depth
Maximum Child Elements
Avoid multiple page redirects - Potential savings of 190 ms
Redirects introduce additional delays before the page can be loaded. Learn more.

Time Spent
Keep request counts low and transfer sizes small - 93 requests • 4,765 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
934765 KB
524446 KB
12140 KB
4120 KB
842 KB
112 KB
165 KB
00 KB
48386 KB
Eliminate render-blocking resources - Potential savings of 230 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.

SizePotential Savings
1 KB70
6 KB270
3 KB150,400italic,700,600
2 KB230
9 KB230
7 KB190
12 KB310
32 KB430
4 KB230
1 KB150
10 KB190
2 KB70
Network Round Trip Times - 0 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance. Learn more.

Preconnect to required origins
Consider adding `preconnect` or `dns-prefetch` resource hints to establish early connections to important third-party origins. Learn more.

Minify CSS
Minifying CSS files can reduce network payload sizes. Learn more.

Server Backend Latencies - 0 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance. 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.

Avoid chaining critical requests - 19 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.

Preload key requests
Consider using `` to prioritize fetching resources that are currently requested later in page load. Learn more.

Minify JavaScript
Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.

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.

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 more.

Server response times are low (TTFB) - Root document took 350 ms
Time To First Byte identifies the time at which your server sends a response. Learn more.

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.

Page Speed (Google PageSpeed Insights) - Mobile

Currently Not Available

Page Speed (Google PageSpeed Insights) - v2

Suggestions Summary

Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 256.2KiB (80% reduction).

Compressing and resizing could save 126.9KiB (96% reduction).
Compressing and resizing could save 56.3KiB (90% reduction).
Compressing and resizing could save 53.6KiB (94% reduction).
Compressing could save 10.9KiB (30% reduction).
Compressing could save 8.4KiB (30% reduction).

Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 1 blocking CSS resources. This causes a delay in rendering your page.

None of the above-the-fold content on your page could be rendered without waiting for the following resources to load. Try to defer or asynchronously load blocking resources, or inline the critical portions of those resources directly in the HTML.Optimize CSS Delivery of the following:

Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Leverage browser caching for the following cacheable resources: (20 minutes)******ytics.js (2 hours)

Reduce server response time

In our test, your server responded in 0.24 seconds.

There are many factors that can slow down your server response time. Please read our recommendations to learn how you can monitor and measure where your server is spending the most time.

Minify CSS

Compacting CSS code can save many bytes of data and speed up download and p*** times.

Minify CSS for the following resources to reduce their size by 2KiB (17% reduction).

Minifying could save 1.5KiB (17% reduction) after compression.
Minifying could save 532B (18% reduction) after compression.

Minify JavaScript

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and *** time.

Minify JavaScript for the following resources to reduce their size by 920B (35% reduction).

Minifying could save 674B (39% reduction) after compression.
Minifying could save 246B (28% reduction) after compression.
Avoid landing page redirects
Your page has no redirects. Learn more about avoiding landing page redirects.
Avoid plugins
Your page does not appear to use plugins, which would prevent content from being usable on many platforms. Learn more about the importance of avoiding plugins.
Configure the viewport
Your page specifies a viewport matching the device's size, which allows it to render properly on all devices. Learn more about configuring viewports.
Enable compression
You have compression enabled. Learn more about enabling compression.
Minify HTML
Your HTML is minified. Learn more about minifying HTML.
Prioritize visible content
You have the above-the-fold content properly prioritized. Learn more about prioritizing visible content.
Size content to viewport
The contents of your page fit within the viewport. Learn more about sizing content to the viewport.
Size tap targets appropriately
All of your page's links/buttons are large enough for a user to easily tap on a touchscreen. Learn more about sizing tap targets appropriately.
Use legible font sizes
The text on your page is legible. Learn more about using legible font sizes.
Download optimized image, JavaScript, and CSS resources for this page.

+ Does use compression? use gzip compression.
Original size: 82.04 KB
Compressed size: 11.9 KB
File reduced by: 70.14 KB (85%)

+ Google Safe Browsing

This site is not currently listed as suspicious Reputation Ratings

Vendor reliability:
Child safety:

+ SSL Checker - SSL Certificate Verify supports HTTPS
Verifying SSL Support. Please wait...
Common Name:
Issuer: Sectigo RSA Domain Validation Secure Server CA
Valid from: Sep 8 00:00:00 2019 GMT
Valid until: Sep 21 23:59:59 2020 GMT

+ Verify HTTP/2 Support supports HTTP/2
Verifying HTTP/2.0 Support. Please wait...

+ Site Categories (dmoz)

Currently Not Available

+ Http Header

Date: Fri, 14 Feb 2020 10:24:33 GMT
Server: Apache
Content-Length: 233
Content-Type: text/html; charset=iso-8859-1

HTTP/2 200 
date: Fri, 14 Feb 2020 10:24:33 GMT
server: Apache
x-powered-by: PHP/7.0.33
link: <>; rel="", <>; rel=shortlink
vary: Accept-Encoding
content-encoding: gzip
content-length: 12184
content-type: text/html; charset=UTF-8

+ DNS Lookup

Type Ip Target TTL
MX 1200
SOA 3600
Serial Number 1575244322
Refresh 86400
Retry 7200
Expire 3600000
Minimum TTL 0
A 1167
NS 3566
NS 3566

+ Whois Lookup

Domain Created:
Domain Age:

Currently Not Available
Last update was 10 days ago
This can take up to 60 seconds. Please wait...

* is not linking to, promoting or affiliated with in any way. Only publicly available statistics data are displayed.
We are using the world's No. 1 Marketing Tool to grow our website. Activate your FREE trial today!


Install HypeStat extension in your browser to see statistics and technologies used with one click.

Hide/Remove your site data

• Use Show/Hide ESTIMATED data form to hide (Website worth, Daily ads revenue, Daily Visits, Daily Pageviews)
• Use Show/Hide WHOIS data form to hide whois data
• Use Remove form to remove all data
• If you have any problem with REMOVE/HIDE your data just drop an email at support (at) and we will remove/hide your site data manualy.
Make custom Widget for your website
Get the code now! widget