Your Website Score is

Similar Ranking

12
링크프라이스 - 대한민국 제휴마케팅의 강자
linkprice.com
12
LORDFILM.TV - СМОТРЕТЬ ФИЛЬМЫ ОНЛАЙН В ХОРОШЕМ КАЧЕСТВЕ БЕСПЛАТНО
lordfilm5.tv
12
رهام داتک
datak.ir
12
智佳科技网上解放碑,重庆互联网经济大数据监测分析中心,专业从事AI人工智能,数据挖掘,VR虚拟现实,智能硬件,服务机器人,网络营销,360搜索推广,微博,微信,今日头条等新媒体推广,代运营,域名注册,网站备案
cqhot.cn
12
| WWW.GRANDARS.RU
grandars.ru
12
九酷音乐网|好听的歌|网络歌曲|DJ舞曲|流行歌曲大全
9ku.com
12
TELEAMAZONAS - NOTICIAS DE ECUADOR E INTERNACIONALES AL INSTANTE
teleamazonas.com

Latest Sites

76
FACEBOOK - LOG IN OR SIGN UP
facebook.com
9
FREE ---, ---, TUBE VIDEOS, --- PICS, --- IN ---O MOVIES - XNXX.COM
xnxx.com
28
LITECOIN (LTC) MINING POOL - HOME
ltcminer.com
14
EARN $1000 AND MORE PER DAY!
newcrypto.world
40
İSTANBUL SPOR ENVANTERI | İBB DIRECTORATE OF YOUTH AND SPORTS
sporenvanteri.ibb.istanbul
19
FREEMINING - START--- BITCOIN CLOUD MINING & EARN--- BTC EVERY HOUR
freemining.club
19
MININGCOMPANY.LTD - CLOUD MINING FARMA
miningcompany.ltd

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

12 lankadeepa.lk Last Updated: 12 months

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

Desktop

Mobile

Performance Desktop Score 17%
Best Practices Desktop Score 38%
SEO Desktop Score 80%
Progressive Web App Desktop Score 12%
Performance Mobile Score 2%
Best Practices Mobile Score 38%
SEO Mobile Score 82%
Progressive Web App Mobile Score 11%
Page Authority Authority 0%
Domain Authority Domain Authority 0%
Moz Rank 0.0/10
Bounce Rate Rate 0%
Charset Encoding
Great, language/character encoding is specified: UTF-8
Title Tag 17 Characters
LANKADEEPA ONLINE
Meta Description 173 Characters
Lankadeepa.lk – Sri Lanka 24 Hours Sinhala Breaking News : News, video news, Latest News Hot news,Goship ,Politics, Video, Finance, Business, Sports, Entertainment, Travel.
Effective URL 24 Characters
http://www.lankadeepa.lk
Excerpt Page content
Lankadeepa Online ...
Google Preview Your look like this in google search result
LANKADEEPA ONLINE
http://www.lankadeepa.lk
Lankadeepa.lk – Sri Lanka 24 Hours Sinhala Breaking News : News, video news, Latest News Hot news,Goship ,Politics, Video, Finance, Business, Sports,
Robots.txt File Detected
Sitemap.xml File Detected
Page Size Code & Text Ratio
Document Size: ~347.84 KB
Code Size: ~235.97 KB
Text Size: ~111.87 KB Ratio: 32.16%

Estimation Traffic and Earnings

Only Registered Users

Sign up for see all features and reviews about this site

Login

Desktop

Desktop Screenshot
Minify CSS Potential savings of 36 KB
Minifying CSS files can reduce network payload sizes
Remove unused CSS Potential savings of 529 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 2,822 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
Does not use HTTPS 320 insecure requests found
All sites should be protected with HTTPS, even ones that don't handle sensitive data. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs
User Timing marks and measures 27 user timings
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences
Server response times are low (TTFB) Root document took 150 ms
Time To First Byte identifies the time at which your server sends a response
Eliminate render-blocking resources Potential savings of 1,080 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 1,246 KB
Optimized images load faster and consume less cellular data
Enable text compression Potential savings of 1,846 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 280 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 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 2.0 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 3,118 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
Properly size images Potential savings of 1,569 KB
Serve images that are appropriately-sized to save cellular data and improve load time
Speed Index 4.5 s
Speed Index shows how quickly the contents of a page are visibly populated
First CPU Idle 6.0 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 11,943 KB
Large network payloads cost users real money and are highly correlated with long load times
Minimize main-thread work 4.1 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
First Contentful Paint 1.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 8 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Avoid chaining critical requests 18 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 3,089 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)
Minify JavaScript Potential savings of 165 KB
Minifying JavaScript files can reduce payload sizes and script parse time
First Meaningful Paint 1.9 s
First Meaningful Paint measures when the primary content of a page is visible
Keep request counts low and transfer sizes small 443 requests • 11,943 KB
To set budgets for the quantity and size of page resources, add a budget.json file
Use video formats for animated content Potential savings of 212 KB
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
Serve static assets with an efficient cache policy 98 resources found
A long cache lifetime can speed up repeat visits to your page
Max Potential First Input Delay 210 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task
Time to Interactive 9.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 9 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 51.1 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

Mobile

Mobile Screenshot
Total Blocking Time 2,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 9.5 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 3,232 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
Properly size images Potential savings of 83 KB
Serve images that are appropriately-sized to save cellular data and improve load time
Speed Index 22.2 s
Speed Index shows how quickly the contents of a page are visibly populated
First CPU Idle 11.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).
Avoid enormous network payloads Total size was 11,243 KB
Large network payloads cost users real money and are highly correlated with long load times
Minimize main-thread work 17.1 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
First Contentful Paint 8.6 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 8 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Avoid chaining critical requests 18 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 3,104 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)
Minify JavaScript Potential savings of 165 KB
Minifying JavaScript files can reduce payload sizes and script parse time
First Meaningful Paint 9.4 s
First Meaningful Paint measures when the primary content of a page is visible
Keep request counts low and transfer sizes small 425 requests • 11,243 KB
To set budgets for the quantity and size of page resources, add a budget.json file
Use video formats for animated content Potential savings of 279 KB
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
Serve static assets with an efficient cache policy 89 resources found
A long cache lifetime can speed up repeat visits to your page
Max Potential First Input Delay 560 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task
Time to Interactive 49.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 9 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 49.0 s
A fast page load over a cellular network ensures a good mobile user experience
First Contentful Paint (3G) 18466 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
Estimated Input Latency 290 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
Minify CSS Potential savings of 36 KB
Minifying CSS files can reduce network payload sizes
Tap targets are not sized appropriately 94% 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 80.71% 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 532 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 2,143 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
Does not use HTTPS 307 insecure requests found
All sites should be protected with HTTPS, even ones that don't handle sensitive data. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs
User Timing marks and measures 27 user timings
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences
Server response times are low (TTFB) Root document took 80 ms
Time To First Byte identifies the time at which your server sends a response
Eliminate render-blocking resources Potential savings of 5,280 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 1,159 KB
Optimized images load faster and consume less cellular data
Enable text compression Potential savings of 1,846 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,370 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 200 OK
Content-Type: text/html; charset=UTF-8
Connection: keep-alive
Access-Control-Allow-Origin: http://www.saaravita.lk
Cache-Control: max-age=61
Cache-Control: public
Date: Wed, 18 Dec 2019 17:00:49 GMT
Expires: Wed, 18 Dec 2019 17:01:50 GMT
Last-Modified: Wed, 18 Dec 2019 16:59:56 GMT
Pragma: public
Server: nginx/1.14.1
X-Cache: Hit from cloudfront
Via: 1.1 7c9d2cffb8d1fe464e9f78e42af1b34d.cloudfront.net (CloudFront)
X-Amz-Cf-Pop: IAD79-C3
X-Amz-Cf-Id: KHZWeSb-8hdoxht0xALS_WEYfZRSzzYRVIfh4I4gA-MrVMx9J_mKBQ==
Age: 5
DNS Records DNS Resource Records associated with a hostname
View DNS Records

Comments

Add extension to Chrome