Landen.Co - Info landen.co

landen.co receives about 4,242 unique visitors and 15,270 (3.60 per visitor) page views per day which should earn about $7.12/day from advertising revenue. Estimated site value is $2,988.83. According to Alexa Traffic Rank landen.co is ranked number 208,566 in the world and 0.00025% of global Internet users visit it. Site is hosted in Boardman, Oregon, 97818, United States and links to network IP address 54.71.114.71. This server supports HTTPS and HTTP/2.

About - landen.co


Technologies used on Website

Font Scripts
Google Font API

landen.co Profile

Title: Landen: The Website Platform for Startups
Description: Generate, edit and publish beautiful websites and landing pages for your startup. All without code.
Last update was 140 days ago
loader
This can take up to 60 seconds. Please wait...

*HypeStat.com is not linking to, promoting or affiliated with landen.co in any way. Only publicly available statistics data are displayed.

How popular is landen.co?

4.2K daily visitors
Is this your site?
Verify your site's metrics.
Daily Unique Visitors:
4,242
Monthly Unique Visitors:
101,808
Pages per Visit:
3.60
Daily Pageviews:
15,270
Alexa Rank:
208,566 visit alexa
Alexa Reach:
0.00025%   (of global internet users)
Avg. visit duration:
n/a
Bounce rate:
n/a
*All traffic values are estimates only.

Alexa Traffic Ranks
Search Traffic

Visitors by country

Users%Pageviews%Rank
India 21.2%19.0%99938
Nigeria 14.6%6.2%17987

Where do visitors go on this site?

Reach%Pageviews%PerUser
landen.co
76.03%44.57%1.6
app.landen.co
44.81%48.10%3
OTHER
0%7.33%0

Competitive Data

SEMrush
Domain:
  landen.co
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
Adwords Keywords:
(Keywords a website is buying in Google AdWords for ads that appear in paid search results)
  0
Adwords Traffic:
(Number of visitors brought to the website via paid search results)
  0
Adwords Cost:
(Estimated budget spent for buying keywords in Google AdWords for ads that appear in paid search results - monthly estimation)
  $0.00

+ Moz Data

Domain Authority:
  n/a
Page Authority:
  n/a
MozRank:
  n/a

+ How socially engaged is landen.co?

Facebook:
  0
Google +:
  0
Linkedin:
  0
Stumbles:
  0
Buffer:
  0
Pins:
  0

+ Ad Experience Report

Summary of the ad experience rating of a site for a specific platform.

Desktop summary

Root domain:
landen.co
Region:
(The Ad Standard region to which this site has been assigned.)
Pending
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


Mobile summary

Region:
(The Ad Standard region to which this site has been assigned.)
Pending
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

Root domain:
landen.co
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

+ How much landen.co can earn?

Daily Revenue:
$7.12
Monthly Revenue:
$213.60
Yearly Revenue:
$2,598.80
*All earnings values are estimates only.

Daily earning by country

PageviewsEarning
India 2,901$4.64
Nigeria 947$2.48

How much money do landen.co lose due to Adblock?

Daily Revenue Loss:
$1.35
Monthly Revenue Loss:
$40.48
Yearly Revenue Loss:
$492.53
Daily Pageviews Blocked:
831
Monthly Pageviews Blocked:
24,939
Yearly Pageviews Blocked:
303,424
*All earnings values are estimates only.

Daily revenue loss by country

BlockedLost Money
India 812$1.30
Nigeria 19$0.05

How much is landen.co worth?

Website Value:
$2,988.83

+ Where is landen.co hosted?

Server IP:
54.71.114.71
ASN:
AS16509 
ISP:
Amazon.com, Inc. 
Server Location:
Boardman
Oregon, OR
97818
United States, US
 

Other sites hosted on 54.71.114.71

+ How fast does landen.co load?

Average Load Time:
(1033 ms) 78 % of sites are slower

Page Speed (Google PageSpeed Insights) - Desktop

96
0-49 50-89 90-100 i

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.

First Contentful Paint (FCP)2.8s 44% of loads for this page have a fast (<1s) First Contentful Paint (FCP) 44% 41% of loads for this page have an average (1s ~ 2.5s) First Contentful Paint (FCP) 41% 13% of loads for this page have a slow (>2.5s) First Contentful Paint (FCP) 13%
First Input Delay (FID)23ms 97% of loads for this page have a fast (<50ms) First Input Delay (FID) 97% 2% of loads for this page have an average (50ms ~ 250ms) First Input Delay (FID) 2% 0% of loads for this page have a slow (>250ms) First Input Delay (FID) 0%

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.

First Contentful Paint (FCP)2.6s 53% of loads for this page have a fast (<1s) First Contentful Paint (FCP) 53% 35% of loads for this page have an average (1s ~ 2.5s) First Contentful Paint (FCP) 35% 10% of loads for this page have a slow (>2.5s) First Contentful Paint (FCP) 10%
First Input Delay (FID)20ms 98% of loads for this page have a fast (<50ms) First Input Delay (FID) 98% 1% of loads for this page have an average 50ms ~ 250ms) First Input Delay (FID) 1% 0% of loads for this page have a slow (>250ms) First Input Delay (FID) 0%

Lab Data

Estimated Input Latency 10 ms
Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy. Learn more.
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 Index 1.2 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 0.9 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. Learn more.
First Contentful Paint 0.9 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.
Performance budget
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more.
First Meaningful Paint 0.9 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more.
Max Potential First Input Delay 30 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task. Learn more.
Time to Interactive 0.9 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.

Screenshot Thumbnails

This is what the load of your site looked like.

Ensure text remains visible during webfont load
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more.

URL
Potential Savings
https://fonts.gstatic.com/s/roboto/v20/KFOlCnqEu92Fr1MmWUlfBBc4.woff2
5 ms
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. Learn more.

URL
Total CPU TimeScript EvaluationScript Parse
Other
385 ms4 ms1 ms
Properly size images - Potential savings of 63 KB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.

URL
SizePotential Savings
https://landen.imgix.net/hqqzhj62ez8m/assets/0fd0ppwq.png?w=1200&h=900&fit=max
89 KB63 KB
Remove unused CSS - Potential savings of 8 KB
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity. Learn more.

URL
SizePotential Savings
https://cdn.landen.co/hqqzhj62ez8m/assets/main.a727a989.css
10 KB8 KB
Avoids enormous network payloads - Total size was 299 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
https://landen.imgix.net/hqqzhj62ez8m/assets/0fd0ppwq.png?w=1200&h=900&fit=max
89 KB
https://www.landen.co/
75 KB
https://cdn.landen.co/hqqzhj62ez8m/assets/mxoofvds.svg
40 KB
https://www.googletagmanager.com/gtag/js?id=UA-115144659-2
27 KB
https://www.google-analytics.com/analytics.js
18 KB
https://fonts.gstatic.com/s/roboto/v20/KFOlCnqEu92Fr1MmWUlfBBc4.woff2
16 KB
https://landen.imgix.net/hqqzhj62ez8m/assets/udvwi5p9.svg
15 KB
https://cdn.landen.co/hqqzhj62ez8m/assets/main.a727a989.css
10 KB
https://landen.imgix.net/hqqzhj62ez8m/assets/w4yv55bl.svg?w=240
5 KB
https://fonts.googleapis.com/css?family=Roboto:700
1 KB
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.

Category
Time Spent
Other
123 ms
Rendering
120 ms
Style & Layout
113 ms
Script Evaluation
47 ms
Parse HTML & CSS
25 ms
Script Parsing & Compilation
5 ms
Garbage Collection
0 ms
Serve images in next-gen formats - Potential savings of 52 KB
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more.

URL
SizePotential Savings
https://landen.imgix.net/hqqzhj62ez8m/assets/0fd0ppwq.png?w=1200&h=900&fit=max
89 KB52 KB
Avoids an excessive DOM size - 770 elements
Browser engineers recommend pages contain fewer than ~1,500 DOM elements. The sweet spot is a tree depth < 32 elements and fewer than 60 children/parent element. A large DOM can 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). Learn more.

Statistic
ElementValue
Total DOM Elements
770
Maximum DOM Depth
12
Maximum Child Elements
16
Avoid multiple page redirects - Potential savings of 340 ms
Redirects introduce additional delays before the page can be loaded. Learn more.

URL
Time Spent
(Initial: http://landen.co/)
0
https://landen.co/
190
https://www.landen.co/
150
Keep request counts low and transfer sizes small - 17 requests • 4,448 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
Total
174448 KB
Media
14149 KB
Image
7151 KB
Document
175 KB
Script
245 KB
Font
116 KB
Stylesheet
211 KB
Other
31 KB
Third-party
114322 KB
Eliminate render-blocking resources - Potential savings of 230 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.

URL
SizePotential Savings
https://cdn.landen.co/hqqzhj62ez8m/assets/main.a727a989.css
10 KB230
https://fonts.googleapis.com/css?family=Roboto:700
1 KB230
Enable text compression - Potential savings of 61 KB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.

URL
SizePotential Savings
https://www.landen.co/
75 KB61 KB
Network Requests
Lists the network requests that were made during page load.

URL
Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
http://landen.co/
0 ms86 ms0 KB0 KB307text/html
https://landen.co/
86 ms369 ms0 KB0 KB307text/html
https://www.landen.co/
369 ms625 ms75 KB75 KB200text/htmlDocument
https://cdn.landen.co/hqqzhj62ez8m/assets/main.a727a989.css
637 ms660 ms10 KB45 KB200text/cssStylesheet
https://fonts.googleapis.com/css?family=Roboto:700
637 ms656 ms1 KB2 KB200text/cssStylesheet
https://www.googletagmanager.com/gtag/js?id=UA-115144659-2
638 ms665 ms27 KB69 KB200application/javascriptScript
https://landen.imgix.net/hqqzhj62ez8m/assets/w4yv55bl.svg?w=240
638 ms656 ms5 KB12 KB200image/svg+xmlImage
https://landen.imgix.net/hqqzhj62ez8m/assets/udvwi5p9.svg
658 ms716 ms15 KB49 KB200image/svg+xmlImage
https://landen.imgix.net/hqqzhj62ez8m/assets/0fd0ppwq.png?w=1200&h=900&fit=max
680 ms776 ms89 KB89 KB200image/pngImage
https://cdn.landen.co/hqqzhj62ez8m/assets/mxoofvds.svg
680 ms760 ms40 KB57 KB200image/svg+xmlImage
data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAMAAAADACAYAAABS3GwHAAAAAXNSR0IArs4c6QAABqVJREFUeNrt3c
729 ms729 ms0 KB2 KB200image/pngImage
data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAEAAAJwCAYAAABI9AvEAAACkklEQVRIS1XHdxQIZBiFcTtCkmRHqS
729 ms729 ms0 KB1 KB200image/pngImage
https://fonts.gstatic.com/s/roboto/v20/KFOlCnqEu92Fr1MmWUlfBBc4.woff2
739 ms744 ms16 KB15 KB200font/woff2Font
https://d1y5yrbkjijoq3.cloudfront.net/hqqzhj62ez8m/assets/5fxn3bxw.mp4
803 ms1057 ms4149 KB3072 KB206video/mp4Media
https://www.google-analytics.com/analytics.js
836 ms841 ms18 KB43 KB200text/javascriptScript
https://www.google-analytics.com/r/collect?v=1&_v=j79&a=1347536289&t=pageview&_s=1&dl=https%3A%2F%2Fwww.landen.co%2F&ul=en-us&de=UTF-8&dt=Landen%3A%20The%20Website%20Platform%20for%20Startups&sd=24-bit&sr=800x600&vp=1350x940&je=0&_u=IEBAAUAB~&jid=667474436&gjid=1667464489&cid=1976961926.1569970045&tid=UA-115144659-2&_gid=1967389517.1569970045&_r=1>m=2ou9p0&z=1454795177
916 ms926 ms0 KB0 KB200image/gifImage
https://www.landen.co/api/view
1877 ms1965 ms0 KB0 KB200application/jsonXHR
Serve static assets with an efficient cache policy - 4 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.

URL
Cache TTLSize
https://d1y5yrbkjijoq3.cloudfront.net/hqqzhj62ez8m/assets/5fxn3bxw.mp4
0 ms4149 KB
https://cdn.landen.co/hqqzhj62ez8m/assets/mxoofvds.svg
0 ms40 KB
https://cdn.landen.co/hqqzhj62ez8m/assets/main.a727a989.css
0 ms10 KB
https://www.google-analytics.com/analytics.js
7200000 ms18 KB
Third-Party Usage - 2 Third-Parties Found
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 more.

Third-Party
SizeMain Thread Time
18 KB25 ms
27 KB15 ms
Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
646 ms
6 ms
656 ms
5 ms
675 ms
20 ms
698 ms
5 ms
704 ms
17 ms
721 ms
15 ms
737 ms
5 ms
742 ms
65 ms
808 ms
14 ms
822 ms
11 ms
839 ms
6 ms
846 ms
9 ms
855 ms
36 ms
897 ms
13 ms
910 ms
25 ms
Preconnect to required origins
Consider adding preconnect or dns-prefetch resource hints to establish early connections to important third-party origins. Learn more.

Minify CSS
Minifying CSS files can reduce network payload sizes. Learn more.

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. Learn more.

Defer offscreen images
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn more.

Minimize Critical Requests Depth - 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. Learn more.

Preload key requests
Consider using to prioritize fetching resources that are currently requested later in page load. Learn more.

Minify JavaScript
Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.

User Timing marks and measures
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more.

Use video formats for animated content
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Learn more.

Server response times are low (TTFB) - Root document took 260 ms
Time To First Byte identifies the time at which your server sends a response. Learn more.

Efficiently encode images
Optimized images load faster and consume less cellular data. Learn more.

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. Learn more.


Page Speed (Google PageSpeed Insights) - Mobile

80
0-49 50-89 90-100 i

Field Data

Over the last 30 days, the field data shows that this page has a 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.

Origin Data

All pages served from this origin have an 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.

Lab Data

Max Potential First Input Delay 90 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task. Learn more.
Time to Interactive 4.7 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
First Contentful Paint (3G) 6120 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network. Learn more.
Estimated Input Latency 10 ms
Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy. Learn more.
Total Blocking Time 20 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Speed Index 3.7 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 4.4 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. Learn more.
First Contentful Paint 3.1 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.
Performance budget
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more.
First Meaningful Paint 3.1 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more.

Screenshot Thumbnails

This is what the load of your site looked like.

Eliminate render-blocking resources - Potential savings of 780 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.

URL
SizePotential Savings
https://cdn.landen.co/hqqzhj62ez8m/assets/main.a727a989.css
10 KB780
https://fonts.googleapis.com/css?family=Roboto:700
1 KB780
Enable text compression - Potential savings of 61 KB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.

URL
SizePotential Savings
https://www.landen.co/
75 KB61 KB
Network Requests
Lists the network requests that were made during page load.

URL
Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
http://landen.co/
0 ms197 ms0 KB0 KB307text/html
https://landen.co/
197 ms283 ms0 KB0 KB307text/html
https://www.landen.co/
284 ms570 ms75 KB75 KB200text/htmlDocument
https://cdn.landen.co/hqqzhj62ez8m/assets/main.a727a989.css
582 ms696 ms10 KB45 KB200text/cssStylesheet
https://fonts.googleapis.com/css?family=Roboto:700
583 ms601 ms1 KB2 KB200text/cssStylesheet
https://www.googletagmanager.com/gtag/js?id=UA-115144659-2
583 ms608 ms27 KB69 KB200application/javascriptScript
https://landen.imgix.net/hqqzhj62ez8m/assets/w4yv55bl.svg?w=240
583 ms620 ms5 KB12 KB200image/svg+xmlImage
https://landen.imgix.net/hqqzhj62ez8m/assets/udvwi5p9.svg
614 ms632 ms15 KB49 KB200image/svg+xmlImage
https://landen.imgix.net/hqqzhj62ez8m/assets/0fd0ppwq.png?w=1200&h=900&fit=max,https://landen.imgix.net/hqqzhj62ez8m/assets/0fd0ppwq.png?w=1200&h=900&fit=max&dpr=2
621 ms703 ms89 KB89 KB200image/pngImage
https://cdn.landen.co/hqqzhj62ez8m/assets/mxoofvds.svg
634 ms708 ms40 KB57 KB200image/svg+xmlImage
https://www.google-analytics.com/analytics.js
708 ms713 ms18 KB43 KB200text/javascriptScript
data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAMAAAADACAYAAABS3GwHAAAAAXNSR0IArs4c6QAABqVJREFUeNrt3c
760 ms760 ms0 KB2 KB200image/pngImage
data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAEAAAJwCAYAAABI9AvEAAACkklEQVRIS1XHdxQIZBiFcTtCkmRHqS
760 ms760 ms0 KB1 KB200image/pngImage
https://d1y5yrbkjijoq3.cloudfront.net/hqqzhj62ez8m/assets/5fxn3bxw.mp4
834 ms1923 ms4149 KB3072 KB206video/mp4Media
https://www.google-analytics.com/r/collect?v=1&_v=j79&a=2069664003&t=pageview&_s=1&dl=https%3A%2F%2Fwww.landen.co%2F&ul=en-us&de=UTF-8&dt=Landen%3A%20The%20Website%20Platform%20for%20Startups&sd=24-bit&sr=412x660&vp=412x660&je=0&_u=IEBAAUAB~&jid=967332872&gjid=758315743&cid=919915971.1569970037&tid=UA-115144659-2&_gid=1281791706.1569970037&_r=1>m=2ou9p0&z=923933837
875 ms880 ms0 KB0 KB200image/gifImage
https://www.landen.co/api/view
1855 ms2152 ms0 KB0 KB200application/jsonXHR
Serve static assets with an efficient cache policy - 4 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.

URL
Cache TTLSize
https://d1y5yrbkjijoq3.cloudfront.net/hqqzhj62ez8m/assets/5fxn3bxw.mp4
0 ms4149 KB
https://cdn.landen.co/hqqzhj62ez8m/assets/mxoofvds.svg
0 ms40 KB
https://cdn.landen.co/hqqzhj62ez8m/assets/main.a727a989.css
0 ms10 KB
https://www.google-analytics.com/analytics.js
7200000 ms18 KB
Third-Party Usage - 2 Third-Parties Found
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 more.

Third-Party
SizeMain Thread Time
18 KB83 ms
27 KB25 ms
Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
589 ms
6 ms
632 ms
5 ms
638 ms
13 ms
651 ms
12 ms
716 ms
11 ms
730 ms
7 ms
737 ms
23 ms
759 ms
11 ms
771 ms
67 ms
839 ms
13 ms
856 ms
11 ms
872 ms
21 ms
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. Learn more.

URL
Total CPU TimeScript EvaluationScript Parse
Other
1484 ms16 ms3 ms
https://www.google-analytics.com/analytics.js
83 ms79 ms4 ms
https://www.landen.co/
64 ms57 ms7 ms
Defer offscreen images - Potential savings of 129 KB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn more.

URL
SizePotential Savings
https://landen.imgix.net/hqqzhj62ez8m/assets/0fd0ppwq.png?w=1200&h=900&fit=max,https://landen.imgix.net/hqqzhj62ez8m/assets/0fd0ppwq.png?w=1200&h=900&fit=max&dpr=2
89 KB89 KB
https://cdn.landen.co/hqqzhj62ez8m/assets/mxoofvds.svg
40 KB40 KB
Remove unused CSS - Potential savings of 7 KB
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity. Learn more.

URL
SizePotential Savings
https://cdn.landen.co/hqqzhj62ez8m/assets/main.a727a989.css
10 KB7 KB
Avoids enormous network payloads - Total size was 283 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
https://landen.imgix.net/hqqzhj62ez8m/assets/0fd0ppwq.png?w=1200&h=900&fit=max,https://landen.imgix.net/hqqzhj62ez8m/assets/0fd0ppwq.png?w=1200&h=900&fit=max&dpr=2
89 KB
https://www.landen.co/
75 KB
https://cdn.landen.co/hqqzhj62ez8m/assets/mxoofvds.svg
40 KB
https://www.googletagmanager.com/gtag/js?id=UA-115144659-2
27 KB
https://www.google-analytics.com/analytics.js
18 KB
https://landen.imgix.net/hqqzhj62ez8m/assets/udvwi5p9.svg
15 KB
https://cdn.landen.co/hqqzhj62ez8m/assets/main.a727a989.css
10 KB
https://landen.imgix.net/hqqzhj62ez8m/assets/w4yv55bl.svg?w=240
5 KB
https://fonts.googleapis.com/css?family=Roboto:700
1 KB
https://www.google-analytics.com/r/collect?v=1&_v=j79&a=2069664003&t=pageview&_s=1&dl=https%3A%2F%2Fwww.landen.co%2F&ul=en-us&de=UTF-8&dt=Landen%3A%20The%20Website%20Platform%20for%20Startups&sd=24-bit&sr=412x660&vp=412x660&je=0&_u=IEBAAUAB~&jid=967332872&gjid=758315743&cid=919915971.1569970037&tid=UA-115144659-2&_gid=1281791706.1569970037&_r=1>m=2ou9p0&z=923933837
0 KB
Minimizes main-thread work - 1.7 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.

Category
Time Spent
Other
545 ms
Rendering
442 ms
Style & Layout
412 ms
Script Evaluation
170 ms
Parse HTML & CSS
66 ms
Script Parsing & Compilation
22 ms
Serve images in next-gen formats - Potential savings of 52 KB
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more.

URL
SizePotential Savings
https://landen.imgix.net/hqqzhj62ez8m/assets/0fd0ppwq.png?w=1200&h=900&fit=max,https://landen.imgix.net/hqqzhj62ez8m/assets/0fd0ppwq.png?w=1200&h=900&fit=max&dpr=2
89 KB52 KB
Avoids an excessive DOM size - 770 elements
Browser engineers recommend pages contain fewer than ~1,500 DOM elements. The sweet spot is a tree depth < 32 elements and fewer than 60 children/parent element. A large DOM can 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). Learn more.

Statistic
ElementValue
Total DOM Elements
770
Maximum DOM Depth
12
Maximum Child Elements
16
Avoid multiple page redirects - Potential savings of 1,110 ms
Redirects introduce additional delays before the page can be loaded. Learn more.

URL
Time Spent
(Initial: http://landen.co/)
0
https://landen.co/
630
https://www.landen.co/
480
Keep request counts low and transfer sizes small - 16 requests • 4,432 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
Total
164432 KB
Media
14149 KB
Image
7151 KB
Document
175 KB
Script
245 KB
Stylesheet
211 KB
Other
31 KB
Font
00 KB
Third-party
104306 KB
Efficiently encode images
Optimized images load faster and consume less cellular data. Learn more.

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. Learn more.

All text remains visible during webfont loads
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more.

Preconnect to required origins
Consider adding preconnect or dns-prefetch resource hints to establish early connections to important third-party origins. Learn more.

Minify CSS
Minifying CSS files can reduce network payload sizes. Learn more.

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. Learn more.

Properly size images
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.

Minimize Critical Requests Depth - 2 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. Learn more.

Preload key requests
Consider using to prioritize fetching resources that are currently requested later in page load. Learn more.

Minify JavaScript
Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.

User Timing marks and measures
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more.

Use video formats for animated content
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Learn more.

Server response times are low (TTFB) - Root document took 290 ms
Time To First Byte identifies the time at which your server sends a response. Learn more.

Page Speed (Google PageSpeed Insights) - v2

Suggestions Summary

Avoid landing page redirects

Your page has 2 redirects. Redirects introduce additional delays before the page can be loaded.

Avoid landing page redirects for the following chain of redirected URLs.

http://landen.co/
https://landen.co/
https://www.landen.co/

Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 2 blocking CSS resources. This causes a delay in rendering your page.

None of the above-the-fold content on your page could be rendered without waiting for the following resources to load. Try to defer or asynchronously load blocking resources, or inline the critical portions of those resources directly in the HTML.Optimize CSS Delivery of the following:

https://cdn.landen.co/hqqzhj62ez8m/assets/main.a727a989.css
https://fonts.googleapis.com/css?family=Roboto:700

Size tap targets appropriately

Some of the links/buttons on your webpage may be too small for a user to easily tap on a touchscreen. Consider making these tap targets larger to provide a better user experience.

The following tap targets are close to other nearby tap targets and may need additional spacing around them.

The tap target <a href="/generator">Generator</a> and 17 others are close to other tap targets.

Enable compression

Compressing resources with gzip or deflate can reduce the number of bytes sent over the network.

Enable compression for the following resources to reduce their transfer size by 61KiB (81% reduction).

Compressing https://www.landen.co/ could save 61KiB (81% reduction).

Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Leverage browser caching for the following cacheable resources:

https://cdn.landen.co/hqqzhj62ez8m/assets/main.a727a989.css (expiration not specified)
https://cdn.landen.co/hqqzhj62ez8m/assets/mxoofvds.svg (expiration not specified)
https://www.landen.co/api/view (expiration not specified)
https://www.googletagmanager.com/gtag/js?id=UA-115144659-2 (15 minutes)
https://www.google-***ytics.com/***ytics.js (2 hours)

Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 30.5KiB (35% reduction).

Compressing https://landen.imgix.net/hqqzhj62ez8m/assets/0fd0ppwq.png?w=1200&h=900&fit=max,https://landen.imgix.net/hqqzhj62ez8m/assets/0fd0ppwq.png?w=1200&h=900&fit=max&dpr=2 could save 30.5KiB (35% reduction).
Avoid plugins
Your page does not appear to use plugins, which would prevent content from being usable on many platforms. Learn more about the importance of avoiding plugins.
Configure the viewport
Your page specifies a viewport matching the device's size, which allows it to render properly on all devices. Learn more about configuring viewports.
Reduce server response time
Your server responded quickly. Learn more about server response time optimization.
Minify CSS
Your CSS is minified. Learn more about minifying CSS.
Minify HTML
Your HTML is minified. Learn more about minifying HTML.
Minify JavaScript
Your JavaScript content is minified. Learn more about minifying JavaScript.
Prioritize visible content
You have the above-the-fold content properly prioritized. Learn more about prioritizing visible content.
Size content to viewport
The contents of your page fit within the viewport. Learn more about sizing content to the viewport.
Use legible font sizes
The text on your page is legible. Learn more about using legible font sizes.
Download optimized image, JavaScript, and CSS resources for this page.

+ Does landen.co use compression?

landen.co does not use compression.
Original size: 75.27 KB
Compressed size: n/a
File reduced by: n/a

+ Google Safe Browsing

This site is not currently listed as suspicious

MyWot.com Reputation Ratings

Trustworthiness:
  n/a
Vendor reliability:
  n/a
Privacy:
  n/a
Child safety:
  n/a

+ SSL Checker - SSL Certificate Verify

landen.co supports HTTPS
loader
Verifying SSL Support. Please wait...
Common Name: *.landen.co
Organization:
Location:
Issuer: Let's Encrypt Authority X3
Valid from: Aug 21 18:17:07 2019 GMT
Valid until: Nov 19 18:17:07 2019 GMT
Authority:
Keysize:

+ Verify HTTP/2 Support

landen.co supports HTTP/2
loader
Verifying HTTP/2.0 Support. Please wait...

+ Site Categories (dmoz)

Currently Not Available

+ Http Header

Content-Type: text/html;charset=utf-8
Location: https://landen.co/
Date: Tue, 01 Oct 2019 22:47:03 GMT
Content-Length: 0

HTTP/2 307 
content-type: text/html;charset=utf-8
location: https://www.landen.co/
content-length: 0
date: Tue, 01 Oct 2019 22:47:03 GMT

HTTP/2 200 
content-type: text/html;charset=utf-8
x-cache: hit
date: Tue, 01 Oct 2019 22:47:04 GMT

+ DNS Lookup

Type Ip Target TTL
TXT 300
MX aspmx.l.google.com 300
MX alt1.aspmx.l.google.com 300
MX alt2.aspmx.l.google.com 300
MX aspmx2.googlemail.com 300
MX aspmx3.googlemail.com 300
SOA 900
Mname ns-159.awsdns-19.com
Rname awsdns-hostmaster.amazon.com
Serial Number 1
Refresh 7200
Retry 900
Expire 1209600
Minimum TTL 0
A 54.71.114.71 273
NS ns-159.awsdns-19.com 3572
NS ns-959.awsdns-55.net 3572
NS ns-1415.awsdns-48.org 3572
NS ns-1948.awsdns-51.co.uk 3572

+ Whois Lookup

Domain Created:
2018-02-22
Domain Age:
1 years 7 months 7 days  
WhoIs:
 

whois lookup at whois.nic.co...
Domain Name: landen.co
Registry Domain ID: D1501C4B8FF984D02B8D822D00BA55890-NSR
Registrar WHOIS Server:
Registrar URL: www.name.com
Updated Date: 2019-02-01T18:01:54Z
Creation Date: 2018-02-22T04:16:53Z
Registry Expiry Date: 2020-02-22T04:16:53Z
Registrar: Name.com, Inc.
Registrar IANA ID: 625
Registrar Abuse Contact Email: email
Registrar Abuse Contact Phone: +1.7203101849
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Registry Registrant ID:
Registrant Name:
Registrant Organization: Domain Protection Services, Inc.
Registrant Street:
Registrant Street:
Registrant Street:
Registrant City:
Registrant State/Province: CO
Registrant Postal Code:
Registrant Country: US
Registrant Phone:
Registrant Phone Ext:
Registrant Fax:
Registrant Fax Ext:
Registrant Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Registry Admin ID:
Admin Name:
Admin Organization:
Admin Street:
Admin Street:
Admin Street:
Admin City:
Admin State/Province:
Admin Postal Code:
Admin Country:
Admin Phone:
Admin Phone Ext:
Admin Fax:
Admin Fax Ext:
Admin Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Registry Tech ID:
Tech Name:
Tech Organization:
Tech Street:
Tech Street:
Tech Street:
Tech City:
Tech State/Province:
Tech Postal Code:
Tech Country:
Tech Phone:
Tech Phone Ext:
Tech Fax:
Tech Fax Ext:
Tech Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Name Server: ns-959.awsdns-55.net
Name Server: ns-1948.awsdns-51.co.uk
Name Server: ns-1415.awsdns-48.org
Name Server: ns-159.awsdns-19.com
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of WHOIS database: 2019-10-01T22:47:30Z <<<

For more information on Whois status codes, please visit https://icann.org/epp

The above WHOIS results have been redacted to remove potential personal data. The full WHOIS output may be available to individuals and organisations with a legitimate interest in accessing this data not outweighed by the fundamental privacy rights of the data subject. To find out more, or to make a request for access, please visit: RDDSrequest.nic.co.

.CO Internet, S.A.S., the Administrator for .CO, has collected this information for the WHOIS database through Accredited Registrars. This information is provided to you for informational purposes only and is designed to assist persons in determining contents of a domain name registration record in the .CO Internet registry database. .CO Internet makes this information available to you "as is" and does not guarantee its accuracy.

By submitting a WHOIS query, you agree that you will use this data only for lawful purposes and that, under no cir***stances will you use this data: (1) to allow, enable, or otherwise support the transmission of mass unsolicited, commercial advertising or solicitations via direct mail, electronic mail, or by telephone; (2) in contravention of any applicable data and privacy protection laws; or (3) to enable high volume, automated, electronic processes that apply to the registry (or its systems). Compilation, repackaging, dissemination, or other use of the WHOIS database in its entirety, or of a substantial portion thereof, is not allowed without .CO Internet's prior written permission. .CO Internet reserves the right to modify or change these conditions at any time without prior or subsequent notification of any kind. By executing this query, in any manner whatsoever, you agree to abide by these terms. In some limited cases, domains that might appear as available in whois might not actually be available as they could be already registered and the whois not yet updated and/or they could be part of the Restricted list. In this cases, performing a check through your Registrar's (EPP check) will give you the actual status of the domain. Additionally, domains currently or previously used as extensions in 3rd level domains will not be available for registration in the 2nd level. For example, org.co,mil.co,edu.co,com.co,net.co,nom.co,arts.co, firm.co,info.co,int.co,web.co,rec.co,co.co.

NOTE: FAILURE TO LOCATE A RECORD IN THE WHOIS DATABASE IS NOT INDICATIVE OF THE AVAILABILITY OF A DOMAIN NAME. All domain names are subject to certain additional domain name registration rules. For details, please visit our site at www.cointernet.co <http://www.cointernet.co>.
Last update was 140 days ago
loader
This can take up to 60 seconds. Please wait...

*HypeStat.com is not linking to, promoting or affiliated with landen.co in any way. Only publicly available statistics data are displayed.

Recently Analyzed Sites

myetherwallet.com
39 secs
bdgovtjob.net
47 secs
arbistar.pw
1 min
mycrypto.com
1 min
provrach.ru
2 mins
podkovyrova.ru
3 mins
masalpromo.com
4 mins
free-bonus.icu
4 mins
retail-focus.co.uk
4 mins
vip-tor.top
5 mins
WHAT WE RECOMMEND:
We are using the world's No. 1 Marketing Tool to grow our website. Activate your FREE trial today!

BrowserExtension

Install HypeStat extension in your browser to see statistics and technologies used with one click.

Hide/Remove your site data

• Use Show/Hide ESTIMATED data form to hide (Website worth, Daily ads revenue, Daily Visits, Daily Pageviews)
• Use Show/Hide WHOIS data form to hide whois data
• Use Remove form to remove all data
• If you have any problem with REMOVE/HIDE your data just drop an email at support (at) hypestat.com and we will remove/hide your site data manualy.
Make custom Widget for your website
Get the code now!
landen.co widget