Your Website Score is

Latest Sites

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

1 drmanuelvelezm.site Last Updated: 1 year

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

Desktop

Mobile

Performance Desktop Score 97%
Best Practices Desktop Score 82%
SEO Desktop Score 73%
Performance Mobile Score 71%
Best Practices Mobile Score 83%
SEO Mobile Score 73%
Page Authority Authority 0%
Domain Authority Domain Authority 0%
Moz Rank 0.0/10
Bounce Rate Rate 0%
Title Tag 0 Characters
NO DATA
Meta Description 0 Characters
NO DATA
Effective URL 26 Characters
http://drmanuelvelezm.site
Google Preview Your look like this in google search result
drmanuelvelezm.site
http://drmanuelvelezm.site
Robots.txt File Detected
Sitemap.xml File Detected
Page Size Code & Text Ratio
Document Size: ~114 B
Code Size: ~58 B
Text Size: ~56 B Ratio: 49.12%

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.2 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Eliminate render-blocking resources Potential savings of 310 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Server Backend Latencies 10 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
Serve static assets with an efficient cache policy 5 resources found
A long cache lifetime can speed up repeat visits to your page
Largest Contentful Paint 1.3 s
Largest Contentful Paint marks the time at which the largest text or image is painted
First Contentful Paint 0.6 s
First Contentful Paint marks the time at which the first text or image is painted
Total Blocking Time 20 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
robots.txt is not valid 1 error found
If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed
Avoid long main-thread tasks 1 long task found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
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
Largest Contentful Paint element 1,260 ms
This is the largest contentful element painted within the viewport
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 multiple page redirects Potential savings of 200 ms
Redirects introduce additional delays before the page can be loaded
Minimizes main-thread work 0.4 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 20 ms
Keep the server response time for the main document short because all other requests depend on it
Reduce unused JavaScript Potential savings of 178 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity
Does not use HTTPS 2 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 served over 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
Avoids an excessive DOM size 28 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)
First Meaningful Paint 0.6 s
First Meaningful Paint measures when the primary content of a page is visible
Minimize third-party usage Third-party code blocked the main thread for 20 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
Time to Interactive 1.0 s
Time to Interactive is the amount of time it takes for the page to become fully interactive
Avoids enormous network payloads Total size was 377 KiB
Large network payloads cost users real money and are highly correlated with long load times
Speed Index 0.8 s
Speed Index shows how quickly the contents of a page are visibly populated

Mobile

Mobile Screenshot
Server Backend Latencies 10 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
Does not use HTTPS 2 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 served over 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
Initial server response time was short Root document took 20 ms
Keep the server response time for the main document short because all other requests depend on it
Largest Contentful Paint 5.2 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Eliminate render-blocking resources Potential savings of 1,260 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Avoid large layout shifts 1 layout shift 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 4 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
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
Total Blocking Time 280 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
robots.txt is not valid 1 error found
If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed
Avoids enormous network payloads Total size was 376 KiB
Large network payloads cost users real money and are highly correlated with long load times
Cumulative Layout Shift 0.04
Cumulative Layout Shift measures the movement of visible elements within the viewport
Minimizes main-thread work 1.2 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Time to Interactive 5.1 s
Time to Interactive is the amount of time it takes for the page to become fully interactive
Avoids an excessive DOM size 28 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)
Max Potential First Input Delay 350 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
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
Reduce the impact of third-party code Third-party code blocked the main thread for 260 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
Largest Contentful Paint element 5,160 ms
This is the largest contentful element painted within the viewport
Avoid multiple page redirects Potential savings of 810 ms
Redirects introduce additional delays before the page can be loaded
Speed Index 2.5 s
Speed Index shows how quickly the contents of a page are visibly populated
First Meaningful Paint 3.0 s
First Meaningful Paint measures when the primary content of a page is visible
JavaScript execution time 0.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.5 s
First Contentful Paint marks the time at which the first text or image is painted
Reduce unused JavaScript Potential savings of 178 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity
Serve static assets with an efficient cache policy 5 resources found
A long cache lifetime can speed up repeat visits to your page

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
Warning! Your description is not optimized
Robots.txt
Congratulations! Your site 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
Warning! Your page not contain any H1 and H2 headings. H1 and H2 headings help indicate the important topics of your page to search engines
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
drmanuelvelezm.co Available
drmanuelvelezm.us Available
drmanuelvelezm.com Available
drmanuelvelezm.org Available
drmanuelvelezm.net Available
dmanuelvelezm.site Available
ermanuelvelezm.site Available
crmanuelvelezm.site Available

Information Server

Response Header HTTP headers carry information about the client browser, the requested page and the server
HTTP/1.1 405 Method Not Allowed
Server: openresty
Date: Wed, 12 Jun 2024 00:42:15 GMT
Connection: keep-alive
DNS Records DNS Resource Records associated with a hostname
View DNS Records