Your Website Score is

Similar Ranking

41
IDPAY | آیدی پی
idpay.ir
41
KÊNH THÔNG TIN KINH TẾ - TÀI CHÍNH VIỆT NAM
cafef.vn
41
FREE CLIP ART - CLIP ART COLLECTION - DOWNLOAD CLIPART ON CLIPART LIBRARY
clipart-library.com
41
MUBI: WATCH AND DISCOVER MOVIES
mubi.com
41
SIMPLENOTE
simplenote.com
41
МВД РОССИИ
xn--b1aew.xn--p1ai
41
سینماتیکت بزرگترین مرجع فروش بلیت سینما
cinematicket.org

Latest Sites

24
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
19
SẢN PHẨM NỘI THẤT: GIƯỜNG TẦNG, GIƯỜNG BÀN, GIƯỜNG GẤP
nhacanhothongminh.com
16
CRYPTO-MINING.BIZ - REGISTERED AT NAMECHEAP.COM
crypto-mining.biz
57
99.9% DICE - BITCOIN, DOGECOIN, LITECOIN & ETHEREUM GAMBLING
999dice.com
19
RELANDICE BOT FOR 999DICE
relandice.com
23
❶ BẢO PHONG | LẮP ĐẶT CAMERA, CAMERA WIFI GIÁ RẺ Ở HUẾ !
baophong.vn

Top Technologies

Nginx
Web Servers
Google Tag Manager
Tag Managers
Google Font API
Font Scripts
CloudFlare
CDN
Apache
Web Servers
Font Awesome
Font Scripts
WordPress
CMS
Twitter Bootstrap
Web Frameworks

41 discovery.co.za Last Updated: 9 months

Success 47% of passed verification steps
Warning 30% of total warning
Errors 23% of total errors, require fast action

Desktop

Mobile

Performance Desktop Score 34%
Best Practices Desktop Score 77%
SEO Desktop Score 64%
Progressive Web App Desktop Score 31%
Performance Mobile Score 17%
Best Practices Mobile Score 77%
SEO Mobile Score 69%
Progressive Web App Mobile Score 33%
Page Authority Authority 45%
Domain Authority Domain Authority 58%
Moz Rank 4.5/10
Bounce Rate Rate 0%
Charset Encoding
Great, language/character encoding is specified: UTF-8
Title Tag 59 Characters
MEDICAL AID, BANK, INSURANCE, INVEST & VITALITY - DISCOVERY
Meta Description 151 Characters
Discovery offers award-winning products - Medical Aid Administration, Car and Life Insurance, Bank Accounts and Investments, all with Vitality rewards.
Effective URL 34 Characters
https://www.discovery.co.za/portal
Excerpt Page content
Medical Aid, Bank, Insurance, Invest & Vitality - Discovery ...
Keywords Cloud Density
discovery33 insurance29 vitality25 cover21 life19 quote18 medical14 bank13 join11 find11
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
discovery 33
insurance 29
vitality 25
cover 21
life 19
quote 18
medical 14
bank 13
join 11
find 11
Google Preview Your look like this in google search result
MEDICAL AID, BANK, INSURANCE, INVEST & VITALITY - DISCOVERY
https://www.discovery.co.za/portal
Discovery offers award-winning products - Medical Aid Administration, Car and Life Insurance, Bank Accounts and Investments, all with Vitality rewards
Robots.txt File No Found
Sitemap.xml File No Found
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: 2019-07-18 / 1 year
Create on: 1996-08-19 / 24 years
Expires on: 2020-08-19 / 1 months 9 days

MarkMonitor ,ZA
Registrar Name: REDACTED
Registrar URL: markmonitor.com
Registrar Phone: REDACTED
Registrar Email: Please
Registrar Address: REDACTED , REDACTED

REDACTED
Admin Organization: REDACTED
Admin Email: Please
Admin Phone: REDACTED
Admin Address: REDACTED, REDACTED

Nameservers
ns229.a1.incapsecuredns.net
ns128.a0.incapsecuredns.net
ns101.a2.incapsecuredns.net
Page Size Code & Text Ratio
Document Size: ~138.43 KB
Code Size: ~84.36 KB
Text Size: ~54.07 KB Ratio: 39.06%

Estimation Traffic and Earnings

Only Registered Users

Sign up for see all features and reviews about this site

Login

Technologies

PWA - Manifest

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

Desktop

Desktop Screenshot
Total Blocking Time 400 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.3 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 635 KB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Properly size images Potential savings of 69 KB
Serve images that are appropriately-sized to save cellular data and improve load time
Speed Index 4.8 s
Speed Index shows how quickly the contents of a page are visibly populated
First CPU Idle 4.7 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).
Avoid enormous network payloads Total size was 5,302 KB
Large network payloads cost users real money and are highly correlated with long load times
Minimize main-thread work 4.0 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
robots.txt is not valid 1 error found
If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed
First Contentful Paint 0.9 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 3 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Avoid chaining critical requests 16 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 1,823 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)
Preload key requests Potential savings of 130 ms
Consider using `<link rel=preload>` to prioritize fetching resources that are currently requested later in page load
Minify JavaScript Potential savings of 33 KB
Minifying JavaScript files can reduce payload sizes and script parse time
First Meaningful Paint 3.0 s
First Meaningful Paint measures when the primary content of a page is visible
Keep request counts low and transfer sizes small 183 requests • 5,311 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 71 resources found
A long cache lifetime can speed up repeat visits to your page
Max Potential First Input Delay 200 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task
Time to Interactive 6.6 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Links do not have descriptive text 4 links 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 28.7 s
A fast page load over a cellular network ensures a good mobile user experience
Estimated Input Latency 40 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 284 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
Serve images in next-gen formats Potential savings of 538 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
Avoid multiple page redirects Potential savings of 230 ms
Redirects introduce additional delays before the page can be loaded
User Timing marks and measures 30 user timings
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences
Reduce server response times (TTFB) Root document took 1,550 ms
Time To First Byte identifies the time at which your server sends a response
Eliminate render-blocking resources Potential savings of 360 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Efficiently encode images Potential savings of 105 KB
Optimized images load faster and consume less cellular data
Enable text compression Potential savings of 120 KB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes
Minimize third-party usage Third-party code blocked the main thread for 120 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

Mobile

Mobile Screenshot
Total Blocking Time 4,820 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Reduce JavaScript execution time 10.3 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 571 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 17.6 s
Speed Index shows how quickly the contents of a page are visibly populated
First CPU Idle 22.7 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).
Avoid enormous network payloads Total size was 5,366 KB
Large network payloads cost users real money and are highly correlated with long load times
Minimize main-thread work 15.2 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
robots.txt is not valid 1 error found
If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed
First Contentful Paint 3.5 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 3 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Avoid chaining critical requests 16 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 1,375 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)
Preload key requests Potential savings of 1,470 ms
Consider using `<link rel=preload>` to prioritize fetching resources that are currently requested later in page load
Minify JavaScript Potential savings of 33 KB
Minifying JavaScript files can reduce payload sizes and script parse time
First Meaningful Paint 3.5 s
First Meaningful Paint measures when the primary content of a page is visible
Keep request counts low and transfer sizes small 180 requests • 5,376 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 72 resources found
A long cache lifetime can speed up repeat visits to your page
Max Potential First Input Delay 700 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task
Time to Interactive 28.8 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Links do not have descriptive text 4 links 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 28.8 s
A fast page load over a cellular network ensures a good mobile user experience
Estimated Input Latency 280 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
First Contentful Paint (3G) 7050 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 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
Document uses legible font sizes 90.27% 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 285 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
Serve images in next-gen formats Potential savings of 561 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
Avoid multiple page redirects Potential savings of 780 ms
Redirects introduce additional delays before the page can be loaded
User Timing marks and measures 30 user timings
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences
Reduce server response times (TTFB) Root document took 1,790 ms
Time To First Byte identifies the time at which your server sends a response
Eliminate render-blocking resources Potential savings of 1,020 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 120 KB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes
Efficiently encode images Potential savings of 177 KB
Optimized images load faster and consume less cellular data
Reduce the impact of third-party code Third-party code blocked the main thread for 2,030 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

Speed And Optimization Tips

Only Registered Users

Sign up for see all features and reviews about this site

Login

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 302 Moved Temporarily
Date: Fri, 03 Jan 2020 02:45:09 GMT
Server: Apache/2.4.6 (Red Hat Enterprise Linux) OpenSSL/1.0.2k-fips
Location: https://www.discovery.co.za/portal/
X-OneAgent-JS-Injection: true
X-ruxit-JS-Agent: true
Set-Cookie: dtCookie=6$E94151C8C28E8BECBABA7B9C555D3828; Path=/; Domain=.discovery.co.za
Content-Type: text/html; charset=UTF-8
Set-Cookie: visid_incap_1753140=G1dgYi8SQk6M6WUTmyVFa7WqDl4AAAAAQUIPAAAAAACkY9mQemA3OdDfgRem9iI6; expires=Fri, 01 Jan 2021 11:04:12 GMT; path=/; Domain=.discovery.co.za
Set-Cookie: incap_ses_148_1753140=EQG5dDbZ8Fub7VYpM9ENArWqDl4AAAAAJK7mcHK0ip3jsM3x6Y9Crg==; path=/; Domain=.discovery.co.za
Set-Cookie: ___utmvmKFuKBaKB=jNjSDoAwxJR; path=/; Max-Age=900
Set-Cookie: ___utmvaKFuKBaKB=loPdiNJ; path=/; Max-Age=900
Set-Cookie: ___utmvbKFuKBaKB=mZj
XMVOIalk: Ftp; path=/; Max-Age=900
X-CDN: Incapsula
X-Iinfo: 14-257794823-257794828 NNNY CT(0 0 0) RT(1578019509121 12) q(0 0 0 -1) r(2 2) U6

Comments

Add extension to Chrome