Your Website Score is

Similar Ranking

34
WELCOME TO NGINX!
youtube.com.music
34
PÁGINA INICIAL SAN MARTÍN DE LOS ANDES - SAN MARTIN DE LOS ANDES
sanmartindelosandes.gov.ar
34
404 NOT FOUND
mp3-convert.org
34
YOUTUBE MP3 CONVERTER
mp3-youtube.net
34
GUITAR LESSONS WITH PAUL
paulhoeguitar.mymusicstaff.com
34
--- RAILWAY RULES FOR EMPLOYEES AT RAILWAYRULE.COM
railwayrule.com

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

34 orientwatchusa.com Last Updated: 2 years

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

Desktop

Mobile

Performance Desktop Score 57%
Best Practices Desktop Score 93%
SEO Desktop Score 92%
PWA Desktop Score 29%
Performance Mobile Score 28%
Best Practices Mobile Score 93%
SEO Mobile Score 83%
PWA Mobile Score 38%
Page Authority Authority 47%
Domain Authority Domain Authority 46%
Moz Rank 4.7/10
Bounce Rate Rate 0%
Title Tag 36 Characters
AUTOMATIC WATCHES | ORIENT WATCH USA
Meta Description 173 Characters
Orient Watch USA™ is the official and licensed online distributor. Shop Mako USA II, Bambino, Kamasu, Ray II, Orient Star and best priced Japanese watches for men and women.
Effective URL 30 Characters
https://www.orientwatchusa.com
Excerpt Page content
Automatic Watches | Orient Watch USASkip to contentSearch AccountCartBrowse Style---plore our select list of collectionsClassicShop NowOrient BambinoShop NowSportShop NowBest SellersShop NowSmaller WatchesShop NowWatch StrapsShop NowShop AllOur Best ...
Keywords Cloud Density
orient19 20px10 shop10 sale9 bambino7 watch7 >svg5 version4 service3 story3
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
orient 19
20px 10
shop 10
sale 9
bambino 7
watch 7
>svg 5
version 4
service 3
story 3
Google Preview Your look like this in google search result
AUTOMATIC WATCHES | ORIENT WATCH USA
https://www.orientwatchusa.com
Orient Watch USA™ is the official and licensed online distributor. Shop Mako USA II, Bambino, Kamasu, Ray II, Orient Star and best priced Japanese wat
Robots.txt File Detected
Sitemap.xml File Detected
Page Size Code & Text Ratio
Document Size: ~128 KB
Code Size: ~77.42 KB
Text Size: ~50.58 KB Ratio: 39.52%

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
Total Blocking Time 460 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Minimize main-thread work 3.5 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.4 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Time to Interactive 5.5 s
Time to Interactive is the amount of time it takes for the page to become fully interactive
Server Backend Latencies 600 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 images in next-gen formats Potential savings of 168 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption
Avoid serving legacy JavaScript to modern browsers Potential savings of 11 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
Avoid enormous network payloads Total size was 3,957 KiB
Large network payloads cost users real money and are highly correlated with long load times
Avoid non-composited animations 1 animated element found
Animations which are not composited can be janky and increase CLS
Reduce initial server response time Root document took 600 ms
Keep the server response time for the main document short because all other requests depend on it
First Contentful Paint 1.6 s
First Contentful Paint marks the time at which the first text or image is painted
Reduce unused JavaScript Potential savings of 975 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity
Remove duplicate modules in JavaScript bundles Potential savings of 28 KiB
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
Reduce the impact of third-party code Third-party code blocked the main thread for 1,160 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.8 s
First Meaningful Paint measures when the primary content of a page is visible
Web app manifest or service worker do not meet the installability requirements 1 reason
Service worker is the technology that enables your app to use many Progressive Web App features, such as offline, add to homescreen, and push notifications. With proper service worker and manifest implementations, browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement
Avoid chaining critical requests 11 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
Defer offscreen images Potential savings of 4 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Reduce JavaScript execution time 2.2 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Avoid large layout shifts 6 elements found
These DOM elements were most affected by layout shifts. Some layout shifts may not be included in the CLS metric value due to [windowing](https://web.dev/articles/cls#what_is_cls)
Speed Index 2.6 s
Speed Index shows how quickly the contents of a page are visibly populated
Reduce unused CSS Potential savings of 89 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity
Max Potential First Input Delay 250 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Network Round Trip Times 100 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 17 resources found
A long cache lifetime can speed up repeat visits to your page
Largest Contentful Paint element 2,360 ms
This is the largest contentful element painted within the viewport
User Timing marks and measures 17 user timings
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences
Enable text compression Potential savings of 4 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes
Some third-party resources can be lazy loaded with a facade 1 facade alternative available
Some third-party embeds can be lazy loaded. Consider replacing them with a facade until they are required
Eliminate render-blocking resources Potential 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
Avoids an excessive DOM size 718 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)
Avoid long main-thread tasks 8 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Properly size images Potential savings of 558 KiB
Serve images that are appropriately-sized to save cellular data and improve load time

Mobile

Mobile Screenshot
Max Potential First Input Delay 1,170 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Speed Index 8.4 s
Speed Index shows how quickly the contents of a page are visibly populated
Largest Contentful Paint 8.9 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Avoids an excessive DOM size 724 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)
Network Round Trip Times 40 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 3,640 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Initial server response time was short Root document took 360 ms
Keep the server response time for the main document short because all other requests depend on it
Avoid chaining critical requests 11 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
Serve images in next-gen formats Potential savings of 168 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption
Server Backend Latencies 360 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
Enable text compression Potential savings of 4 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes
Avoid large layout shifts 3 elements found
These DOM elements were most affected by layout shifts. Some layout shifts may not be included in the CLS metric value due to [windowing](https://web.dev/articles/cls#what_is_cls)
Web app manifest or service worker do not meet the installability requirements 1 reason
Service worker is the technology that enables your app to use many Progressive Web App features, such as offline, add to homescreen, and push notifications. With proper service worker and manifest implementations, browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement
Largest Contentful Paint element 8,920 ms
This is the largest contentful element painted within the viewport
Document uses legible font sizes 99.98% 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
Tap targets are not sized appropriately 64% appropriately sized tap targets
Interactive elements like buttons and links should be large enough (48x48px), or have enough space around them, to be easy enough to tap without overlapping onto other elements
Avoid serving legacy JavaScript to modern browsers Potential savings of 11 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
Eliminate render-blocking resources Potential savings of 530 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Reduce unused CSS Potential savings of 100 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity
First Contentful Paint 5.3 s
First Contentful Paint marks the time at which the first text or image is painted
Time to Interactive 25.0 s
Time to Interactive is the amount of time it takes for the page to become fully interactive
Remove duplicate modules in JavaScript bundles Potential savings of 29 KiB
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
Properly size images Potential savings of 277 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Reduce unused JavaScript Potential savings of 991 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity
Defer offscreen images Potential savings of 351 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Reduce JavaScript execution time 9.5 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
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
Links do not have descriptive text 9 links found
Descriptive link text helps search engines understand your content
User Timing marks and measures 11 user timings
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences
Minimize main-thread work 13.0 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
First Meaningful Paint 6.1 s
First Meaningful Paint measures when the primary content of a page is visible
Reduce the impact of third-party code Third-party code blocked the main thread for 6,130 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 enormous network payloads Total size was 3,783 KiB
Large network payloads cost users real money and are highly correlated with long load times
Some third-party resources can be lazy loaded with a facade 1 facade alternative available
Some third-party embeds can be lazy loaded. Consider replacing them with a facade until they are required
Serve static assets with an efficient cache policy 17 resources found
A long cache lifetime can speed up repeat visits to your page
Cumulative Layout Shift 0.001
Cumulative Layout Shift measures the movement of visible elements 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
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
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
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
orientwatchusa.co Available
orientwatchusa.us Available
orientwatchusa.com Already Registered
orientwatchusa.org Available
orientwatchusa.net Available
oientwatchusa.com Available
krientwatchusa.com Available
lrientwatchusa.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: Fri, 02 Feb 2024 03:28:25 GMT
Content-Type: text/html
Connection: keep-alive
Cache-Control: null
oxygen-full-page-cache: uncacheable
powered-by: Shopify, Oxygen, Hydrogen
x-request-id: o2-5d6e6ad2-f5bb-4d1b-b081-05b57abdb451.84ef58101a3a0ca0
x-shopid: 2649784385
Set-Cookie: __cf_bm=5foxta9_IeKDkaFbxPxZsW2psHO5wcBP9HTXaR_7xow-1706844505-1-AdVUBgy5+/A3hNWTOx6GP9ZDi0NOo5KBSiFyoQEbAqCZOqUTf3tOdM/l+3WbtHD7voJKU//Qj/KQ82UuEQDQ1n4=; path=/; expires=Fri, 02-Feb-24 03:58:25 GMT; domain=.www.orientwatchusa.com; HttpOnly; Secure; SameSite=None
Vary: Accept-Encoding
Server: cloudflare
CF-RAY: 84ef58101a3a0ca0-EWR
Content-Encoding: gzip
alt-svc: h3=":443"; ma=86400
DNS Records DNS Resource Records associated with a hostname
View DNS Records