Your Website Score is

Similar Ranking

28
MOVIERULZ | WATCH BOLLYWOOD AND HOLLYWOOD FULL MOVIES ONLINE---
3movierulz.mx
28
SCI-HUB: УСТРАНЯЯ ПРЕГРАДЫ НА ПУТИ РАСПРОСТРАНЕНИЯ ЗНАНИЙ
sci-hub.tw
28
FRESHERSLIVE - EXCLUSIVE JOB PORTAL FOR FRESHERS IN INDIA
fresherslive.com
28
DIZI ATV’DE IZLENIR
atv.com.tr
28
PREMIUM &--- BOOTSTRAP ADMIN TEMPLATE - PIXINVENT
pixinvent.com
28
ШКОЛА ТЕХНИК НАРУТО: ЛУЧШЕ УМЕРЕТЬ СРАЖАЯСЬ, ЧЕМ БЕЗДЕЙСТВОВАТЬ
jut.su
28
404 NOT FOUND
searchnewworld.com

Latest Sites

19
SEU LEITOR ONLINE DE MANHWAS, MANHUAS E WEBCOMICS YURI | YURIVERSO
yuri.live
27
AMY-SCANS | FILMES, SÉRIES, DORAMAS, ---S, OVA'S, LIVROS, MANGÁS E COMICS COM CONTEÚDO LÉSBICO
amyscans.com
19
HOME PAGE - PAUL OZYZNIEWSKI PORTFOLIO
paulthedeveloper.com
19
HOMEPAGE - THINKING THROUGH
dev.thinkingthrough.com
18

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

28 hirunews.lk Last Updated: 7 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 31%
Best Practices Desktop Score 38%
SEO Desktop Score 90%
Progressive Web App Desktop Score 12%
Performance Mobile Score 22%
Best Practices Mobile Score 46%
SEO Mobile Score 89%
Progressive Web App Mobile Score 15%
Page Authority Authority 44%
Domain Authority Domain Authority 57%
Moz Rank 4.4/10
Bounce Rate Rate 0%
Charset Encoding
Great, language/character encoding is specified: UTF-8
Title Tag 179 Characters
HIRU NEWS OFFICIAL WEB SITE|MOST VISITED WEBSITE IN SRI LANKA|SRI LANKA NEWS|NEWS SRI LANKA|ONLINE ENGLISH NEWS|BREAKING ENGLISH NEWS|HIRU TV NEWS|A RAYYNOR SILVA HOLDINGS COMPANY
Meta Description 213 Characters
Hiru News Most visited website in Sri Lanka,Sri Lanka Latest news updates from Sri Lanka.Sri Lanka News updates and discussions. Welcome to the No1 online news Site for Sri Lankans.A Rayynor Silva Holdings Company
Effective URL 22 Characters
http://www.hirunews.lk
Excerpt Page content
Hiru News Official Web Site|Most visited website in Sri Lanka|Sri Lanka News|News Sri Lanka|Online English News|Breaking English News|Hiru TV News|A Rayynor Silva Holdings Company ...
Keywords Cloud Density
views48 share42 december38 more28 read27 comments20 monday20 news18 embassy9 swiss9
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
views 48
share 42
december 38
more 28
read 27
comments 20
monday 20
news 18
embassy 9
swiss 9
Google Preview Your look like this in google search result
HIRU NEWS OFFICIAL WEB SITE|MOST VISITED WEBSITE IN SRI LANK
http://www.hirunews.lk
Hiru News Most visited website in Sri Lanka,Sri Lanka Latest news updates from Sri Lanka.Sri Lanka News updates and discussions. Welcome to the No1 on
Robots.txt File Detected
Sitemap.xml File No Found
Page Size Code & Text Ratio
Document Size: ~124.95 KB
Code Size: ~87.58 KB
Text Size: ~37.37 KB Ratio: 29.91%

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
Does not use HTTPS 179 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 29 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 510 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,203 KB
Optimized images load faster and consume less cellular data
Enable text compression Potential savings of 306 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 380 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 260 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Reduce JavaScript execution time 3.9 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 4,786 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 3,986 KB
Serve images that are appropriately-sized to save cellular data and improve load time
Speed Index 3.5 s
Speed Index shows how quickly the contents of a page are visibly populated
First CPU Idle 7.9 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 12,021 KB
Large network payloads cost users real money and are highly correlated with long load times
Minimize main-thread work 7.3 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.8 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 7 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Avoid chaining critical requests 26 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,553 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 5 KB
Minifying JavaScript files can reduce payload sizes and script parse time
First Meaningful Paint 1.0 s
First Meaningful Paint measures when the primary content of a page is visible
Keep request counts low and transfer sizes small 604 requests • 12,021 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 341 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 154 resources found
A long cache lifetime can speed up repeat visits to your page
Max Potential First Input Delay 140 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task
Time to Interactive 13.7 s
Time to interactive is the amount of time it takes for the page to become fully interactive
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 61.9 s
A fast page load over a cellular network ensures a good mobile user experience
Estimated Input Latency 30 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 5 KB
Minifying CSS files can reduce network payload sizes
Remove unused CSS Potential savings of 154 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 3,163 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

Mobile Screenshot
Total Blocking Time 3,980 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Reduce JavaScript execution time 15.2 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 5,615 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 15.1 s
Speed Index shows how quickly the contents of a page are visibly populated
First CPU Idle 29.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).
Avoid enormous network payloads Total size was 10,010 KB
Large network payloads cost users real money and are highly correlated with long load times
Minimize main-thread work 27.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 2.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 7 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Avoid chaining critical requests 22 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,412 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 5 KB
Minifying JavaScript files can reduce payload sizes and script parse time
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 438 requests • 10,010 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 341 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 133 resources found
A long cache lifetime can speed up repeat visits to your page
Max Potential First Input Delay 1,160 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task
Time to Interactive 54.3 s
Time to interactive is the amount of time it takes for the page to become fully interactive
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 54.3 s
A fast page load over a cellular network ensures a good mobile user experience
First Contentful Paint (3G) 5086 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 540 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 5 KB
Minifying CSS files can reduce network payload sizes
Tap targets are not sized appropriately 81% 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 89.54% 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 111 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,976 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 189 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 35 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 90 ms
Time To First Byte identifies the time at which your server sends a response
Eliminate render-blocking resources Potential savings of 2,440 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 262 KB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes
Efficiently encode images Potential savings of 1,168 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 5,000 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
Connection: Keep-Alive
Set-Cookie: PHPSESSID=cu7tagtlq0hqmar3kdm3ek27p4; path=/
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
Content-Type: text/html; charset=UTF-8
Date: Tue, 10 Dec 2019 03:01:49 GMT
Server: LiteSpeed
Vary: User-Agent
DNS Records DNS Resource Records associated with a hostname
View DNS Records

Comments

Add extension to Chrome