Your Website Score is

Similar Ranking

2
CANVA
canva.com
2
MSN
msn.com
2
---HUBER.CO - THIS WEBSITE IS FOR SALE! - ---HUBER RESOURCES AND INFORMATION.
beegcom.club
2
JUST A MOMENT...
kinks.ca

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

2 carlosreyesdop.com Last Updated: 2 months

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

Desktop

Mobile

Performance Desktop Score 100%
Best Practices Desktop Score 82%
SEO Desktop Score 92%
Performance Mobile Score 92%
Best Practices Mobile Score 83%
SEO Mobile Score 92%
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 12 Characters
CARLOS REYES
Meta Description 122 Characters
Director of Photography based in Mexico and NYC. Over 5 years of experience in music videos, commercials, and short films.
Effective URL 25 Characters
http://carlosreyesdop.com
Excerpt Page content
Carlos Reyes Work NYC Demo Reel Docena en escena Self Fulfilling Prophecy In the Bronx Se...
Keywords Cloud Density
breteau6 bronx6 foundation6 unreal3 production3 footage3 docena3 clothing3 ackerman3 flowers3
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
breteau 6
bronx 6
foundation 6
unreal 3
production 3
footage 3
docena 3
clothing 3
ackerman 3
flowers 3
Google Preview Your look like this in google search result
CARLOS REYES
http://carlosreyesdop.com
Director of Photography based in Mexico and NYC. Over 5 years of experience in music videos, commercials, and short films.
Robots.txt File Detected
Sitemap.xml File Detected
Page Size Code & Text Ratio
Document Size: ~39.96 KB
Code Size: ~33.48 KB
Text Size: ~6.48 KB Ratio: 16.21%

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 chaining critical requests 7 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
Reduce unused JavaScript Est savings of 47 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity
Properly size images Est savings of 1,352 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Initial server response time was short Root document took 60 ms
Keep the server response time for the main document short because all other requests depend on it
Avoids enormous network payloads Total size was 2,143 KiB
Large network payloads cost users real money and are highly correlated with long load times
Eliminate render-blocking resources Est savings of 0 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Document request latency Est savings of 110 ms
Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.
Avoid serving legacy JavaScript to modern browsers Est savings of 0 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile [Baseline](https://web.dev/baseline) features, unless you know you must support legacy browsers
Render blocking requests Est savings of 80 ms
Requests are blocking the page's initial render, which may delay LCP
Serve images in next-gen formats Est savings of 1,616 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption
Minimizes main-thread work 0.1 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Does not use HTTPS 1 insecure request 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
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
Total Blocking Time 0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Avoids an excessive DOM size 256 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)
Improve image delivery Est savings of 1,540 KiB
Reducing the download time of images can improve the perceived load time of the page and LCP
Largest Contentful Paint 0.7 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Enable text compression Est savings of 34 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes
Font display Est savings of 40 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 1,114 KiB
Optimized images load faster and consume less cellular data
Use efficient cache lifetimes Est savings of 85 KiB
A long cache lifetime can speed up repeat visits to your page
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
Minify CSS Est savings of 15 KiB
Minifying CSS files can reduce network payload sizes
Avoid multiple page redirects Est savings of 190 ms
Redirects introduce additional delays before the page can be loaded
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
Serve static assets with an efficient cache policy 21 resources found
A long cache lifetime can speed up repeat visits to your page
First Contentful Paint 0.6 s
First Contentful Paint marks the time at which the first 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
Minify JavaScript Est savings of 33 KiB
Minifying JavaScript files can reduce payload sizes and script parse time
Reduce unused CSS Est savings of 33 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity
Speed Index 0.7 s
Speed Index shows how quickly the contents of a page are visibly populated
Time to Interactive 0.7 s
Time to Interactive is the amount of time it takes for the page to become fully interactive
Largest Contentful Paint element 690 ms
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

Mobile

Mobile Screenshot
Avoid multiple page redirects Est savings of 630 ms
Redirects introduce additional delays before the page can be loaded
Minify JavaScript Est savings of 33 KiB
Minifying JavaScript files can reduce payload sizes and script parse time
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
Eliminate render-blocking resources Est 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
First Contentful Paint 2.5 s
First Contentful Paint marks the time at which the first text or image is painted
Use efficient cache lifetimes Est savings of 85 KiB
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 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
Speed Index 2.5 s
Speed Index shows how quickly the contents of a page are visibly populated
Avoid chaining critical requests 7 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 50 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
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
Font display Est savings of 80 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).
Reduce unused JavaScript Est savings of 47 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity
Avoid serving legacy JavaScript to modern browsers Est savings of 0 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile [Baseline](https://web.dev/baseline) features, unless you know you must support legacy browsers
Does not use HTTPS 1 insecure request 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
Render blocking requests Est savings of 600 ms
Requests are blocking the page's initial render, which may delay LCP
Reduce unused CSS Est savings of 30 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity
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
Serve static assets with an efficient cache policy 23 resources found
A long cache lifetime can speed up repeat visits to your page
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
Time to Interactive 2.8 s
Time to Interactive is the amount of time it takes for the page to become fully interactive
Minimizes main-thread work 0.7 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
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
Efficiently encode images Est savings of 1,193 KiB
Optimized images load faster and consume less cellular data
Avoids enormous network payloads Total size was 2,427 KiB
Large network payloads cost users real money and are highly correlated with long load times
Largest Contentful Paint 2.8 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Enable text compression Est savings of 34 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes
Properly size images Est savings of 1,403 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Serve images in next-gen formats Est savings of 1,784 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption
Document request latency Est savings of 80 ms
Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.
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
Minify CSS Est savings of 15 KiB
Minifying CSS files can reduce network payload sizes
Avoids an excessive DOM size 256 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)
Improve image delivery Est savings of 2,031 KiB
Reducing the download time of images can improve the perceived load time of the page and LCP
Largest Contentful Paint element 2,830 ms
This is the largest contentful element painted within the viewport

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
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
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
carlosreyesdop.co Available
carlosreyesdop.us Available
carlosreyesdop.com Already Registered
carlosreyesdop.org Available
carlosreyesdop.net Available
crlosreyesdop.com Available
darlosreyesdop.com Available
rarlosreyesdop.com Available

Information Server

Response Header HTTP headers carry information about the client browser, the requested page and the server
HTTP/1.1 404 Not Found
Connection: close
Content-Length: 0
Server: Varnish
Retry-After: 0
Accept-Ranges: bytes
Date: Tue, 05 Aug 2025 22:13:14 GMT
Via: 1.1 varnish
X-Served-By: cache-yul1970027-YUL
X-Cache: MISS
X-Cache-Hits: 0
X-Timer: S1754431995.534131,VS0,VE26
X-Last-60s-Hits: 4
DNS Records DNS Resource Records associated with a hostname
View DNS Records