Zi.media - SEO Checker - Website Review

Your Website Score is

Similar Ranking

LUMPTY: LEARNING FOR THE FUN OF IT

lumpty.com

FREE ADVERTISING TRAFFIC EXCHANGE - TRAFFIC AD BAR

trafficadbar.com

JUST A MOMENT...

rmz.cr

WEB色見本原色大辞典 - HTMLカラーコード

colordic.org

PRESS INFORMATION BUREAU

pib.gov.in

理想生活上天猫

小谊家的小球星-HELLO, WORLD!

tiyu68.com

Latest Sites

THIẾT KẾ - THI CÔNG NỘI THẤT - SẢN XUẤT TRỰC TIẾP | NỘI THẤT MẠNH HỆ

noithatmanhhe.vn

SẢN PHẨM NỘI THẤT: GIƯỜNG TẦNG, GIƯỜNG BÀN, GIƯỜNG GẤP

nhacanhothongminh.com

CRYPTO-MINING.BIZ - REGISTERED AT NAMECHEAP.COM

crypto-mining.biz

99.9% DICE - BITCOIN, DOGECOIN, LITECOIN & ETHEREUM GAMBLING

999dice.com

RELANDICE BOT FOR 999DICE

relandice.com

❶ BẢO PHONG | LẮP ĐẶT CAMERA, CAMERA WIFI GIÁ RẺ Ở HUẾ !

baophong.vn

ONE MORE STEP

seeking.com

Top Technologies

Nginx

Web Servers

PHP

Programming Languages

Google Tag Manager

Tag Managers

Google Font API

Font Scripts

CloudFlare

CDN

jQuery

JavaScript Frameworks

Apache

Web Servers

Font Awesome

Font Scripts

WordPress

CMS

Twitter Bootstrap

Web Frameworks

34 zi.media Last Updated: 10 months

Success 70% of passed verification steps

Warning 15% of total warning

Errors 15% of total errors, require fast action

Mobile

Performance Desktop Score 67%

Best Practices Desktop Score 54%

SEO Desktop Score 82%

Progressive Web App Desktop Score 27%

Performance Mobile Score 20%

Best Practices Mobile Score 46%

SEO Mobile Score 80%

Progressive Web App Mobile Score 30%

Page Authority Authority 44%

Domain Authority Domain Authority 46%

Moz Rank 4.4/10

Bounce Rate Rate 0%

Charset Encoding

Great, language/character encoding is specified: UTF-8

Title Tag 6 Characters

ZI 字媒體

Meta Description 87 Characters

提供您最有效的美食,旅遊,3C,數位,攝影,電腦,手機,電玩,動漫,時尚,美容,彩妝,親子,寵物,居家,運動,汽車,機車,娛樂,電影,生活,婚姻,醫療,裝潢,藝文...等資訊

Effective URL 16 Characters

https://zi.media

Excerpt Page content

Zi 字媒體 Please click here if you are not redirected within a few seconds. 3C科技娛樂遊戲美食旅遊時尚美妝親子育兒生活休閒金融理財健康運動寰宇綜合更多直心巷明星店家 ...

Keywords Cloud Density

肚肚科技開店學18 tripmoment14 時刻旅行14 3c科技13 美食旅遊13 健康運動6 生活休閒5 ai即時新聞4 一點資訊4 寰宇綜合4

Keyword Consistency Keyword density is one of the main terms in SEO

Keyword	Freq	Title	Desc	Domain	H1	H2
肚肚科技開店學	18
tripmoment	14
時刻旅行	14
3c科技	13
美食旅遊	13
健康運動	6
生活休閒	5
ai即時新聞	4
一點資訊	4
寰宇綜合	4

Google Preview Your look like this in google search result

ZI 字媒體

https://zi.media

Robots.txt File Detected

http://zi.media/robots.txt

Sitemap.xml File Detected

http://zi.media/sitemap.xml

Whois Is a query and response protocol that is widely used for querying databases that store the registered users or assignees of an Internet resource, such as a domain name, an IP address block, or an autonomous system

Updated: 2018-11-19 / 2 years

Create on: 2017-03-23 / 3 years

Expires on: 2020-03-23 / 6 months 1 days

Gandi SAS ,TW

Registrar Name: REDACTED FOR PRIVACY

Registrar Whois Server: whois.gandi.net

Registrar URL: https://www.gandi.net

Registrar Phone: REDACTED

Registrar Email: Please

Registrar Address: REDACTED FOR PRIVACY , REDACTED FOR PRIVACY

REDACTED FOR PRIVACY

Admin Organization: REDACTED FOR PRIVACY

Admin Email: Please

Admin Phone: REDACTED

Admin Address: REDACTED FOR PRIVACY, REDACTED FOR PRIVACY

Nameservers

ns-cloud-e1.googledomains.com

ns-cloud-e2.googledomains.com

ns-cloud-e3.googledomains.com

ns-cloud-e4.googledomains.com

Page Size Code & Text Ratio

Document Size: ~149.44 KB

Code Size: ~98.31 KB

Text Size: ~51.13 KB Ratio: 34.21%

Estimation Traffic and Earnings

Only Registered Users

Sign up for see all features and reviews about this site

Technologies

PWA - Manifest

Manifest is not valid

Your site don't have valid manifest.json, read more in Web App Manifest

Desktop

Reduce server response times (TTFB) Root document took 1,400 ms

Time To First Byte identifies the time at which your server sends a response

Eliminate render-blocking resources Potential savings of 0 ms

Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles

Enable text compression Potential savings of 187 KB

Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes

Efficiently encode images Potential savings of 41 KB

Optimized images load faster and consume less cellular data

Minimize third-party usage Third-party code blocked the main thread for 230 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

Total Blocking Time 760 ms

Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.

Reduce JavaScript execution time 2.5 s

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this

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

Defer offscreen images Potential savings of 265 KB

Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive

Speed Index 4.4 s

Speed Index shows how quickly the contents of a page are visibly populated

First CPU Idle 2.3 s

First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. [Learn more](https://web.dev/first-cpu-idle).

Avoids enormous network payloads Total size was 1,811 KB

Large network payloads cost users real money and are highly correlated with long load times

Minimize main-thread work 4.9 s

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this

First Contentful Paint 0.7 s

First Contentful Paint marks the time at which the first text or image is painted

Includes front-end JavaScript libraries with known security vulnerabilities 1 vulnerability detected

Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers

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

Avoid an excessive DOM size 2,154 elements

A large DOM will increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow)

First Meaningful Paint 0.7 s

First Meaningful Paint measures when the primary content of a page is visible

Keep request counts low and transfer sizes small 155 requests • 1,811 KB

To set budgets for the quantity and size of page resources, add a budget.json file

Serve static assets with an efficient cache policy 53 resources found

A long cache lifetime can speed up repeat visits to your page

Max Potential First Input Delay 400 ms

The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task

Time to Interactive 3.0 s

Time to interactive is the amount of time it takes for the page to become fully interactive

Links do not have descriptive text 1 link found

Descriptive link text helps search engines understand your content

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

Page load is not fast enough on mobile networks Interactive on simulated mobile network at 15.3 s

A fast page load over a cellular network ensures a good mobile user experience

Estimated Input Latency 120 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

Remove unused CSS Potential savings of 17 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

Uses deprecated APIs 1 warning found

Deprecated APIs will eventually be removed from the browser

Serve images in next-gen formats Potential savings of 80 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

Mobile

Time to Interactive 20.9 s

Time to interactive is the amount of time it takes for the page to become fully interactive

Links do not have descriptive text 1 link found

Descriptive link text helps search engines understand your content

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

Page load is not fast enough on mobile networks Interactive at 20.9 s

A fast page load over a cellular network ensures a good mobile user experience

Estimated Input Latency 2,130 ms

First Contentful Paint (3G) 4060 ms

First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network

Tap targets are not sized appropriately 50% 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

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

Remove unused CSS Potential savings of 17 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

Uses deprecated APIs 1 warning found

Deprecated APIs will eventually be removed from the browser

Serve images in next-gen formats Potential savings of 17 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

Reduce server response times (TTFB) Root document took 840 ms

Time To First Byte identifies the time at which your server sends a response

Eliminate render-blocking resources Potential savings of 0 ms

Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles

Enable text compression Potential savings of 193 KB

Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes

Reduce the impact of third-party code Third-party code blocked the main thread for 3,350 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

Total Blocking Time 11,190 ms

Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.

Reduce JavaScript execution time 21.4 s

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this

Defer offscreen images Potential savings of 233 KB

Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive

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

Speed Index 16.2 s

Speed Index shows how quickly the contents of a page are visibly populated

First CPU Idle 18.8 s

First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. [Learn more](https://web.dev/first-cpu-idle).

Avoids enormous network payloads Total size was 2,056 KB

Large network payloads cost users real money and are highly correlated with long load times

Minimize main-thread work 33.8 s

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this

First Contentful Paint 3.2 s

First Contentful Paint marks the time at which the first text or image is painted

Includes front-end JavaScript libraries with known security vulnerabilities 1 vulnerability detected

Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers

Avoid chaining critical requests 5 chains found

Avoid an excessive DOM size 2,315 elements

First Meaningful Paint 3.2 s

First Meaningful Paint measures when the primary content of a page is visible

Keep request counts low and transfer sizes small 179 requests • 2,056 KB

To set budgets for the quantity and size of page resources, add a budget.json file

Serve static assets with an efficient cache policy 58 resources found

A long cache lifetime can speed up repeat visits to your page

Max Potential First Input Delay 3,150 ms

The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task

Speed And Optimization Tips

Only Registered Users

Sign up for see all features and reviews about this site

Alexa Rank

0

Local Rank: / Users: / PageViews:

Global Rank

Information Server

Response Header HTTP headers carry information about the client browser, the requested page and the server

HTTP/1.1 200 OK
Server: nginx/1.13.7
Date: Thu, 28 Nov 2019 10:35:32 GMT
Content-Type: text/html; charset=UTF-8
Connection: keep-alive
Vary: Accept-Encoding
Content-Encoding: gzip
X-Backend: zimedia_app
X-UA-Device: pc
X-User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.77 Safari/537.36
cache-control: max-age = 7200
X-Varnish: 649429323
Age: 0
X-Cache: MISS
X-Cache-Hits: 0

DNS Records DNS Resource Records associated with a hostname

View DNS Records

Type	Name	Value	Class	TTL
A	zi.media	35.194.179.75	IN	213
NS	zi.media	ns-cloud-e1.googledomains.com	IN	21599
NS	zi.media	ns-cloud-e2.googledomains.com	IN	21599
NS	zi.media	ns-cloud-e3.googledomains.com	IN	21599
NS	zi.media	ns-cloud-e4.googledomains.com	IN	21599
MX	zi.media	spool.mail.gandi.net	IN	10799
MX	zi.media	fb.mail.gandi.net	IN	10799

Your Website Score is

Similar Ranking

Latest Sites

Top Technologies

34 zi.media Last Updated: 10 months

Desktop

Mobile

Estimation Traffic and Earnings

Sign up for see all features and reviews about this site

Technologies

comScore

Google Font API

Google Tag Manager

Nginx

Varnish

PWA - Manifest

Desktop

Mobile

Speed And Optimization Tips

Sign up for see all features and reviews about this site

Alexa Rank

0

Information Server

Comments