SEO Rank : 26 Website URL: ddl-island.co Last Updated: 4 months
Success
32% of passed verification steps
Warning
30% of total warning
Errors
38% of total errors, require fast action
Share
Estimation Traffic and Earnings
322
Unique Visits
Daily
595
Pages Views
Daily
$0
Income
Daily
9,016
Unique Visits
Monthly
16,958
Pages Views
Monthly
$0
Income
Monthly
104,328
Unique Visits
Yearly
199,920
Pages Views
Yearly
$0
Income
Yearly
Desktop
Mobile
Moz Authority Rank
Page Authority
Authority 0%
Domain Authority
Domain Authority 0%
Moz Rank
0.0/10
Bounce Rate
Rate 0%
Meta Data
Title Tag
47 Characters
ERROR: THE REQUESTED URL COULD NOT BE RETRIEVED
Meta Description
0 Characters
NO DATA
Effective URL
21 Characters
https://ddl-island.co
Excerpt
Page content
ERROR: The requested URL could not be retrieved
ERROR
The requested URL could not be retrieved
The following error was encountered while trying to retrieve the URL: http://ddl-island.co/
Unable to forward this request at this time.
This re...
Google Preview
Your look like this in google search result
ERROR: THE REQUESTED URL COULD NOT BE RETRIEVED
https://ddl-island.co
ERROR: The requested URL could not be retrieved
ERROR
The requested URL could not be retrieved
The following error was encountered while trying to retrieve the URL: http://ddl-island.co/
Unable to forward this request at this time.
This re...
Robots.txt
File No Found
Sitemap.xml
File No Found
Page Size
Code & Text Ratio
Document Size: ~3.14 KB
Code Size: ~2.52 KB
Text Size: ~638 B Ratio: 19.84%
Social Data
Desktop
Mobile
Serve images in next-gen formats
Potential savings of 127 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
Largest Contentful Paint
2.8 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Remove unused JavaScript
Potential savings of 327 KB
Remove unused JavaScript to reduce bytes consumed by network activity
Total Blocking Time
4,480 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
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
Avoids enormous network payloads
Total size was 2,109 KB
Large network payloads cost users real money and are highly correlated with long load times
Avoid large layout shifts
5 elements found
These DOM elements contribute most to the CLS of the page.
Largest Contentful Paint element
1 element found
This is the element that was identified as the Largest Contentful Paint
First Contentful Paint
2.1 s
First Contentful Paint marks the time at which the first text or image is painted
Reduce JavaScript execution time
10.1 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Reduce the impact of third-party code
Third-party code blocked the main thread for 310 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
105 resources found
A long cache lifetime can speed up repeat visits to your page
Keep request counts low and transfer sizes small
314 requests • 2,109 KB
To set budgets for the quantity and size of page resources, add a budget.json file
First Contentful Paint (3G)
4025 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
First Meaningful Paint
3.5 s
First Meaningful Paint measures when the primary content of a page is visible
Eliminate render-blocking resources
Potential savings of 1,260 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
User Timing marks and measures
1 user timing
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences
Initial server response time was short
Root document took 300 ms
Keep the server response time for the main document short because all other requests depend on it
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
Tap targets are not sized appropriately
77% appropriately sized tap targets
Interactive elements like buttons and links should be large enough (48x48px), and have enough space around them, to be easy enough to tap without overlapping onto other elements
Efficiently encode images
Potential savings of 23 KB
Optimized images load faster and consume less cellular data
Avoid an excessive DOM size
861 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)
Document doesn't use legible font sizes
54.38% 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
Max Potential First Input Delay
2,350 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Includes front-end JavaScript libraries with known security vulnerabilities
6 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Estimated Input Latency
1,500 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
Enable text compression
Potential savings of 117 KB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes
Page load is not fast enough on mobile networks
Interactive at 20.6 s
A fast page load over a cellular network ensures a good mobile user experience
Avoid chaining critical requests
8 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
Speed Index
10.2 s
Speed Index shows how quickly the contents of a page are visibly populated
Defer offscreen images
Potential savings of 3 KB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Time to Interactive
20.6 s
Time to interactive is the amount of time it takes for the page to become fully interactive
First CPU Idle
11.6 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. [Learn more](https://web.dev/first-cpu-idle).
Minimize main-thread work
18.3 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
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
Warning! Your site not have a robots.txt file
Sitemap.xml
Warning! Not 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
Warning! Domain Authority of your website is slow. It is good to have domain authority more than 25.
GZIP Compress
Warning! Your site not is compressed, this can make slower response for the visitors
Favicon
Warning! Your site not have a favicon
Broken Links
Warning! You have broken links
View links
| First 1 Links | Relationship | HTTP Status |
| http://ddl-island.co/ | Internal Link | 500 |
Alexa Rank
424
Local Rank: MU / Users: 100.0% / PageViews: 100.0%681,754
Global RankDomain Available
| Domain (TDL) and Typo | Status |
|---|---|
| ddl-island.co | Already Registered |
| ddl-island.us | Available Buy Now! |
| ddl-island.com | Already Registered |
| ddl-island.org | Already Registered |
| ddl-island.net | Available Buy Now! |
| dl-island.co | Available Buy Now! |
| edl-island.co | Available Buy Now! |
| cdl-island.co | Available Buy Now! |
Information Server
Response Header
HTTP headers carry information about the client browser, the requested page and the server
HTTP/2 500
date: Fri, 07 Aug 2020 12:09:48 GMT
content-type: text/html;charset=utf-8
set-cookie: __cfduid=d5c94f527d542c1812c57246b6d2aa3c01596802188; expires=Sun, 06-Sep-20 12:09:48 GMT; path=/; domain=.ddl-island.co; HttpOnly; SameSite=Lax; Secure
mime-version: 1.0
x-squid-error: ERR_CANNOT_FORWARD 0
cf-cache-status: DYNAMIC
cf-request-id: 046a6cdba40000eb5173157200000001
expect-ct: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
server: cloudflare
cf-ray: 5bf0e40c39d5eb51-LAX
Click to Add/Show Comments