Your Website Score is
SEO Rank : 55 Website URL: danluan.org Last Updated: 4 months
Success
70% of passed verification steps
Warning
7% of total warning
Errors
23% of total errors, require fast action
Share
Estimation Traffic and Earnings
0
Unique Visits
Daily
0
Pages Views
Daily
$0
Income
Daily
0
Unique Visits
Monthly
0
Pages Views
Monthly
$0
Income
Monthly
0
Unique Visits
Yearly
0
Pages Views
Yearly
$0
Income
Yearly
Desktop
Mobile
Moz Authority Rank
Page Authority
Authority 45%
Domain Authority
Domain Authority 42%
Moz Rank
4.5/10
Bounce Rate
Rate 0%
Meta Data
Charset
Encoding
Great, language/character encoding is specified: UTF-8
Title Tag
50 Characters
DÂN LUẬN | KHÔNG GIAN MỞ BÀY TỎ QUAN ĐIỂM CÔNG DÂN
Meta Description
0 Characters
NO DATA
Effective URL
23 Characters
https://www.danluan.org
Excerpt
Page content
Dân Luận | không gian mở bày tỏ quan điểm công dân
Skip to main content
Nguyên tắc
Vượt tường lửa
Gửi bài
Dịch thuật
RSS
Đăng nhập
Trang chủ
Trong nước
Quốc tế
Thư viện
V...
Google Preview
Your look like this in google search result
DÂN LUẬN | KHÔNG GIAN MỞ BÀY TỎ QUAN ĐIỂM CÔNG DÂN
https://www.danluan.org
Dân Luận | không gian mở bày tỏ quan điểm công dân
Skip to main content
Nguyên tắc
Vượt tường lửa
Gửi bài
Dịch thuật
RSS
Đăng nhập
Trang chủ
Trong nước
Quốc tế
Thư viện
V...
Robots.txt
File Detected
Sitemap.xml
File No Found
Page Size
Code & Text Ratio
Document Size: ~89.89 KB
Code Size: ~70.46 KB
Text Size: ~19.43 KB Ratio: 21.62%
Social Data
Delicious
Total: 0
Facebook
Total: 18,261
Google
Total: 0
Linkedin
Total: 0
Pinterest
Total: 0
Stumbleupon
Total: 0
Tumblr
Total: 0
Vk
Total: 0
Technologies
PWA - Manifest
Manifest is not valid
Your site don't have valid manifest.json, read more in Web App Manifest
Desktop
Mobile
Tap targets are not sized appropriately
90% 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
Avoid enormous network payloads
Total size was 6,711 KiB
Large network payloads cost users real money and are highly correlated with long load times
Avoid large layout shifts
3 elements found
These DOM elements contribute most to the CLS of the page.
Minimize main-thread work
19.1 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Initial server response time was short
Root document took 240 ms
Keep the server response time for the main document short because all other requests depend on it
First Contentful Paint (3G)
9518 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
Serve static assets with an efficient cache policy
44 resources found
A long cache lifetime can speed up repeat visits to your page
Speed Index
15.2 s
Speed Index shows how quickly the contents of a page are visibly populated
Avoid an excessive DOM size
933 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)
Total Blocking Time
4,760 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Avoid serving legacy JavaScript to modern browsers
Potential savings of 7 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
Remove unused JavaScript
Potential savings of 719 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
First Meaningful Paint
4.6 s
First Meaningful Paint measures when the primary content of a page is visible
Defer offscreen images
Potential savings of 738 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
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
Serve images in next-gen formats
Potential savings of 483 KiB
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
Page load is not fast enough on mobile networks
Interactive at 43.6 s
A fast page load over a cellular network ensures a good mobile user experience
Max Potential First Input Delay
700 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Avoid chaining critical requests
40 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
Network Round Trip Times
0 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance
Efficiently encode images
Potential savings of 113 KiB
Optimized images load faster and consume less cellular data
Reduce the impact of third-party code
Third-party code blocked the main thread for 5,790 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
User Timing marks and measures
21 user timings
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences
Includes front-end JavaScript libraries with known security vulnerabilities
4 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Document uses legible font sizes
99.39% 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
First CPU Idle
13.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/).
Eliminate render-blocking resources
Potential savings of 3,350 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Reduce JavaScript execution time
12.0 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Estimated Input Latency
270 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
Largest Contentful Paint element
1 element found
This is the largest contentful element painted within the viewport
Remove unused CSS
Potential savings of 47 KiB
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
Time to Interactive
43.6 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Does not use HTTPS
3 insecure requests found
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding [mixed content](https://developers.google.com/web/fundamentals/security/prevent-mixed-content/what-is-mixed-content), where some resources are loaded over HTTP despite the initial request being servedover HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs
Cumulative Layout Shift
0.202
Cumulative Layout Shift measures the movement of visible elements within the viewport
Avoids large JavaScript libraries with smaller alternatives
0 large libraries found
Large JavaScript libraries can lead to poor performance. Prefer smaller, functionally equivalent libraries to reduce your bundle size
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
Minify CSS
Potential savings of 3 KiB
Minifying CSS files can reduce network payload sizes
First Contentful Paint
4.5 s
First Contentful Paint marks the time at which the first text or image is painted
Keep request counts low and transfer sizes small
380 requests • 6,711 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Largest Contentful Paint
19.1 s
Largest Contentful Paint marks the time at which the largest text or image is painted
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
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
Congratulations! Your site not 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
0
Local Rank: / Users: / PageViews:
Global Rank
Domain Available
| Domain (TDL) and Typo | Status |
|---|---|
| danluan.co | Already Registered |
| danluan.us | Already Registered |
| danluan.com | Already Registered |
| danluan.org | Already Registered |
| danluan.net | Already Registered |
| dnluan.org | Already Registered |
| eanluan.org | Already Registered |
| canluan.org | Already Registered |
Information Server
Response Header
HTTP headers carry information about the client browser, the requested page and the server
HTTP/2 200
date: Tue, 20 Oct 2020 00:04:19 GMT
content-type: text/html
set-cookie: __cfduid=deb72c980f02eb60d089c3cbc3acd246a1603152258; expires=Thu, 19-Nov-20 00:04:18 GMT; path=/; domain=.danluan.org; HttpOnly; SameSite=Lax; Secure
last-modified: Mon, 19 Oct 2020 05:05:50 GMT
expires: Tue, 22 Sep 1974 08:00:00 GMT
cache-control: must-revalidate, post-check=0, pre-check=0
cf-cache-status: DYNAMIC
cf-request-id: 05e4eb3e670000eb6dff8c3000000001
expect-ct: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
server: cloudflare
cf-ray: 5e4e7b10989deb6d-LAX
content-encoding: gzip
Click to Add/Show Comments