Your Website Score is

Similar Ranking

31
SHOEKEEPER | THE GREATEST WORDPRESS.COM SITE IN ALL THE LAND!
shoekeeper.wordpress.com
31
NAZARBAGH PALACE
nazarbagh.com
31
FONTMASH - ALL ABOUT FONTS!
fontmash.com
31
ANIMEINDO - PORTAL DOWNLOAD ANIME SUB INDO BATCH
anime-indo.online
31
LAZER BEST - THE BRAND ENERGY
lazerbest.com
31
CHIAKI.VN - MUA SẮM TRỰC TUYẾN GIÁ TỐT
chiaki.vn
31
KANSAS CITY CHIEFS GAME LIVE STREAMING FOOTBALL ONLINE
chiefsgame.net

Latest Sites

90
YOUR ACCESS TO THIS WEBSITE HAS BEEN BLOCKED
fiverr.com
1
ytstv.com Website SEO Rank Analysis by SEOWebsiteRank.com
ytstv.com
9
FILMY4WAP.IN | FILMY4WAP HD MP4 MOVIES DOWNLOAD,NEW BOLLYWOOD MOVIES DOWNLOAD,NEW SOUTH HINDI DUBBED MOVIES,NEW HOLLYWOOD HINDI DUBBED MOVIES,720P MOVIES ,NEW MOVIES SITE,MP4MOVIEZ,MOVIEMAD,JALSHAMOVI
1filmy4wap.in
21
CUM FACE GENERATOR - CREATE FAKE CUMSHOT IMAGES ▻CUM FACE GENERATOR | CREATE FAKE CUMSHOT IMAGES ▻
cumfacegenerator.com
9
flashback.org Website SEO Rank Analysis by SEOWebsiteRank.com
flashback.org
1
edmdl.com Website SEO Rank Analysis by SEOWebsiteRank.com
edmdl.com
8
INICIO - DIBUJOTECNICO.COM
dibujotecnico.com

Top Technologies

Nginx.png
Nginx
Web Servers
Apache.png
Apache
Web Servers
CloudFlare.png
CloudFlare
CDN
Google%20Font%20API.png
Google Font API
Font Scripts
Font%20Awesome.png
Font Awesome
Font Scripts
WordPress.png
WordPress
CMS
Twitter%20Bootstrap.png
Twitter Bootstrap
Web Frameworks
Microsoft.png
Windows Server
Operating Systems

SEO Rank : 31 Website URL: silumina.lk Last Updated: 6 months

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

Estimation Traffic and Earnings

625
Unique Visits
Daily
1,156
Pages Views
Daily
$4
Income
Daily
17,500
Unique Visits
Monthly
32,946
Pages Views
Monthly
$100
Income
Monthly
202,500
Unique Visits
Yearly
388,416
Pages Views
Yearly
$1,056
Income
Yearly

Desktop

Mobile

Performance Desktop Score 25%
Best Practices Desktop Score 57%
SEO Desktop Score 100%
Progressive Web App Desktop Score 11%
Performance Mobile Score 5%
Best Practices Mobile Score 50%
SEO Mobile Score 99%
Progressive Web App Mobile Score 11%

Moz Authority Rank

Page Authority Authority 42%
Domain Authority Domain Authority 36%
Moz Rank 4.2/10
Bounce Rate Rate 0%

Meta Data

Charset Encoding
Great, language/character encoding is specified: UTF-8
Title Tag 48 Characters
සිළුමිණ | ප්‍රථම සතිඅන්ත සිංහල අන්තර්ජාල පුවත්පත
Meta Description 119 Characters
Sri Lanka news, Sri Lanka politics, Sri Lanka government, Sri Lanka business, Sri lanka financial, Sports, Feature News
Effective URL 22 Characters
http://www.silumina.lk
Excerpt Page content
සිළුමිණ | ප්‍රථම සතිඅන්ත සිංහල අන්තර්ජාල පුවත්පත Skip to main content ...
Keywords Cloud Density
ගුවන්8 අවසන්8 ක්‍රිකට්7 පුවත්7 මෙරට7 ශ්‍රී6 මහතා6 ආසාදිතයින්5 ලිපි5 තහනම5
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
ගුවන් 8
අවසන් 8
ක්‍රිකට් 7
පුවත් 7
මෙරට 7
ශ්‍රී 6
මහතා 6
ආසාදිතයින් 5
ලිපි 5
තහනම 5
Google Preview Your look like this in google search result
සිළුමිණ | ප්‍රථම සතිඅන්ත සිංහල අන්තර්ජාල පුවත්පත
http://www.silumina.lk
Sri Lanka news, Sri Lanka politics, Sri Lanka government, Sri Lanka business, Sri lanka financial, Sports, Feature News
Robots.txt File Detected
Sitemap.xml File No Found
Page Size Code & Text Ratio
Document Size: ~141.26 KB
Code Size: ~102.82 KB
Text Size: ~38.44 KB Ratio: 27.22%

Social Data

Delicious Total: 0
Facebook Total: 0
Google Total: 0
Linkedin Total: 0
Pinterest Total: 0
Stumbleupon Total: 0
Tumblr Total: 0
Vk Total: 0

Technologies

PWA - Manifest

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

Desktop

Desktop Screenshot
Avoid enormous network payloads Total size was 8,525 KiB
Large network payloads cost users real money and are highly correlated with long load times
Eliminate render-blocking resources Potential savings of 650 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Defer offscreen images Potential savings of 478 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Efficiently encode images Potential savings of 116 KiB
Optimized images load faster and consume less cellular data
Time to Interactive 7.9 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Avoid large layout shifts 5 elements found
These DOM elements contribute most to the CLS of the page.
Serve static assets with an efficient cache policy 102 resources found
A long cache lifetime can speed up repeat visits to your page
Minify JavaScript Potential savings of 22 KiB
Minifying JavaScript files can reduce payload sizes and script parse time
Avoid serving legacy JavaScript to modern browsers Potential savings of 22 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers
Initial server response time was short Root document took 350 ms
Keep the server response time for the main document short because all other requests depend on it
Avoid chaining critical requests 35 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
Max Potential First Input Delay 280 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Minimize main-thread work 4.8 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Total Blocking Time 550 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Remove unused CSS Potential savings of 346 KiB
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 796 KiB
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
Minify CSS Potential savings of 4 KiB
Minifying CSS files can reduce network payload sizes
Largest Contentful Paint 8.0 s
Largest Contentful Paint marks the time at which the largest text or image is painted
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
Enable text compression Potential savings of 1 KiB
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 600 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
First Meaningful Paint 1.7 s
First Meaningful Paint measures when the primary content of a page is visible
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
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
Avoid an excessive DOM size 984 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)
Does not use HTTPS 101 insecure requests found
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding [mixed content](https://developers.google.com/web/fundamentals/security/prevent-mixed-content/what-is-mixed-content), where some resources are loaded over HTTP despite the initial request being servedover HTTPS. 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
Keep request counts low and transfer sizes small 314 requests • 8,525 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
First CPU Idle 6.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/).
Page load is not fast enough on mobile networks Interactive on simulated mobile network at 40.9 s
A fast page load over a cellular network ensures a good mobile user experience
User Timing marks and measures 14 user timings
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences
Speed Index 2.6 s
Speed Index shows how quickly the contents of a page are visibly populated
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
First Contentful Paint 1.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 4 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Estimated Input Latency 70 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
Avoids large JavaScript libraries with smaller alternatives 0 large libraries found
Large JavaScript libraries can lead to poor performance. Prefer smaller, functionally equivalent libraries to reduce your bundle size
Avoid long main-thread tasks 12 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Cumulative Layout Shift 0.157
Cumulative Layout Shift measures the movement of visible elements within the viewport
Remove unused JavaScript Potential savings of 1,882 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
Properly size images Potential savings of 268 KiB
Serve images that are appropriately-sized to save cellular data and improve load time

Mobile

Mobile Screenshot
Max Potential First Input Delay 1,220 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
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
Remove unused JavaScript Potential savings of 1,916 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
Enable text compression Potential savings of 1 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes
Estimated Input Latency 830 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
Initial server response time was short Root document took 380 ms
Keep the server response time for the main document short because all other requests depend on it
Avoid an excessive DOM size 987 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)
Minimize main-thread work 26.1 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Avoid enormous network payloads Total size was 8,677 KiB
Large network payloads cost users real money and are highly correlated with long load times
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
Keep request counts low and transfer sizes small 336 requests • 8,677 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Avoids large JavaScript libraries with smaller alternatives 0 large libraries found
Large JavaScript libraries can lead to poor performance. Prefer smaller, functionally equivalent libraries to reduce your bundle size
First Meaningful Paint 5.1 s
First Meaningful Paint measures when the primary content of a page is visible
Minify CSS Potential savings of 4 KiB
Minifying CSS files can reduce network payload sizes
User Timing marks and measures 14 user timings
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences
Minify JavaScript Potential savings of 22 KiB
Minifying JavaScript files can reduce payload sizes and script parse time
Reduce the impact of third-party code Third-party code blocked the main thread for 8,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
Avoid long main-thread tasks 20 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Avoid large layout shifts 4 elements found
These DOM elements contribute most to the CLS of the page.
Remove unused CSS Potential savings of 346 KiB
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
Does not use HTTPS 104 insecure requests found
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding [mixed content](https://developers.google.com/web/fundamentals/security/prevent-mixed-content/what-is-mixed-content), where some resources are loaded over HTTP despite the initial request being servedover HTTPS. 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
First CPU Idle 7.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 serving legacy JavaScript to modern browsers Potential savings of 22 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers
Serve static assets with an efficient cache policy 104 resources found
A long cache lifetime can speed up repeat visits to your page
Includes front-end JavaScript libraries with known security vulnerabilities 4 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Speed Index 13.2 s
Speed Index shows how quickly the contents of a page are visibly populated
Reduce JavaScript execution time 15.1 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Cumulative Layout Shift 0.844
Cumulative Layout Shift measures the movement of visible elements within the viewport
Tap targets are not sized appropriately 97% 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
Page load is not fast enough on mobile networks Interactive at 45.7 s
A fast page load over a cellular network ensures a good mobile user experience
Serve images in next-gen formats Potential savings of 796 KiB
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
Defer offscreen images Potential savings of 692 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Avoid chaining critical requests 35 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
Document uses legible font sizes 90.09% 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
Time to Interactive 45.7 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Total Blocking Time 6,910 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
First Contentful Paint 5.1 s
First Contentful Paint marks the time at which the first text or image is painted
Efficiently encode images Potential savings of 116 KiB
Optimized images load faster and consume less cellular data
First Contentful Paint (3G) 10056 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
Largest Contentful Paint 43.4 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Eliminate render-blocking resources Potential savings of 1,900 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Properly size images Potential savings of 20 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
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

Speed And Optimization Tips

Website speed has a huge impact on performance, affecting user experience, conversion rates and even rankings. ‪‬‬By reducing page load-times, users are less likely to get distracted and the search engines are more likely to reward you by ranking you
Title Website
Congratulations! Your title is optimized
Description Website
Congratulations! Your description is optimized
Robots.txt
Congratulations! Your site have a robots.txt file
Sitemap.xml
Warning! Not found a sitemap file for your website
SSL Secure
Congratulations! Your site have Support to HTTPS
Headings
Congratulations! You are using your H1 and H2 tags in your site
Blacklist
Congratulations! Your site is not listed in a blacklist
W3C Validator
Warning! Your site have errors W3C
Accelerated Mobile Pages (AMP)
Warning! Your site not have AMP Version
Domain Authority
Congratulations! Your Domain Authority is good
GZIP Compress
Warning! Your site not is compressed, this can make slower response for the visitors
Favicon
Congratulations! Your website appears to have a favicon.
Broken Links
Warning! You have broken links View links

Alexa Rank

523

Local Rank: LK / Users: 100.0% / PageViews: 100.0%

275,199

Global Rank

Domain Available

Domain (TDL) and Typo Status
silumina.co Already Registered
silumina.us Already Registered
silumina.com Already Registered
silumina.org Already Registered
silumina.net Already Registered
slumina.lk Already Registered
wilumina.lk Already Registered
xilumina.lk Already Registered

Information Server

Response Header HTTP headers carry information about the client browser, the requested page and the server
HTTP/1.1 200 OK
Date: Tue, 15 Sep 2020 00:19:26 GMT
Content-Type: text/html; charset=utf-8
Connection: keep-alive
Set-Cookie: __cfduid=d53fdbab10fb240a66d01948024075f551600129166; expires=Thu, 15-Oct-20 00:19:26 GMT; path=/; domain=.silumina.lk; HttpOnly; SameSite=Lax
X-Drupal-Cache: HIT
Content-Language: si
X-Frame-Options: SAMEORIGIN
Link: ; rel="canonical",; rel="shortlink",; rel="shortcut icon"
Cache-Control: public, max-age=1800
Last-Modified: Mon, 14 Sep 2020 23:18:27 GMT
Expires: Sun, 19 Nov 1978 05:00:00 GMT
Vary: Cookie,Accept-Encoding
CF-Cache-Status: DYNAMIC
cf-request-id: 0530ba82d70000991d26a5c200000001
Server: cloudflare
CF-RAY: 5d2e2d17bddb991d-LAX
Content-Encoding: gzip

View DNS Records

DNS Records DNS Resource Records associated with a hostname
Type Name Value Class TTL

Comments

silumina.lk Stats By Traffic Tips Alexa Server Meta Authority Technologies Pagespeed Pagespeed Stats Social Domain Available
Add extension to Chrome