Your Website Score is

Similar Ranking

31
GYMBEAM - OBCHOD S DOPLNKAMI VÝŽIVY PRE ŠPORTOVCOV
gymbeam.sk
31
VFILMES
vfilmes.net
31
// KRNL.TO
krnl.to
31
TIKTOK DOWNLOADER - DOWNLOAD VIDEO TIKTOK WITHOUT WATERMARK - SNAPTIK
ssnaptik.app
31
PAISE KA FUNDA - LEARN TO EARN, SAVE & BUDGET
techinsights.live
31
DOOR HANDLE COMPANY | DOOR HANDLE & DOOR FURNITURE SPECIALISTS
doorhandlecompany.co.uk
31
CLUB BÀSQUET VILATORRADA BLOG - CLUB ESPORTIU AMATEUR DE BÀSQUET
cbvilatorrada.cat

Latest Sites

2
YOUTUBE
youtu.be
56
EDUFILTER – SEARCH AND FILTER EDUCATIONAL YOUTUBE VIDEOS WITH AI
edufilter.github.io
99
YOUTUBE
m.youtube.com
9
PIXAI - AI ART GENERATOR | CREATE STUNNING ANIME AI ART
pixai.art
26
CRAZED COMMON JOE
common-joe.com

Top Technologies

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

31 pridma.netlify.app Last Updated: 3 weeks

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

Desktop

Mobile

Performance Desktop Score 72%
Best Practices Desktop Score 100%
SEO Desktop Score 100%
Performance Mobile Score 58%
Best Practices Mobile Score 100%
SEO Mobile Score 100%
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 97 Characters
INDUNIL PRIDMA CHATHURANGA: MULTIFACETED ARTIST & OWNER OF PRIDMA INDUSTRIES
Meta Description 100 Characters
Explore the world of Indunil Pridma Chathuranga, a multifaceted artist & owner of PRIDMA Industries.
Effective URL 26 Characters
https://pridma.netlify.app
Excerpt Page content
Indunil Pridma Chathuranga: Multifaceted Artist & Owner of Pridma Industries ...
Keywords Cloud Density
pridma5 stories2 films2 music2 reserved1 rights1 services1 industries1 about1
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
pridma 5
stories 2
films 2
music 2
reserved 1
rights 1
services 1
industries 1
about 1
Google Preview Your look like this in google search result
INDUNIL PRIDMA CHATHURANGA: MULTIFACETED ARTIST & OW
https://pridma.netlify.app
Explore the world of Indunil Pridma Chathuranga, a multifaceted artist & owner of PRIDMA Industries.
Robots.txt File No Found
Sitemap.xml File Detected
Page Size Code & Text Ratio
Document Size: ~35.14 KB
Code Size: ~3.83 KB
Text Size: ~31.31 KB Ratio: 89.11%

Social Data

Estimation Traffic and Earnings

8
Unique Visits
Daily
14
Pages Views
Daily
$0
Income
Daily
224
Unique Visits
Monthly
399
Pages Views
Monthly
$0
Income
Monthly
2,592
Unique Visits
Yearly
4,704
Pages Views
Yearly
$0
Income
Yearly

Desktop

Desktop Screenshot
Avoid non-composited animations 1 animated element found
Animations which are not composited can be janky and increase CLS
Avoid chaining critical requests 4 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
Total Blocking Time 90 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Reduce unused CSS Est savings of 14 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity
Reduce unused JavaScript Est savings of 114 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity
Eliminate render-blocking resources Est savings of 290 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Largest Contentful Paint 2.7 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Serve static assets with an efficient cache policy 12 resources found
A long cache lifetime can speed up repeat visits to your page
Cumulative Layout Shift 0.231
Cumulative Layout Shift measures the movement of visible elements within the viewport
Font display Est savings of 470 ms
Consider setting [font-display](https://developer.chrome.com/blog/font-display) to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with [font metric overrides](https://developer.chrome.com/blog/font-fallbacks).
Efficiently encode images Est savings of 8 KiB
Optimized images load faster and consume less cellular data
Time to Interactive 2.7 s
Time to Interactive is the amount of time it takes for the page to become fully interactive
Max Potential First Input Delay 120 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Minimize third-party usage Third-party code blocked the main thread for 90 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
Minimizes main-thread work 0.9 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 3,510 KiB
Large network payloads cost users real money and are highly correlated with long load times
Render blocking requests Est savings of 390 ms
Requests are blocking the page's initial render, which may delay LCP
Largest Contentful Paint element 2,710 ms
This is the largest contentful element painted within the viewport
Speed Index 1.4 s
Speed Index shows how quickly the contents of a page are visibly populated
Avoid large layout shifts 15 layout shifts found
These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to [windowing](https://web.dev/articles/cls#what_is_cls)
Avoid long main-thread tasks 2 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
JavaScript execution time 0.3 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Initial server response time was short Root document took 90 ms
Keep the server response time for the main document short because all other requests depend on it
First Contentful Paint 0.5 s
First Contentful Paint marks the time at which the first text or image is painted
Avoids an excessive DOM size 215 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)
Server Backend Latencies 20 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
Network Round Trip Times 10 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
Serve images in next-gen formats Est savings of 1,077 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption
Improve image delivery Est savings of 2,489 KiB
Reducing the download time of images can improve the perceived load time of the page and LCP
Use efficient cache lifetimes Est savings of 1,192 KiB
A long cache lifetime can speed up repeat visits to your page

Mobile

Mobile Screenshot
Avoid large layout shifts 15 layout shifts found
These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to [windowing](https://web.dev/articles/cls#what_is_cls)
Avoid enormous network payloads Total size was 3,510 KiB
Large network payloads cost users real money and are highly correlated with long load times
First Contentful Paint 2.3 s
First Contentful Paint marks the time at which the first text or image is painted
Largest Contentful Paint element 14,880 ms
This is the largest contentful element painted within the viewport
Render blocking requests Est savings of 1,660 ms
Requests are blocking the page's initial render, which may delay LCP
Eliminate render-blocking resources Est savings of 1,460 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Largest Contentful Paint 14.9 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
Minimizes main-thread work 0.8 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
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
Cumulative Layout Shift 0.23
Cumulative Layout Shift measures the movement of visible elements within the viewport
Reduce unused CSS Est savings of 14 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity
Use efficient cache lifetimes Est savings of 1,192 KiB
A long cache lifetime can speed up repeat visits to your page
Time to Interactive 15.2 s
Time to Interactive is the amount of time it takes for the page to become fully interactive
Serve static assets with an efficient cache policy 12 resources found
A long cache lifetime can speed up repeat visits to your page
Avoids an excessive DOM size 215 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)
Initial server response time was short Root document took 90 ms
Keep the server response time for the main document short because all other requests depend on it
Avoid long main-thread tasks 2 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
JavaScript execution time 0.3 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Speed Index 4.4 s
Speed Index shows how quickly the contents of a page are visibly populated
Serve images in next-gen formats Est savings of 1,220 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption
Reduce unused JavaScript Est savings of 114 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity
Server Backend Latencies 20 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
Total Blocking Time 50 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Max Potential First Input Delay 80 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Avoid non-composited animations 1 animated element found
Animations which are not composited can be janky and increase CLS
Efficiently encode images Est savings of 8 KiB
Optimized images load faster and consume less cellular data
Improve image delivery Est savings of 2,425 KiB
Reducing the download time of images can improve the perceived load time of the page and LCP
Font display Est savings of 300 ms
Consider setting [font-display](https://developer.chrome.com/blog/font-display) to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with [font metric overrides](https://developer.chrome.com/blog/font-fallbacks).
Avoid chaining critical requests 4 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
Minimize third-party usage Third-party code blocked the main thread for 50 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

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
Warning! Your title is not optimized
Description Website
Congratulations! Your description is optimized
Robots.txt
Warning! Your site not have a robots.txt file
Sitemap.xml
Congratulations! We've 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
Warning! Domain Authority of your website is slow. It is good to have domain authority more than 25.
GZIP Compress
Warning! Your site not is compressed, this can make slower response for the visitors
Favicon
Warning! Your site not have a favicon
Broken Links
Congratulations! You not have broken links View links

Alexa Rank

99,999,999

Global Rank

99,999,999

-
Traffic
Search

Domain Available

Domain (TDL) and Typo Status
pridma.netlify.co Already Registered
pridma.netlify.us Available
pridma.netlify.com Already Registered
pridma.netlify.org Available
pridma.netlify.net Already Registered
pidma.netlify.app Already Registered
lridma.netlify.app 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
Accept-Ranges: bytes
Age: 1
Cache-Control: public,max-age=0,must-revalidate
Cache-Status: "Netlify Edge"; hit
Content-Encoding: gzip
Content-Length: 8049
Content-Type: text/html; charset=UTF-8
Date: Mon, 11 Aug 2025 02:04:40 GMT
Etag: "90dafa6df53250f2156a31e1cfa138a9-ssl-df"
Server: Netlify
Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
Vary: Accept-Encoding
X-Nf-Request-Id: 01K2BDYSRVR80ZASE6DQQ7W9SP
DNS Records DNS Resource Records associated with a hostname
View DNS Records