Your Website Score is

Similar Ranking

41
MATT BOYLE CHINESE MEDICINE & ACUPUNCTURE
mattboyle.com.au
41
HOME - DRO-EZ
dro-ez.com
41
A ARTE DE AMAR – PROJETO OFICINAS DE ARTES PLÁSTICAS NEIL KERMAN
aartedeamar.org.br
41
YAHOO RECHERCHE DE VIDÉOS
fr.video.search.yahoo.com
41
JESUS-QC ✨????
jesusqc.es
41
COMPETITOR RESEARCH & ANALYSIS AGENCY - COMPETITIVE INSIGHT
competitiveinsight.io
41

Latest Sites

19
CREATIVE DESIGN & MARKETING SERVICES | IBS AGENCY
ibsagency.net
19
SENILE TEAM DEV LOG
senileteam.com
14
BOXHERO.IN
boxhero.in
21
HUYCHESS
huychess.sbs
96
YOUTUBE
youtu.be
9
YOUTUBE
youtube.com
19
YUPPOW - FREE HD MOVIES AND TV SHOWS STREAMING ONLINE
yuppow.org

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

41 neelshha.com Last Updated: 1 month

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

Desktop

Mobile

Performance Desktop Score 99%
Best Practices Desktop Score 100%
SEO Desktop Score 100%
Performance Mobile Score 93%
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 21 Characters
NEEL SHAH | PORTFOLIO
Meta Description 39 Characters
Computer science student and developer.
Effective URL 24 Characters
https://www.neelshha.com
Excerpt Page content
Neel Shah | Portfolio Hi, I'm NeelI'm a compute...
Keywords Cloud Density
vinyl3 aiotize3 code2 focus2 july2 github1 twitter1 projects1 towards1 mail1
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
vinyl 3
aiotize 3
code 2
focus 2
july 2
github 1
twitter 1
projects 1
towards 1
mail 1
Google Preview Your look like this in google search result
NEEL SHAH | PORTFOLIO
https://www.neelshha.com
Computer science student and developer.
Robots.txt File Detected
Sitemap.xml File No Found
Page Size Code & Text Ratio
Document Size: ~11.21 KB
Code Size: ~9.98 KB
Text Size: ~1.23 KB Ratio: 10.97%

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
JavaScript execution time 0.0 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Avoids enormous network payloads Total size was 150 KiB
Large network payloads cost users real money and are highly correlated with long load times
Minimize third-party usage Third-party code blocked the main thread for 0 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 0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Avoid chaining critical requests 3 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
Avoids an excessive DOM size 86 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)
Reduce unused JavaScript Est savings of 31 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity
Largest Contentful Paint element 720 ms
This is the largest contentful element painted within the viewport
Max Potential First Input Delay 20 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
First Contentful Paint 0.7 s
First Contentful Paint marks the time at which the first text or image is painted
Serve static assets with an efficient cache policy 1 resource found
A long cache lifetime can speed up repeat visits to your page
Use efficient cache lifetimes Est savings of 3 KiB
A long cache lifetime can speed up repeat visits to your page
Initial server response time was short Root document took 100 ms
Keep the server response time for the main document short because all other requests depend on it
Eliminate render-blocking resources Est savings of 420 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Speed Index 0.7 s
Speed Index shows how quickly the contents of a page are visibly populated
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
Render blocking requests Est savings of 380 ms
Requests are blocking the page's initial render, which may delay LCP
Time to Interactive 0.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
Minimizes main-thread work 0.2 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Largest Contentful Paint 0.7 s
Largest Contentful Paint marks the time at which the largest text or image is painted

Mobile

Mobile Screenshot
Render blocking requests Est savings of 1,220 ms
Requests are blocking the page's initial render, which may delay LCP
JavaScript execution time 0.1 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Largest Contentful Paint 2.6 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Speed Index 2.9 s
Speed Index shows how quickly the contents of a page are visibly populated
Avoid chaining critical requests 3 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
Use efficient cache lifetimes Est savings of 3 KiB
A long cache lifetime can speed up repeat visits to your page
Eliminate render-blocking resources Est savings of 1,370 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Initial server response time was short Root document took 70 ms
Keep the server response time for the main document short because all other requests depend on it
Time to Interactive 2.6 s
Time to Interactive is the amount of time it takes for the page to become fully interactive
Max Potential First Input Delay 20 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
First Contentful Paint 2.6 s
First Contentful Paint marks the time at which the first text or image is painted
Minimize third-party usage Third-party code blocked the main thread for 0 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
Reduce unused JavaScript Est savings of 28 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity
Minimizes main-thread work 0.2 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Avoids enormous network payloads Total size was 150 KiB
Large network payloads cost users real money and are highly correlated with long load times
Largest Contentful Paint element 2,590 ms
This is the largest contentful element painted within the viewport
Avoids an excessive DOM size 85 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 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
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
Serve static assets with an efficient cache policy 1 resource found
A long cache lifetime can speed up repeat visits to your page
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
Total Blocking Time 0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds

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
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
Congratulations! Your website appears to 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
neelshha.co Available
neelshha.us Available
neelshha.com Already Registered
neelshha.org Available
neelshha.net Available
nelshha.com Available
heelshha.com Available
ueelshha.com Available

Information Server

Response Header HTTP headers carry information about the client browser, the requested page and the server
HTTP/1.1 200 OK
Date: Sat, 30 Aug 2025 17:56:10 GMT
Content-Type: text/html; charset=utf-8
Connection: keep-alive
access-control-allow-origin: *
Age: 820510
Cache-Control: public, max-age=0, must-revalidate
content-disposition: inline
Nel: {"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}
last-modified: Thu, 21 Aug 2025 06:01:00 GMT
Server: cloudflare
strict-transport-security: max-age=63072000
x-vercel-cache: HIT
x-vercel-id: cle1::7mxf8-1756576570831-1885c0df8429
Report-To: {"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=08%2BJRLUFAyBl%2Bi%2Bd96gvZfqOHuty6A9Hpuqj5MfNjRXmk02vtEeQzSQlCy9g1eGH7jwkYJX%2FpOVNwd0DJohAzvZoaEPRdiih0fOj4F8c"}]}
cf-cache-status: DYNAMIC
Content-Encoding: gzip
CF-RAY: 977629cf3dfaa1d8-YYZ
alt-svc: h3=":443"; ma=86400
DNS Records DNS Resource Records associated with a hostname
View DNS Records