Deck.ly
X / ?
Domain Summary
What is the traffic rank for Deck.ly?
• Deck.ly ranks #8,482,868 globally on HypeStat.
What IP addresses does Deck.ly resolve to?
• Deck.ly resolves to the IP addresses 104.244.42.67.
Where are Deck.ly servers located in?
• Deck.ly has servers located in United States.
deck.ly Profile

What technologies does deck.ly use?
These are the technologies used at deck.ly. deck.ly has a total of 7 technologies installed in 6 different categories.deck.ly Traffic Analysis
Deck.ly is ranked #8,482,868 in the world.Daily Visitors n/a
Monthly Visits n/a
Pages per Visit n/a
Visit duration n/a
Bounce Rate n/a
Is this your site?Verify your site's metrics.
- Daily Unique Visitors:
- n/a
- Monthly Visits:
- n/a
- Pages per Visit:
- n/a
- Daily Pageviews:
- n/a
- Avg. visit duration:
- n/a
- Bounce rate:
- n/a
- Global Reach:
- n/a
- HypeRank:
- 8,482,868
Backlinks Report ▼
Deck.ly has a total of 16,343 backlinks from 845 referring domains and most of them comes from United States.- Total Backlinks:
- 16,343
- Follow Links:
- n/a
- Nofollow Links:
- n/a
- Referring Domains:
- 845
- Referring IPs:
- 754
- Authority Domain Score:
- 6
Backlinks by country
- Country
- Domains
- United States 488
- Japan 50
- Germany 30
- United Kingdom 24
- France 24
Backlinks by TLDs
- TLD Distribution
- Domains
- .com
- 603
- .net
- 49
- .org
- 39
- .edu
- 2
- .gov
- 0
Last update was 324 days ago
This can take up to 60 seconds. Please wait...
This can take up to 60 seconds. Please wait...
*HypeStat.com is not promoting or affiliated with deck.ly in any way. Only publicly available statistics data are displayed.
▼
SEMrush is a complete on line advertising and marketing platform that gives a extensive variety of gear and functions to help companies and entrepreneurs in enhancing their on line visibility and optimizing their virtual advertising and marketing strategies.- Domain:
- deck.ly
- Rank:
(Rank based on keywords, cost and organic traffic) - n/a
- Organic Keywords:
(Number of keywords in top 20 Google SERP) - 0
- Organic Traffic:
(Number of visitors coming from top 20 search results) - 0
- Organic Cost:
((How much need to spend if get same number of visitors from Google Adwords) - $0.00
Ad Experience Report ▼
Summary of the ad experience rating of a website for a specific platform.Mobile summary
- Root domain:
- deck.ly
- Ad filtering:
(Chrome is not filtering ads on your site.) - Off
- Status:
(The status of the site that is reviewed for the Better Ads Standards.) - Not reviewed
Desktop summary
- Root domain:
- deck.ly
- Ad filtering:
(Chrome is not filtering ads on your site.) - Off
- Status:
(The status of the site that is reviewed for the Better Ads Standards.) - Not reviewed
Abusive Experience Report ▼
Summary of the abusive experience rating of a website.- Root domain:
- deck.ly
- Enforcement:
(Chrome is not preventing your site from opening new windows or tabs.) - Off
- Status:
(The status of the site reviewed for the abusive experiences.) - Not reviewed
Where is deck.ly hosted? ▼
Deck.ly may be hosted in multiple data centers distributed in different locations around the world. This is probably just one of them.- Server IP:
- 104.244.42.67
- ASN:
- AS13414
- ISP:
- Twitter Inc.
- Server Location:
United States, US
Other sites hosted on 104.244.42.67
How fast does deck.ly load? ▼
The average loading time of deck.ly is 314 ms. The Desktop speed index is 58 and mobile speed index is 38.- Average Load Time:
- 314 ms
Page Speed (Google PageSpeed Insights) - Desktop
Field Data
Over the last 30 days, the field data shows that this page has a SLOW speed compared to other pages in the Chrome User Experience Report.We are showing the 90th percentile of FCP and the 95th percentile of FID.
Cumulative Layout Shift (CLS)5ms
Time To First Byte (TTFB)547ms
First Contentful Paint (FCP)730ms
First Input Delay (FID)4ms
Interaction To Next Paint (INP)263ms
Largest Contentful Paint (LCP)4.2s
Origin Data
All pages served from this origin have an SLOW speed compared to other pages in the Chrome User Experience Report. over the last 30 days.To view suggestions tailored to each page, analyze individual page URLs.
Cumulative Layout Shift (CLS)5ms
Time To First Byte (TTFB)547ms
First Contentful Paint (FCP)730ms
First Input Delay (FID)4ms
Interaction To Next Paint (INP)263ms
Largest Contentful Paint (LCP)4.2s
Lab Data
Preload Largest Contentful Paint image
If the LCP element is dynamically added to the page, you should preload the image in order to improve LCP. Learn more about preloading LCP elements
If the LCP element is dynamically added to the page, you should preload the image in order to improve LCP. Learn more about preloading LCP elements
First Contentful Paint 0.9 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more about the First Contentful Paint metric
First Contentful Paint marks the time at which the first text or image is painted. Learn more about the First Contentful Paint metric
Minimizes main-thread work
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work
Max Potential First Input Delay 300 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric
Largest Contentful Paint 2.6 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint metric
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint metric
Time to Interactive 2.8 s
Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric
Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric
Speed Index 1.3 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric
Lazy load third-party resources with facades
Some third-party embeds can be lazy loaded. Consider replacing them with a facade until they are required. Learn how to defer third-parties with a facade
Some third-party embeds can be lazy loaded. Consider replacing them with a facade until they are required. Learn how to defer third-parties with a facade
JavaScript execution time
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time
First Meaningful Paint 2.0 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric
Total Blocking Time 700 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more about the Total Blocking Time metric
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more about the Total Blocking Time metric
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint. Learn more about optimal lazy loading
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint. Learn more about optimal lazy loading
Minimize third-party usage
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. Learn how to minimize third-party impact
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. Learn how to minimize third-party impact
Avoid long main-thread tasks
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn how to avoid long main-thread tasks
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn how to avoid long main-thread tasks
Preconnect to required origins
Consider adding `preconnect` or `dns-prefetch` resource hints to establish early connections to important third-party origins. Learn how to preconnect to required origins
Consider adding `preconnect` or `dns-prefetch` resource hints to establish early connections to important third-party origins. Learn how to preconnect to required origins
Diagnostics
Collection of useful page vitals.
Collection of useful page vitals.
Tasks
Lists the toplevel main thread tasks that executed during page load.
Lists the toplevel main thread tasks that executed during page load.
Page Speed (Google PageSpeed Insights) - Mobile
Field Data
Over the last 30 days, the field data shows that this page has a SLOW speed compared to other pages in the Chrome User Experience Report.We are showing the 90th percentile of FCP and the 95th percentile of FID.
Cumulative Layout Shift (CLS)8ms
Time To First Byte (TTFB)1.2s
First Contentful Paint (FCP)1.6s
First Input Delay (FID)29ms
Interactive To Next Paint (INP)375ms
Largest Contentful Paint (LCP)7.2s
Origin Data
All pages served from this origin have an SLOW speed compared to other pages in the Chrome User Experience Report. over the last 30 days.To view suggestions tailored to each page, analyze individual page URLs.
Cumulative Layout Shift (CLS)8ms
Time To First Byte (TTFB)1.2s
First Contentful Paint (FCP)1.6s
First Input Delay (FID)29ms
Interactive To Next Paint (INP)375ms
Largest Contentful Paint (LCP)7.2s
Lab Data
Diagnostics
Collection of useful page vitals.
Collection of useful page vitals.
Speed Index 4.5 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric
JavaScript execution time
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time
Minimizes main-thread work
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work
Preload Largest Contentful Paint image
If the LCP element is dynamically added to the page, you should preload the image in order to improve LCP. Learn more about preloading LCP elements
If the LCP element is dynamically added to the page, you should preload the image in order to improve LCP. Learn more about preloading LCP elements
Avoid long main-thread tasks
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn how to avoid long main-thread tasks
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn how to avoid long main-thread tasks
Minimize third-party usage
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. Learn how to minimize third-party impact
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. Learn how to minimize third-party impact
Preconnect to required origins
Consider adding `preconnect` or `dns-prefetch` resource hints to establish early connections to important third-party origins. Learn how to preconnect to required origins
Consider adding `preconnect` or `dns-prefetch` resource hints to establish early connections to important third-party origins. Learn how to preconnect to required origins
Time to Interactive 14.8 s
Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric
Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint. Learn more about optimal lazy loading
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint. Learn more about optimal lazy loading
Max Potential First Input Delay 1,350 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric
Lazy load third-party resources with facades
Some third-party embeds can be lazy loaded. Consider replacing them with a facade until they are required. Learn how to defer third-parties with a facade
Some third-party embeds can be lazy loaded. Consider replacing them with a facade until they are required. Learn how to defer third-parties with a facade
Tasks
Lists the toplevel main thread tasks that executed during page load.
Lists the toplevel main thread tasks that executed during page load.
First Contentful Paint 2.8 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more about the First Contentful Paint metric
First Contentful Paint marks the time at which the first text or image is painted. Learn more about the First Contentful Paint metric
First Meaningful Paint 8.4 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric
Total Blocking Time 4,250 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more about the Total Blocking Time metric
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more about the Total Blocking Time metric
Largest Contentful Paint 14.2 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint metric
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint metric
Does deck.ly use compression? ▼
Website compression is the process of reducing the size of website files, such as HTML, CSS, JavaScript, and image files, to improve website performance and load times. Compressing website files can significantly reduce the amount of data that needs to be transferred from the server to the user's browser, resulting in faster page load times and improved user experience. Files on deck.ly are reduced by 58%.
deck.ly use gzip compression.
Original size: 3.57 KB
Compressed size: 1.47 KB
File reduced by: 2.1 KB (58%)
Compressed size: 1.47 KB
File reduced by: 2.1 KB (58%)
Google Safe Browsing ▼
Google Safe Browsing is a service provided by Google that helps protect users from visiting websites that may contain malicious or harmful content, such as malware, phishing attempts, or deceptive software.
This site is not currently listed as suspicious
MyWot.com Reputation Ratings
MyWOT (short for "My Web of Trust") is a web-based reputation and rating service that provides users with information about the trustworthiness and safety of websites. deck.ly has 87 Safety Reputations.- Status:
- SAFE
- Safety Reputations:
- 87
- Safety Confidence:
- 10
SSL Checker - SSL Certificate Verify ▼
An SSL (Secure Sockets Layer) certificate is a digital certificate that establishes a secure encrypted connection between a web server and a user's web browser. It provides authentication and encryption, ensuring that data transmitted between the server and the browser remains private and protected. deck.ly supports HTTPS. deck.ly supports HTTPS
Verifying SSL Support. Please wait...
Common Name: twitter.com
Organization: "Twitter, Inc."
Location: San Francisco, California, US
Issuer: DigiCert Global G2 TLS RSA SHA256 2020 CA1
Valid from: Nov 8 00:00:00 2023 GMT
Valid until: Nov 6 23:59:59 2024 GMT
Authority: CA:FALSE
Keysize: 2048 Bits
Organization: "Twitter, Inc."
Location: San Francisco, California, US
Issuer: DigiCert Global G2 TLS RSA SHA256 2020 CA1
Valid from: Nov 8 00:00:00 2023 GMT
Valid until: Nov 6 23:59:59 2024 GMT
Authority: CA:FALSE
Keysize: 2048 Bits
Common Name: DigiCert Global G2 TLS RSA SHA256 2020 CA1
Organization: DigiCert Inc
Location: US
Issuer: DigiCert Global Root G2
Valid from: Mar 30 00:00:00 2021 GMT
Valid until: Mar 29 23:59:59 2031 GMT
Authority: CA:TRUE
Keysize: 2048 Bits
Organization: DigiCert Inc
Location: US
Issuer: DigiCert Global Root G2
Valid from: Mar 30 00:00:00 2021 GMT
Valid until: Mar 29 23:59:59 2031 GMT
Authority: CA:TRUE
Keysize: 2048 Bits
Verify HTTP/2 Support ▼
HTTP/2 (Hypertext Transfer Protocol version 2) is a major revision of the HTTP protocol, which is the foundation of data communication on the World Wide Web. It was developed as an improvement over the previous HTTP/1.1 version to enhance web performance and efficiency. deck.ly supports HTTP/2
Verifying HTTP/2.0 Support. Please wait...
Http Header ▼
HTTP headers are extra portions of records despatched among a consumer (which include an internet browser) and a server at some stage in an HTTP request or response. They offer instructions, metadata, or manipulate parameters for the conversation among the consumer and server.perf: 7402827104
location: https://twitter.com/TweetDeck/status/114378833225986048
cache-control: no-cache, no-store, max-age=0
content-length: 0
x-transaction-id: 76d19ab6832a361d
x-response-time: 1
x-connection-hash: 1023ffedafeb08fe9ebe7ab772663bc9c0676304d6a0891d4cea6e5d0e0436f0
date: Fri, 26 Jul 2024 20:26:02 GMT
server: tsa_b
HTTP/2 404
date: Fri, 26 Jul 2024 20:26:02 GMT
perf: 7402827104
expiry: Tue, 31 Mar 1981 05:00:00 GMT
pragma: no-cache
server: tsa_b
set-cookie: guest_id_ads=v1%3A172202556288256709; Max-Age=63072000; Expires=Sun, 26 Jul 2026 20:26:02 GMT; Path=/; Domain=.twitter.com; Secure; SameSite=None
set-cookie: guest_id_marketing=v1%3A172202556288256709; Max-Age=63072000; Expires=Sun, 26 Jul 2026 20:26:02 GMT; Path=/; Domain=.twitter.com; Secure; SameSite=None
set-cookie: gt=1816933017098600694; Max-Age=9000; Expires=Fri, 26 Jul 2024 22:56:02 GMT; Path=/; Domain=.twitter.com; Secure
set-cookie: personalization_id="v1_aNsVR0pyk0hL50bAVGWpTQ=="; Max-Age=63072000; Expires=Sun, 26 Jul 2026 20:26:02 GMT; Path=/; Domain=.twitter.com; Secure; SameSite=None
set-cookie: guest_id=v1%3A172202556288256709; Max-Age=63072000; Expires=Sun, 26 Jul 2026 20:26:02 GMT; Path=/; Domain=.twitter.com; Secure; SameSite=None
set-cookie: ct0=; Max-Age=-1722025561; Expires=Thu, 01 Jan 1970 00:00:01 GMT; Path=/; Domain=.twitter.com; Secure; SameSite=Lax
content-type: text/html;charset=utf-8
x-powered-by: Express
cache-control: no-cache, no-store, must-revalidate, pre-check=0, post-check=0
last-modified: Fri, 26 Jul 2024 20:26:02 GMT
x-frame-options: DENY
x-transaction-id: 3c46c3aede133ae4
x-xss-protection: 0
x-content-type-options: nosniff
content-security-policy: default-src 'none'; img-src https://abs.twimg.com; script-src https://abs.twimg.com about:; style-src https://abs.twimg.com 'unsafe-inline'; font-src https://abs.twimg.com https://twitter.com; connect-src 'none'; object-src 'none'; media-src 'none'; frame-src 'none'; report-uri https://twitter.com/i/csp_report?a=ORTGK%3D%3D%3D&ro=false
strict-transport-security: max-age=631138519
cross-origin-opener-policy: same-origin-allow-popups
cross-origin-embedder-policy: unsafe-none
content-encoding: gzip
content-length: 1504
x-response-time: 79
x-connection-hash: ad55f9445b30e760e4d7cf58ba2cc19cff3e1b0d52466eb1c2cfc3956661b68a
DNS Lookup ▼
DNS entries (Domain Name System) are a critical component of the Internet infrastructure. They act as directories that translate human-readable domain names (such as example.com) to machine-readable IP addresses. DNS records are stored on DNS servers and help forward internet traffic efficiently.Type | Ip | Target/Txt | TTL |
A | 104.244.42.195 | 23 | |
A | 104.244.42.3 | 23 | |
A | 104.244.42.67 | 23 | |
A | 104.244.42.131 | 23 | |
NS | 86357 | ||
NS | 86357 | ||
NS | 86357 | ||
NS | 86357 | ||
HINFO | 3600 |
Whois Lookup ▼
Domain WHOIS is a public database that provides information about domain names, including registered owners, contact information, domain registrars, registration and expiration dates, name servers, and other relevant information. Domain registration for this website began on January 17, 2009 and will expire on January 17, 2025 if not renewed. This website is now assigned through the registrar Libyan Spider Network (int). The WHOIS data for this website's domain was last updated on December 13, 2023.- Domain Created:
- 2009-01-17
- Domain Expires:
- 2025-01-17
- Domain Updated:
- 2023-12-13
- Domain Age:
- 16 years 4 months 30 days
- Domain Registrar:
- Libyan Spider Network (int)
- Domain Owner:
- Twitter Inc.
- WhoIs:
Domain Name: deck.ly Registry Domain ID: 29066-CoCCA Registry WHOIS Server: whois.nic.ly Updated Date: 2023-12-13T20:31:59.836Z Creation Date: 2009-01-17T22:00:00.0Z Registry Expiry Date: 2025-01-17T22:00:00.0Z Registrar Registration Expiration Date: 2025-01-17T22:00:00.0Z Domain Status: clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited Registry Registrant ID: 4N9g3-BdKcV Registrant Name: Domain REG Registrant Organization: Twitter Inc. Registrant Street: 1355 Market Street Registrant Street: Suite 900 Registrant City: San Francisco Registrant State/Province: CA Registrant Country: US Registrant Phone: +1.4152229670 Registrant Fax: +1.4152220922 Registrant Email:Registry Admin ID: 4wLPK-nH7MD Admin Name: Domain Admin Admin Organization: Twitter, Inc. Admin Street: 1355 Market Street Admin Street: Suite 900 Admin City: San Francisco, Admin State/Province: CA Admin Postal Code: 94103 Admin Country: US Admin Phone: +1.4152229670 Admin Email:
Registry Tech ID: cNGbW-FlMwS Tech Name: Tech Admin Tech Organization: Twitter, Inc. Tech Street: 1355 Market Street Tech Street: Suite 900 Tech City: San Francisco Tech State/Province: CA Tech Postal Code: 94103 Tech Country: US Tech Phone: +1.4152229670 Tech Email:
Registry Billing ID: nrv6n-ayOBi Billing Name: ccTLD Billing Billing Organization: CSC Corporate Domains, Inc. Billing Street: 251 Little Falls Drive Billing City: Wilmington Billing State/Province: DE Billing Postal Code: 19808 Billing Country: US Billing Phone: +1.3026365400 Billing Email:
Registrar: Libyan Spider Network (int) Registrar Abuse Contact Email:
Registrar Abuse Contact Phone: +1.8448469791 Name Server: a.u08.twtrdns.net Name Server: b.u08.twtrdns.net Name Server: c.u08.twtrdns.net Name Server: d.u08.twtrdns.net DNSSEC: unsigned >>> Last update of WHOIS database: 2024-07-26T20:00:00.554Z