Overview Review Traffic Revenue SEO
Hosting Registration Security Technical Related

travel.blog

travel.blog is SSL secured

Free website and domain report on travel.blog

Last Updated: 7th December, 2020 Update Now
Overview

Snoop Summary for travel.blog

This is a free and comprehensive report about travel.blog. The domain travel.blog is currently hosted on a server located in United States with the IP address 192.0.78.31, where USD is the local currency and the local language is English. Travel.blog has the potential to be earning an estimated $13 USD per day from advertising revenue. If travel.blog was to be sold it would possibly be worth $9,316 USD (based on the daily revenue potential of the website over a 24 month period). Travel.blog receives an estimated 4,473 unique visitors every day - a large amount of traffic! This report was last updated 7th December, 2020.

About travel.blog

Site Preview: travel.blog travel.blog
Title: Travel.blog – Get your subdomain of travel.blog
Description: Artwork by Tony Ruth Site by Automattic Design
Keywords and Tags: internet services, phishing
Related Terms: automattic, automattic careers, automattic inc, automattic wordpress
Fav Icon:
Age:
Domain Created:
Domain Updated:
Domain Expires:
Review

Snoop Score

2/5

Valuation

$9,316 USD
Note: All valuation figures are estimates.

Popularity

Modest
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 137,093
Alexa Reach:
SEMrush Rank (US):
SEMrush Authority Score:
Moz Domain Authority: 0
Moz Page Authority: 0

Organic vs Paid (Google Ads)

Traffic

Visitors

Daily Visitors: 4,473
Monthly Visitors: 136,144
Yearly Visitors: 1,632,645
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $13 USD
Monthly Revenue: $388 USD
Yearly Revenue: $4,653 USD
Note: All revenue figures are estimates.

Revenue By Country

SEO

Backlinks Analysis (SEMrush)

Top New Follow Links

Top Ranking Keywords (US)

Domain Analysis

Value Length
Domain: travel.blog 11
Domain Name: travel 6
Extension (TLD): blog 4

Page Speed Analysis

Average Load Time:
Load Time Comparison:

PageSpeed Insights

Avg. (All Categories) 84
Performance 93
Accessibility 100
Best Practices 79
SEO 100
Progressive Web App 48
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
Simulate loading on desktop
93

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for travel.blog. This includes details about optimizing page load times which can result in a better user experience.

Metrics

First Contentful Paint — 0.8 s
The time taken for the first image or text on the page to be rendered.
Speed Index — 0.8 s
The time taken for the page contents to be visibly populated.
Time to Interactive — 0.8 s
The time taken for the page to become fully interactive.
Total Blocking Time — 0 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).

Other

First CPU Idle — 0.8 s
The time taken for the page's main thread to be quiet enough to handle input.
Max Potential First Input Delay — 20 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 0.8 s
The time taken for the primary content of the page to be rendered.
Estimated Input Latency — 10 ms
The time taken for the page to respond to user input (during the busiest 5 second window of page load). Users are likely to perceive travel.blog as laggy when the latency is higher than 0.05 seconds.
Network Requests
Below is a list of network requests that were made during page load.
URL Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://travel.blog/
0
196.38000003761
253
0
301
text/html
https://travel.blog/
196.78900000872
277.19600003911
13048
42473
200
text/html
Document
https://s1.wp.com/_static/??-eJydkOEKwjAMhF/ILg7dYD/EZ2m7UDubrjQto29vNxGGoIh/Apfcd5CDJQg9+4Q+AWURXDbWMyxBzySYrMPyphrNfIAd9mJMrlJhNPUSEYbm3LSgsnUjKDfru3BWRRkLcCoOf4jZKIYJU5ArLsuckzDRjv9GRJmsN/wB3/2/flD3FGRaHYSjleiQqu0b9ixKqRCRWdRJNpNItwpuvV3p0vbHru9OQ99NDzZijrI=?cssminify=yes
289.60000001825
308.01999999676
9616
60500
200
text/css
Stylesheet
https://s1.wp.com/_static/??/wp-content/mu-plugins/comment-likes/css/comment-likes.css,/i/noticons/noticons.css?m=1436783281j&cssminify=yes
289.79000000982
306.53800000437
22705
37496
200
text/css
Stylesheet
https://fonts.googleapis.com/css?family=Karla%3A400%2C700%2C400italic%2C700italic&subset=latin%2Clatin-ext
290.02200003015
303.98900003638
1345
2736
200
text/css
Stylesheet
https://s2.wp.com/_static/??-eJx9i9EKwjAMAH/IGousb+K3bCV2kbQpTerY3zvxxSHs7Q7uYKkuSjEsBjZjRoXaJ5D2IgW1lfEcVU9wlFGJ39QtNUr+G3J3lXuiopBQHEscjaTsxD14pHa0NpxY0oYJtupHP9M93/xwvYTBh+Cfb7HhTvU=?cssminify=yes
290.26000003796
309.97300002491
10282
52883
200
text/css
Stylesheet
https://s0.wp.com/_static/??-eJxti8sKgCAQAH8oW6KHdoi+xcTUWF1pjX4/OnSIOg0DM3BmYSgVmwrEQ2Q8XEgMmbiIFXXYgb3eQ3IPa8Ncwf/FZIJGgeToLZ+peBstg+/AIS0a72COU9OPUg69atV2AWWKN+I=?cssminify=yes
290.43699998874
308.5120000178
11680
29360
200
text/css
Stylesheet
https://s2.wp.com/_static/??/wp-includes/js/jquery/jquery.js,/wp-content/js/postmessage.js,/wp-content/js/mobile-useragent-info.js?m=1558356653j
290.7600000035
324.26700001815
43192
134928
200
application/x-javascript
Script
https://s1.wp.com/?custom-css=1&csblog=83xvQ&cscache=6&csrev=4
290.94299999997
307.19700001646
1955
5159
200
text/css
Stylesheet
https://0.gravatar.com/js/gprofiles.js?ver=202050y
291.25499998918
307.56799998926
7732
24042
200
application/javascript
Script
https://s1.wp.com/wp-content/mu-plugins/gravatar-hovercards/wpgroho.js?m=1380573781h
291.37900000205
305.77000003541
674
582
200
application/javascript
Script
https://s1.wp.com/_static/??-eJyVzlEKwjAMBuALWaMwpz6IZ+m6dsu6pqVpN49vFYTpRPApIfk/EpiDUJ6SpgQDQ6snVDrctgNvYLFyWYQxd0gMyjtXRmJEq/lhRmyAZwz6H/Q2+ISp167EQm7AxwmfgC2GkiYrjFeZhcHVk9+YyaQSelrdWDwnW4ckGhnBSU46lk6kKJX9hYLnJMwoMQL3MiJ1r1rQ1V329a6ujqdzdRjuWPyEaw==
291.58399999142
311.0769999912
24447
90053
200
application/javascript
Script
https://stats.wp.com/w.js?61
338.3540000068
353.61400002148
4802
13423
200
application/javascript
Script
https://s1.wp.com/wp-includes/js/wp-emoji-release.min.js?m=1605528427h&ver=5.6-RC2-49736
341.72900003614
356.78999999072
5078
14246
200
application/javascript
Script
https://s2.wp.com/wp-content/mu-plugins/global-print/global-print.css?m=1465851035h&cssminify=yes
361.86900001485
376.35400000727
2293
5605
200
text/css
Stylesheet
https://a8ctraveldotblog.files.wordpress.com/2017/12/travel_1600_90.jpg?w=924&h=1&crop=1
387.17400003225
517.72000000346
480075
479604
200
image/webp
Image
https://fonts.gstatic.com/s/karla/v14/qkBbXvYC6trAT7RVLtyU5rZP.woff2
407.7099999995
410.37300002063
26935
26368
200
font/woff2
Font
https://0.gravatar.com/dist/css/hovercard.min.css?ver=202050y
410.8380000107
426.12700001337
2175
7814
200
text/css
Stylesheet
https://0.gravatar.com/dist/css/services.min.css?ver=202050y
410.94800003339
425.6400000304
847
2644
200
text/css
Stylesheet
https://graph.facebook.com/?callback=WPCOMSharing.update_facebook_count&ids=https%3A%2F%2Ftravel.blog%2F
421.21800000314
520.20000002813
923
244
200
text/javascript
Script
https://pixel.wp.com/g.gif?v=wpcom-no-pv&x_sharing-count-request=facebook&r=0.7826456235487786
421.96000000695
435.97400002182
215
50
200
image/gif
Image
https://r-login.wordpress.com/remote-login.php?wpcom_remote_login=key&origin=aHR0cHM6Ly90cmF2ZWwuYmxvZw%3D%3D&wpcomid=119054498&time=1607318368
425.47200003173
534.42400001222
527
131
200
text/html
Document
https://pixel.wp.com/g.gif?x_stats-initial-visibility=visible&v=wpcom-no-pv&rand=0.7195736459929805
433.64800000563
448.42400000198
215
50
200
image/gif
Image
https://pixel.wp.com/g.gif?blog=119054498&v=wpcom&tz=0&user_id=0&post=18&subd=a8ctraveldotblog&host=travel.blog&ref=&fcp=403&rand=0.9397765998647272
433.80300002173
449.00100002997
215
50
200
image/gif
Image
https://pixel.wp.com/g.gif?crypt=UE40eW5QN0p8M2Y%2FRE1lSiYrZXhzUkM5fD1uTDNLUGt6QzVbd3FKb3Q4aWxFU0VMK3ppSG1wamM0bi81JStxN2lKP1pvVnxQRHk3W0d3VEh0SklpNENJfHppaiZjVlFtdzJJS0ovSDNELm8yQjlZJUssV0xnJVFXQ1BbWi84eCZlbyt6VmomVjJyNVFYSjByZiV2UTBpSXNjJi0lW0REYUlobmdjNXB5ZzZOMTAtU3lKMGtTMVBBdiU2bCsyVUwvN0xmSWcxPUl5L1tCaG1tdVBHUUt0dkwtSyx2TXpEZFJnVjFkK104V1AxP1QxNlRXMGJNfix8cmtuNlpUOStzWzZpLHUtWVc9aGduamxKV3NyajlRdXpOUCVlW0FvJkdwRlFPenlxfmU%3D&v=wpcom-no-pv&rand=0.19724577426381895
434.19599998742
448.79300001776
215
50
200
image/gif
Image
https://s0.wp.com/wp-content/mu-plugins/actionbar/actionbar.css?v=20201002
606.50799999712
621.76400003955
3019
12042
200
text/css
Stylesheet
https://s0.wp.com/wp-content/mu-plugins/actionbar/actionbar.js?v=20201002
606.70499998378
621.20900000446
5028
15569
200
application/javascript
Script
https://s2.wp.com/i/logo/wpcom-gray-white.png
627.01300001936
643.37000000523
8544
8203
200
image/png
Image
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
307.218
6.891
316.576
35.824
369.427
21.131
390.574
24.173
416.018
36.299
557.308
17.637
574.961
6.528
582.201
49.249
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data

Opportunities

Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Travel.blog should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Travel.blog should consider minifying CSS files.
Minify JavaScript — Potential savings of 16 KiB
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Travel.blog should consider minifying JS files.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://s1.wp.com/_static/??-eJyVzlEKwjAMBuALWaMwpz6IZ+m6dsu6pqVpN49vFYTpRPApIfk/EpiDUJ6SpgQDQ6snVDrctgNvYLFyWYQxd0gMyjtXRmJEq/lhRmyAZwz6H/Q2+ISp167EQm7AxwmfgC2GkiYrjFeZhcHVk9+YyaQSelrdWDwnW4ckGhnBSU46lk6kKJX9hYLnJMwoMQL3MiJ1r1rQ1V329a6ujqdzdRjuWPyEaw==
24447
10207
https://s2.wp.com/_static/??/wp-includes/js/jquery/jquery.js,/wp-content/js/postmessage.js,/wp-content/js/mobile-useragent-info.js?m=1558356653j
43192
6646
Remove unused CSS — Potential savings of 33 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Travel.blog should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://s1.wp.com/_static/??/wp-content/mu-plugins/comment-likes/css/comment-likes.css,/i/noticons/noticons.css?m=1436783281j&cssminify=yes
22705
22643
https://s0.wp.com/_static/??-eJxti8sKgCAQAH8oW6KHdoi+xcTUWF1pjX4/OnSIOg0DM3BmYSgVmwrEQ2Q8XEgMmbiIFXXYgb3eQ3IPa8Ncwf/FZIJGgeToLZ+peBstg+/AIS0a72COU9OPUg69atV2AWWKN+I=?cssminify=yes
11680
11619
Remove unused JavaScript — Potential savings of 21 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://s2.wp.com/_static/??/wp-includes/js/jquery/jquery.js,/wp-content/js/postmessage.js,/wp-content/js/mobile-useragent-info.js?m=1558356653j
43192
21830
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats
Image formats like PNG and JPEG have poor compression when compared to other next-gen formats, such as JPEG 200, JPEG XR and WebP.
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Initial server response time was short — Root document took 80 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
https://travel.blog/
81.405
Avoid multiple page redirects — Potential savings of 190 ms
Redirects can cause additional delays before the page can begin loading. Travel.blog should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://travel.blog/
190
https://travel.blog/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Travel.blog should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers — Potential savings of 15 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
URL Potential Savings (Bytes)
https://stats.wp.com/w.js?61
9281
https://s2.wp.com/_static/??/wp-includes/js/jquery/jquery.js,/wp-content/js/postmessage.js,/wp-content/js/mobile-useragent-info.js?m=1558356653j
6485

Diagnostics

Avoids enormous network payloads — Total size was 672 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://a8ctraveldotblog.files.wordpress.com/2017/12/travel_1600_90.jpg?w=924&h=1&crop=1
480075
https://s2.wp.com/_static/??/wp-includes/js/jquery/jquery.js,/wp-content/js/postmessage.js,/wp-content/js/mobile-useragent-info.js?m=1558356653j
43192
https://fonts.gstatic.com/s/karla/v14/qkBbXvYC6trAT7RVLtyU5rZP.woff2
26935
https://s1.wp.com/_static/??-eJyVzlEKwjAMBuALWaMwpz6IZ+m6dsu6pqVpN49vFYTpRPApIfk/EpiDUJ6SpgQDQ6snVDrctgNvYLFyWYQxd0gMyjtXRmJEq/lhRmyAZwz6H/Q2+ISp167EQm7AxwmfgC2GkiYrjFeZhcHVk9+YyaQSelrdWDwnW4ckGhnBSU46lk6kKJX9hYLnJMwoMQL3MiJ1r1rQ1V329a6ujqdzdRjuWPyEaw==
24447
https://s1.wp.com/_static/??/wp-content/mu-plugins/comment-likes/css/comment-likes.css,/i/noticons/noticons.css?m=1436783281j&cssminify=yes
22705
https://travel.blog/
13048
https://s0.wp.com/_static/??-eJxti8sKgCAQAH8oW6KHdoi+xcTUWF1pjX4/OnSIOg0DM3BmYSgVmwrEQ2Q8XEgMmbiIFXXYgb3eQ3IPa8Ncwf/FZIJGgeToLZ+peBstg+/AIS0a72COU9OPUg69atV2AWWKN+I=?cssminify=yes
11680
https://s2.wp.com/_static/??-eJx9i9EKwjAMAH/IGousb+K3bCV2kbQpTerY3zvxxSHs7Q7uYKkuSjEsBjZjRoXaJ5D2IgW1lfEcVU9wlFGJ39QtNUr+G3J3lXuiopBQHEscjaTsxD14pHa0NpxY0oYJtupHP9M93/xwvYTBh+Cfb7HhTvU=?cssminify=yes
10282
https://s1.wp.com/_static/??-eJydkOEKwjAMhF/ILg7dYD/EZ2m7UDubrjQto29vNxGGoIh/Apfcd5CDJQg9+4Q+AWURXDbWMyxBzySYrMPyphrNfIAd9mJMrlJhNPUSEYbm3LSgsnUjKDfru3BWRRkLcCoOf4jZKIYJU5ArLsuckzDRjv9GRJmsN/wB3/2/flD3FGRaHYSjleiQqu0b9ixKqRCRWdRJNpNItwpuvV3p0vbHru9OQ99NDzZijrI=?cssminify=yes
9616
https://s2.wp.com/i/logo/wpcom-gray-white.png
8544
Avoids an excessive DOM size — 106 elements
A large DOM (Document Object Model) will increase memory usage, cause longer system calculations as well as costly layout reflows.
Statistic Element Value
Total DOM Elements
106
Maximum DOM Depth
SHOW DETAILS
15
Maximum Child Elements
SHOW DETAILS
24
Avoid chaining critical requests — 12 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Travel.blog should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
JavaScript execution time — 0.0 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://travel.blog/
103.324
36.663
2.993
Unattributable
70.086
1.159
0.217
Minimizes main-thread work — 0.3 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Script Evaluation
87.406
Rendering
70.395
Other
38.535
Style & Layout
29.473
Parse HTML & CSS
18.13
Script Parsing & Compilation
13.58
Keep request counts low and transfer sizes small — 28 requests • 672 KiB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.
Resource Type Requests Transfer Size (Bytes)
Total
28
688035
Image
6
489479
Script
8
91876
Stylesheet
10
65917
Font
1
26935
Document
2
13575
Other
1
253
Media
0
0
Third-party
26
674734
Minimize third-party usage — Third-party code blocked the main thread for 0 ms
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Third-Party Transfer Size (Bytes) Main-Thread Blocking Time (Ms)
SHOW DETAILS
629115
0
SHOW DETAILS
28280
0
SHOW DETAILS
10754
0
SHOW DETAILS
5662
0
SHOW DETAILS
923
0
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
img
Avoid large layout shifts — 3 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
Start your Travel.blog
0.10927239296034
Blog at WordPress.com.
0.03890097189388
Artwork by Tony Ruth Site by Automattic Design
0.021013921723142
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Avoids large JavaScript libraries with smaller alternatives — 0 large libraries found
It is recommended to work with smaller JavaScript libraries to reduce your bundle size and avoid poor performance.

Budgets

Performance budget
It is advised to keep the quantity and size of all network requests under the targets set by the provided performance budget.
Timing budget
It is advised to set a timing budget to monitor the performance of your site.

Metrics

Largest Contentful Paint — 1.4 s
The timing of the largest text or image that is painted.
Cumulative Layout Shift — 0.169
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Opportunities

Eliminate render-blocking resources — Potential savings of 200 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Travel.blog should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
https://s1.wp.com/_static/??-eJydkOEKwjAMhF/ILg7dYD/EZ2m7UDubrjQto29vNxGGoIh/Apfcd5CDJQg9+4Q+AWURXDbWMyxBzySYrMPyphrNfIAd9mJMrlJhNPUSEYbm3LSgsnUjKDfru3BWRRkLcCoOf4jZKIYJU5ArLsuckzDRjv9GRJmsN/wB3/2/flD3FGRaHYSjleiQqu0b9ixKqRCRWdRJNpNItwpuvV3p0vbHru9OQ99NDzZijrI=?cssminify=yes
9616
310
https://s1.wp.com/_static/??/wp-content/mu-plugins/comment-likes/css/comment-likes.css,/i/noticons/noticons.css?m=1436783281j&cssminify=yes
22705
350
https://fonts.googleapis.com/css?family=Karla%3A400%2C700%2C400italic%2C700italic&subset=latin%2Clatin-ext
1345
230
https://s2.wp.com/_static/??-eJx9i9EKwjAMAH/IGousb+K3bCV2kbQpTerY3zvxxSHs7Q7uYKkuSjEsBjZjRoXaJ5D2IgW1lfEcVU9wlFGJ39QtNUr+G3J3lXuiopBQHEscjaTsxD14pHa0NpxY0oYJtupHP9M93/xwvYTBh+Cfb7HhTvU=?cssminify=yes
10282
310
https://s0.wp.com/_static/??-eJxti8sKgCAQAH8oW6KHdoi+xcTUWF1pjX4/OnSIOg0DM3BmYSgVmwrEQ2Q8XEgMmbiIFXXYgb3eQ3IPa8Ncwf/FZIJGgeToLZ+peBstg+/AIS0a72COU9OPUg69atV2AWWKN+I=?cssminify=yes
11680
310
https://s2.wp.com/_static/??/wp-includes/js/jquery/jquery.js,/wp-content/js/postmessage.js,/wp-content/js/mobile-useragent-info.js?m=1558356653j
43192
430
https://s1.wp.com/?custom-css=1&csblog=83xvQ&cscache=6&csrev=4
1955
230
Properly size images — Potential savings of 410 KiB
Images can slow down the page's load time. Travel.blog should consider serving more appropriate-sized images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://a8ctraveldotblog.files.wordpress.com/2017/12/travel_1600_90.jpg?w=924&h=1&crop=1
479604
412160
https://s2.wp.com/i/logo/wpcom-gray-white.png
8203
8121

Diagnostics

Serve static assets with an efficient cache policy — 4 resources found
Travel.blog can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Transfer Size (Bytes)
https://0.gravatar.com/js/gprofiles.js?ver=202050y
604800000
7732
https://0.gravatar.com/dist/css/hovercard.min.css?ver=202050y
604800000
2175
https://0.gravatar.com/dist/css/services.min.css?ver=202050y
604800000
847
https://a8ctraveldotblog.files.wordpress.com/2017/12/travel_1600_90.jpg?w=924&h=1&crop=1
918301000
480075

Diagnostics

Ensure text remains visible during webfont load
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
URL Potential Savings (Ms)
https://fonts.gstatic.com/s/karla/v14/qkBbXvYC6trAT7RVLtyU5rZP.woff2
2.6630000211298
100

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of travel.blog. This includes details about various page attributes that can be optimized.

Navigation

`[accesskey]` values are unique
Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.
The page contains a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.
`[id]` attributes on active, focusable elements are unique
Ensure all focusable elements have a unique id value to allow them to be visible to users of assistive technologies, like a screen reader.
Heading elements appear in a sequentially-descending order
Properly order all headers and do not skip heading levels to better the navigation and readability for users of assistive technologies, like a screen reader.
No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
`[aria-hidden="true"]` is not present on the document `<body>`
If aria-hidden=true is set on the document body, assistive technologies, like a screen reader will work inconsistently.
`[aria-hidden="true"]` elements do not contain focusable descendents
Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.
ARIA input fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when an input field does not have an accessible name specified.
`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.
`[role]`s are contained by their required parent element
Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.
`[role]` values are valid
All ARIA roles require valid values to perform their intended functions.
ARIA toggle fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when a toggle field does not have an accessible name specified.
`[aria-*]` attributes have valid values
ARIA attributes cannot be interpreted with invalid values when used by screen readers and other assistive technologies.
`[aria-*]` attributes are valid and not misspelled
ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.
ARIA IDs are unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.

Names and labels

Buttons have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
`<frame>` or `<iframe>` elements have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Form elements have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
Links have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.
`<object>` elements have `[alt]` text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Contrast

Background and foreground colors have a sufficient contrast ratio
Many (if not most) users find low-contrast text difficult or impossible to read.

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Screen readers and other assistive technologies may produce poor and inaccurate output when definition lists are not properly marked up.
Definition list items are wrapped in `<dl>` elements
In order for screen readers and other assistive technologies to properly announce definition list items ('<dt>' and '<dd>'), they must be wrapped in parent a '<dl>' element.
Presentational `<table>` elements avoid using `<th>`, `<caption>` or the `[summary]` attribute.
It is advised to not include data elements in tables which are used for layout purposes, as it may create confusion for screen reader and other assistive technology users.
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Use proper list structure to aid screen readers and other assistive technologies.
List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
In order for screen readers to announce list items, ensure that list items ('<li>') are contained within parent '<ul>' or '<ol>' tags.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that '<td>' cells using the headers attribute only refer to other cells in the same table, to improve screen reader user experience.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that table headers refer to some set of cells, to improve screen reader user experience.

Internationalization and localization

`<html>` element has a `[lang]` attribute
It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.
`<html>` element has a valid value for its `[lang]` attribute
Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.
`[lang]` attributes have a valid value
Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.

Best practices

The document does not use `<meta http-equiv="refresh">`
Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.

Audio and video

`<video>` elements contain a `<track>` element with `[kind="captions"]`
Travel.blog may provide assistance to deaf or hearing-impaired users with captions on videos.
`<video>` elements contain a `<track>` element with `[kind="description"]`
Travel.blog may provide relevant information that dialogue cannot, by using audio descriptions.

Manual Checks

The page has a logical tab order
The visual layout should be logical in its tab order and users cannot focus elements that are offscreen.
Interactive controls are keyboard focusable
Ensure that custom interactive controls are keyboard focusable and that a focus indicator is displayed.
Interactive elements indicate their purpose and state
Ensure that interactive elements (such as links and buttons) are distinguishable from non-interactive elements and that they indicate their state.
The user's focus is directed to new content added to the page
When new content (such as a dialogue) is added to the page, the user's focus should be directed to it.
User focus is not accidentally trapped in a region
Avoid focus being accidentally trapped when a user tabs in and out of controls or regions on page.
Custom controls have associated labels
Ensure that custom interactive controls have associated labels, which are provided by aria-label and aria-labelledby attributes.
Custom controls have ARIA roles
Ensure that all custom interactive controls have appropriate ARIA roles.
Visual order on the page follows DOM order
Ensure that the DOM order matches with the page's visual order, in order to improve navigation for screen readers and other assistive technologies.
Offscreen content is hidden from assistive technology
Ensure that offscreen content is hidden through the use of "display:none" styling or the aria-hidden attribute.
HTML5 landmark elements are used to improve navigation
Elements such as <main> and <nav> are recommended as they are used by screen readers and other assistive technologies to improve keyboard navigation.
79

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that travel.blog should incorporate. This includes practices such as protecting pages with HTTPS.

Audits

Links to cross-origin destinations are safe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.
Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.

Audits

Allows users to paste into password fields
Ensure that password inputs may be pasted into to aid in the user's ability to use password managers and improve security.
Displays images with correct aspect ratio
Ensure that image display dimensions match their natural aspect ratio.
Serves images with appropriate resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.
Fonts with `font-display: optional` are preloaded
It is recommended that optional fonts are preloaded.

Audits

Page has the HTML doctype
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
Properly defines charset
It is advised to declare a character encoding, optionally via a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header.

Audits

Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.
Avoids Application Cache
Application cache is deprecated and is no longer recommended.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
jQuery
1.12.4
WordPress
WordPress.com
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.

Audits

Does not use HTTPS — 1 insecure request found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL
http://travel.blog/
Includes front-end JavaScript libraries with known security vulnerabilities — 4 vulnerabilities detected
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Library Version Vulnerability Count Highest Severity
SHOW DETAILS
4
Medium

Audits

Browser errors were logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
URL Description
https://r-login.wordpress.com/remote-login.php?wpcom_remote_login=key&origin=aHR0cHM6Ly90cmF2ZWwuYmxvZw%3D%3D&wpcomid=119054498&time=1607318368
Failed to execute 'postMessage' on 'DOMWindow': The target origin provided ('https://r-login.wordpress.com') does not match the recipient window's origin ('https://travel.blog').
100

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for travel.blog. This includes optimizations such as providing meta data.

Mobile Friendly

Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of travel.blog on mobile screens.
Document uses legible font sizes
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.
Tap targets are sized appropriately
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.

Content Best Practices

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
Document has a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.
Links have descriptive text
Make use of descriptive link text to assist search engines in understanding the content.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Document has a valid `hreflang`
Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.
Document has a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.
Document avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
Links are crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.
Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.
robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Manual Checks

Structured data is valid
Structured data can be validated through the use of the Structured Data Testing Tool and the Structured Data Linter.
48

Progressive Web App

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of travel.blog. This includes details about web app manifests.

Fast and reliable

Page load is fast enough on mobile networks
Ensure that the page loads fast enough over a cellular network, to ensure good mobile user experience.

PWA Optimized

Redirects HTTP traffic to HTTPS
It is advised to redirect all HTTP traffic to HTTPS, in order to enable secure web features for all users.
Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of travel.blog on mobile screens.
Contains some content when JavaScript is not available
Apps should display alternative content for when JavaScript is disabled.
Provides a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.

Fast and reliable

Current page does not respond with a 200 when offline
In order for Progressive Web Apps to be made available offline, ensure that the app is using a service worker.
`start_url` does not respond with a 200 when offline
Consider using a service worker for Progressive Web Apps to ensure greater reliability for the user, in the case of poor network conditions.

Installable

Does not use HTTPS — 1 insecure request found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL
http://travel.blog/
Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Web app manifest does not meet the installability requirements
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
View Data

PWA Optimized

Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Does not set a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Manifest doesn't have a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

Manual Checks

Site works cross-browser
Ensure that the Progressive Web App works correctly across every major browser.
Page transitions don't feel like they block on the network
Users perceive apps with responsive, snappy transitions as higher peforming and ensures a great user experience, even on a slow network.
Each page has a URL
Ensure that all pages are deep linkable via URL. They should also be unique for the purpose of shareability on social media.
Avg. (All Categories) 81
Performance 70
Accessibility 100
Best Practices 86
SEO 100
Progressive Web App 50
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
Simulate loading on mobile
70

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for travel.blog. This includes details about optimizing page load times which can result in a better user experience.

Metrics

Speed Index — 3.1 s
The time taken for the page contents to be visibly populated.
Time to Interactive — 3.6 s
The time taken for the page to become fully interactive.
Total Blocking Time — 20 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).

Other

First CPU Idle — 3.3 s
The time taken for the page's main thread to be quiet enough to handle input.
Max Potential First Input Delay — 80 ms
Users could experience a delay when interacting with the page.
Estimated Input Latency — 10 ms
The time taken for the page to respond to user input (during the busiest 5 second window of page load). Users are likely to perceive travel.blog as laggy when the latency is higher than 0.05 seconds.
Network Requests
Below is a list of network requests that were made during page load.
URL Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://travel.blog/
0
15.160000009928
242
0
301
text/html
https://travel.blog/
15.561000036541
118.21200000122
12571
41517
200
text/html
Document
https://s1.wp.com/_static/??-eJydkOEKwjAMhF/ILg7dYD/EZ2m7UDubrjQto29vNxGGoIh/Apfcd5CDJQg9+4Q+AWURXDbWMyxBzySYrMPyphrNfIAd9mJMrlJhNPUSEYbm3LSgsnUjKDfru3BWRRkLcCoOf4jZKIYJU5ArLsuckzDRjv9GRJmsN/wB3/2/flD3FGRaHYSjleiQqu0b9ixKqRCRWdRJNpNItwpuvV3p0vbHru9OQ99NDzZijrI=?cssminify=yes
130.83600002574
149.61000002222
9616
60500
200
text/css
Stylesheet
https://s1.wp.com/_static/??/wp-content/mu-plugins/comment-likes/css/comment-likes.css,/i/noticons/noticons.css?m=1436783281j&cssminify=yes
130.96500001848
152.66100002918
22705
37496
200
text/css
Stylesheet
https://fonts.googleapis.com/css?family=Karla%3A400%2C700%2C400italic%2C700italic&subset=latin%2Clatin-ext
131.09700003406
145.61599999433
1408
2736
200
text/css
Stylesheet
https://s2.wp.com/_static/??-eJx9i9EKwjAMAH/IGousb+K3bCV2kbQpTerY3zvxxSHs7Q7uYKkuSjEsBjZjRoXaJ5D2IgW1lfEcVU9wlFGJ39QtNUr+G3J3lXuiopBQHEscjaTsxD14pHa0NpxY0oYJtupHP9M93/xwvYTBh+Cfb7HhTvU=?cssminify=yes
131.34200003697
153.15200004261
10282
52883
200
text/css
Stylesheet
https://s0.wp.com/_static/??-eJxti8sKgCAQAH8oW6KHdoi+xcTUWF1pjX4/OnSIOg0DM3BmYSgVmwrEQ2Q8XEgMmbiIFXXYgb3eQ3IPa8Ncwf/FZIJGgeToLZ+peBstg+/AIS0a72COU9OPUg69atV2AWWKN+I=?cssminify=yes
131.53600000078
156.25800000271
11680
29360
200
text/css
Stylesheet
https://s2.wp.com/_static/??/wp-includes/js/jquery/jquery.js,/wp-content/js/postmessage.js,/wp-content/js/mobile-useragent-info.js?m=1558356653j
131.82000000961
171.90200003097
43192
134928
200
application/x-javascript
Script
https://s1.wp.com/?custom-css=1&csblog=83xvQ&cscache=6&csrev=4
132.04100000439
146.75700000953
1955
5159
200
text/css
Stylesheet
https://s1.wp.com/_static/??-eJyVzlEKwjAMBuALWaMwpz6IZ+m6dsu6pqVpN49vFYTpRPApIfk/EpiDUJ6SpgQDQ6snVDrctgNvYLFyWYQxd0gMyjtXRmJEq/lhRmyAZwz6H/Q2+ISp167EQm7AxwmfgC2GkiYrjFeZhcHVk9+YyaQSelrdWDwnW4ckGhnBSU46lk6kKJX9hYLnJMwoMQL3MiJ1r1rQ1V329a6ujqdzdRjuWPyEaw==
132.219000021
149.05800000997
24447
90053
200
application/javascript
Script
https://stats.wp.com/w.js?61
185.3500000434
202.97899999423
4802
13423
200
application/javascript
Script
https://s1.wp.com/wp-includes/js/wp-emoji-release.min.js?m=1605528427h&ver=5.6-RC2-49736
190.59400004335
205.13400004711
5078
14246
200
application/javascript
Script
https://s2.wp.com/wp-content/mu-plugins/global-print/global-print.css?m=1465851035h&cssminify=yes
209.45800002664
225.32800002955
2293
5605
200
text/css
Stylesheet
https://a8ctraveldotblog.files.wordpress.com/2017/12/travel_1600_90.jpg?w=924&h=1&crop=1
229.51900004409
330.19800001057
480075
479604
200
image/webp
Image
https://pixel.wp.com/g.gif?v=wpcom-no-pv&x_mobile_platforms=android&x_mobile_devices=android&baba=0.7213827274462459
245.45000004582
259.63700003922
215
50
200
image/gif
Image
https://fonts.gstatic.com/s/karla/v14/qkBbXvYC6trAT7RVLtyU5rZP.woff2
246.91500002518
253.16399999429
26937
26368
200
font/woff2
Font
https://graph.facebook.com/?callback=WPCOMSharing.update_facebook_count&ids=https%3A%2F%2Ftravel.blog%2F
257.77100003324
379.93500003358
920
244
200
text/javascript
Script
https://pixel.wp.com/g.gif?v=wpcom-no-pv&x_sharing-count-request=facebook&r=0.03015201946713142
258.80800001323
272.62800000608
215
50
200
image/gif
Image
https://r-login.wordpress.com/remote-login.php?wpcom_remote_login=key&origin=aHR0cHM6Ly90cmF2ZWwuYmxvZw%3D%3D&wpcomid=119054498&time=1607318564
262.22700002836
325.37999999477
524
121
200
text/html
Document
https://pixel.wp.com/g.gif?x_stats-initial-visibility=visible&v=wpcom-no-pv&rand=0.1725162953350401
269.57900001435
285.34400003264
215
50
200
image/gif
Image
https://pixel.wp.com/g.gif?blog=119054498&v=wpcom&tz=0&user_id=0&post=18&subd=a8ctraveldotblog&host=travel.blog&ref=&fcp=238&rand=0.6730310357413252
269.84900003299
284.70900002867
215
50
200
image/gif
Image
https://pixel.wp.com/g.gif?crypt=UE40eW5QN0p8M2Y%2FRE1lSiYrZXhzUkM5fD1uTDNLUGt6QzVbd3FKb3Q4aWxFU0VMK3ppSG1wamM0bi81JStxN2lKP1pvVnxQRHk3W0d3VEh0SklpNENJfHppaiZjVlFtdzJJS0ovSDNELm8yQjlZJUssV0xnJVFXQ1BbWi84eCZlbyt6VmomVjJyNVFYSjByZiV2UTBpSXNjJi0lW0REbHJRTC1BW3k4MGxJUEljUSVKajY%2FJUpkU2Q2JjdBdWhnNFgxeHZlK1NSeiUuZTFZJnZfZGhCZGdjS1J1Y2hsSz1EWlZON05GJktvMVozNFpGNz9wV283LC9xaHVqXzYmYTBHZFJVZy1IWmZJMCVTdlFddiUlZnpScnlsZFIvMVpXVks1JSZDdg%3D%3D&v=wpcom-no-pv&rand=0.6345472494435032
270.37199999904
285.0150000304
215
50
200
image/gif
Image
https://s0.wp.com/wp-content/mu-plugins/actionbar/actionbar.css?v=20201002
382.48800003203
398.19100004388
3019
12042
200
text/css
Stylesheet
https://s0.wp.com/wp-content/mu-plugins/actionbar/actionbar.js?v=20201002
382.80399999348
397.60200004093
5028
15569
200
application/javascript
Script
https://s2.wp.com/i/logo/wpcom-gray-white.png
403.39700004552
418.80700003821
8544
8203
200
image/png
Image
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
145.153
6.978
154.303
44.959
214.559
19.456
234.032
19.538
254.96
30.94
351.689
7.998
379.997
7.55
427.584
14.69
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data

Opportunities

Defer offscreen images — Potential savings of 8 KiB
Time to Interactive can be slowed down by resources on the page. Travel.blog should consider lazy-loading offscreen and hidden images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://s2.wp.com/i/logo/wpcom-gray-white.png
8203
8203
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Travel.blog should consider minifying CSS files.
Minify JavaScript — Potential savings of 16 KiB
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Travel.blog should consider minifying JS files.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://s1.wp.com/_static/??-eJyVzlEKwjAMBuALWaMwpz6IZ+m6dsu6pqVpN49vFYTpRPApIfk/EpiDUJ6SpgQDQ6snVDrctgNvYLFyWYQxd0gMyjtXRmJEq/lhRmyAZwz6H/Q2+ISp167EQm7AxwmfgC2GkiYrjFeZhcHVk9+YyaQSelrdWDwnW4ckGhnBSU46lk6kKJX9hYLnJMwoMQL3MiJ1r1rQ1V329a6ujqdzdRjuWPyEaw==
24447
10207
https://s2.wp.com/_static/??/wp-includes/js/jquery/jquery.js,/wp-content/js/postmessage.js,/wp-content/js/mobile-useragent-info.js?m=1558356653j
43192
6646
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats
Image formats like PNG and JPEG have poor compression when compared to other next-gen formats, such as JPEG 200, JPEG XR and WebP.
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Initial server response time was short — Root document took 100 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
https://travel.blog/
103.648
Avoid multiple page redirects — Potential savings of 630 ms
Redirects can cause additional delays before the page can begin loading. Travel.blog should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://travel.blog/
630
https://travel.blog/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Travel.blog should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers — Potential savings of 15 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
URL Potential Savings (Bytes)
https://stats.wp.com/w.js?61
9281
https://s2.wp.com/_static/??/wp-includes/js/jquery/jquery.js,/wp-content/js/postmessage.js,/wp-content/js/mobile-useragent-info.js?m=1558356653j
6485

Diagnostics

Avoids enormous network payloads — Total size was 661 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://a8ctraveldotblog.files.wordpress.com/2017/12/travel_1600_90.jpg?w=924&h=1&crop=1
480075
https://s2.wp.com/_static/??/wp-includes/js/jquery/jquery.js,/wp-content/js/postmessage.js,/wp-content/js/mobile-useragent-info.js?m=1558356653j
43192
https://fonts.gstatic.com/s/karla/v14/qkBbXvYC6trAT7RVLtyU5rZP.woff2
26937
https://s1.wp.com/_static/??-eJyVzlEKwjAMBuALWaMwpz6IZ+m6dsu6pqVpN49vFYTpRPApIfk/EpiDUJ6SpgQDQ6snVDrctgNvYLFyWYQxd0gMyjtXRmJEq/lhRmyAZwz6H/Q2+ISp167EQm7AxwmfgC2GkiYrjFeZhcHVk9+YyaQSelrdWDwnW4ckGhnBSU46lk6kKJX9hYLnJMwoMQL3MiJ1r1rQ1V329a6ujqdzdRjuWPyEaw==
24447
https://s1.wp.com/_static/??/wp-content/mu-plugins/comment-likes/css/comment-likes.css,/i/noticons/noticons.css?m=1436783281j&cssminify=yes
22705
https://travel.blog/
12571
https://s0.wp.com/_static/??-eJxti8sKgCAQAH8oW6KHdoi+xcTUWF1pjX4/OnSIOg0DM3BmYSgVmwrEQ2Q8XEgMmbiIFXXYgb3eQ3IPa8Ncwf/FZIJGgeToLZ+peBstg+/AIS0a72COU9OPUg69atV2AWWKN+I=?cssminify=yes
11680
https://s2.wp.com/_static/??-eJx9i9EKwjAMAH/IGousb+K3bCV2kbQpTerY3zvxxSHs7Q7uYKkuSjEsBjZjRoXaJ5D2IgW1lfEcVU9wlFGJ39QtNUr+G3J3lXuiopBQHEscjaTsxD14pHa0NpxY0oYJtupHP9M93/xwvYTBh+Cfb7HhTvU=?cssminify=yes
10282
https://s1.wp.com/_static/??-eJydkOEKwjAMhF/ILg7dYD/EZ2m7UDubrjQto29vNxGGoIh/Apfcd5CDJQg9+4Q+AWURXDbWMyxBzySYrMPyphrNfIAd9mJMrlJhNPUSEYbm3LSgsnUjKDfru3BWRRkLcCoOf4jZKIYJU5ArLsuckzDRjv9GRJmsN/wB3/2/flD3FGRaHYSjleiQqu0b9ixKqRCRWdRJNpNItwpuvV3p0vbHru9OQ99NDzZijrI=?cssminify=yes
9616
https://s2.wp.com/i/logo/wpcom-gray-white.png
8544
Avoids an excessive DOM size — 100 elements
A large DOM (Document Object Model) will increase memory usage, cause longer system calculations as well as costly layout reflows.
Statistic Element Value
Total DOM Elements
100
Maximum DOM Depth
SHOW DETAILS
15
Maximum Child Elements
SHOW DETAILS
18
Avoid chaining critical requests — 9 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Travel.blog should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
JavaScript execution time — 0.4 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://travel.blog/
441.388
195.004
11.004
https://s2.wp.com/_static/??/wp-includes/js/jquery/jquery.js,/wp-content/js/postmessage.js,/wp-content/js/mobile-useragent-info.js?m=1558356653j
119.124
91.828
8.532
Unattributable
89.936
3.352
0.448
https://s1.wp.com/_static/??-eJyVzlEKwjAMBuALWaMwpz6IZ+m6dsu6pqVpN49vFYTpRPApIfk/EpiDUJ6SpgQDQ6snVDrctgNvYLFyWYQxd0gMyjtXRmJEq/lhRmyAZwz6H/Q2+ISp167EQm7AxwmfgC2GkiYrjFeZhcHVk9+YyaQSelrdWDwnW4ckGhnBSU46lk6kKJX9hYLnJMwoMQL3MiJ1r1rQ1V329a6ujqdzdRjuWPyEaw==
58.696
51.176
6.576
Minimizes main-thread work — 0.8 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Script Evaluation
384.78
Other
156.076
Style & Layout
98.004
Rendering
92.572
Parse HTML & CSS
59.476
Script Parsing & Compilation
43.764
Garbage Collection
8.452
Keep request counts low and transfer sizes small — 25 requests • 661 KiB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.
Resource Type Requests Transfer Size (Bytes)
Total
25
676393
Image
7
489694
Script
6
83467
Stylesheet
8
62958
Font
1
26937
Document
2
13095
Other
1
242
Media
0
0
Third-party
23
663580
Minimize third-party usage — Third-party code blocked the main thread for 0 ms
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Third-Party Transfer Size (Bytes) Main-Thread Blocking Time (Ms)
SHOW DETAILS
628438
2.652
SHOW DETAILS
28345
0
SHOW DETAILS
5877
0
SHOW DETAILS
920
0
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
img
Avoid large layout shifts — 3 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
Artwork by Tony Ruth Site by Automattic Design
0.066015625
Start your Travel.blog
0.055453125
Blog at WordPress.com.
0.055453125
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks — 3 long tasks found
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
URL Start Time (Ms) Duration (Ms)
https://travel.blog/
1110
180
https://s2.wp.com/_static/??/wp-includes/js/jquery/jquery.js,/wp-content/js/postmessage.js,/wp-content/js/mobile-useragent-info.js?m=1558356653j
3690
78
https://s1.wp.com/_static/??-eJyVzlEKwjAMBuALWaMwpz6IZ+m6dsu6pqVpN49vFYTpRPApIfk/EpiDUJ6SpgQDQ6snVDrctgNvYLFyWYQxd0gMyjtXRmJEq/lhRmyAZwz6H/Q2+ISp167EQm7AxwmfgC2GkiYrjFeZhcHVk9+YyaQSelrdWDwnW4ckGhnBSU46lk6kKJX9hYLnJMwoMQL3MiJ1r1rQ1V329a6ujqdzdRjuWPyEaw==
3768
62
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Avoids large JavaScript libraries with smaller alternatives — 0 large libraries found
It is recommended to work with smaller JavaScript libraries to reduce your bundle size and avoid poor performance.

Budgets

Performance budget
It is advised to keep the quantity and size of all network requests under the targets set by the provided performance budget.
Timing budget
It is advised to set a timing budget to monitor the performance of your site.

Metrics

First Contentful Paint — 3.1 s
The time taken for the first image or text on the page to be rendered.
Cumulative Layout Shift — 0.177
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

First Meaningful Paint — 3.1 s
The time taken for the primary content of the page to be rendered.
First Contentful Paint (3G) — 5930 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.

Opportunities

Remove unused CSS — Potential savings of 33 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Travel.blog should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://s1.wp.com/_static/??/wp-content/mu-plugins/comment-likes/css/comment-likes.css,/i/noticons/noticons.css?m=1436783281j&cssminify=yes
22705
22643
https://s0.wp.com/_static/??-eJxti8sKgCAQAH8oW6KHdoi+xcTUWF1pjX4/OnSIOg0DM3BmYSgVmwrEQ2Q8XEgMmbiIFXXYgb3eQ3IPa8Ncwf/FZIJGgeToLZ+peBstg+/AIS0a72COU9OPUg69atV2AWWKN+I=?cssminify=yes
11680
11619
Remove unused JavaScript — Potential savings of 22 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://s2.wp.com/_static/??/wp-includes/js/jquery/jquery.js,/wp-content/js/postmessage.js,/wp-content/js/mobile-useragent-info.js?m=1558356653j
43192
22329

Diagnostics

Serve static assets with an efficient cache policy — 1 resource found
Travel.blog can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Transfer Size (Bytes)
https://a8ctraveldotblog.files.wordpress.com/2017/12/travel_1600_90.jpg?w=924&h=1&crop=1
918293000
480075

Metrics

Largest Contentful Paint — 6.0 s
The timing of the largest text or image that is painted.

Opportunities

Eliminate render-blocking resources — Potential savings of 1,040 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Travel.blog should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
https://s1.wp.com/_static/??-eJydkOEKwjAMhF/ILg7dYD/EZ2m7UDubrjQto29vNxGGoIh/Apfcd5CDJQg9+4Q+AWURXDbWMyxBzySYrMPyphrNfIAd9mJMrlJhNPUSEYbm3LSgsnUjKDfru3BWRRkLcCoOf4jZKIYJU5ArLsuckzDRjv9GRJmsN/wB3/2/flD3FGRaHYSjleiQqu0b9ixKqRCRWdRJNpNItwpuvV3p0vbHru9OQ99NDzZijrI=?cssminify=yes
9616
1080
https://s1.wp.com/_static/??/wp-content/mu-plugins/comment-likes/css/comment-likes.css,/i/noticons/noticons.css?m=1436783281j&cssminify=yes
22705
1530
https://fonts.googleapis.com/css?family=Karla%3A400%2C700%2C400italic%2C700italic&subset=latin%2Clatin-ext
1408
780
https://s2.wp.com/_static/??-eJx9i9EKwjAMAH/IGousb+K3bCV2kbQpTerY3zvxxSHs7Q7uYKkuSjEsBjZjRoXaJ5D2IgW1lfEcVU9wlFGJ39QtNUr+G3J3lXuiopBQHEscjaTsxD14pHa0NpxY0oYJtupHP9M93/xwvYTBh+Cfb7HhTvU=?cssminify=yes
10282
1230
https://s0.wp.com/_static/??-eJxti8sKgCAQAH8oW6KHdoi+xcTUWF1pjX4/OnSIOg0DM3BmYSgVmwrEQ2Q8XEgMmbiIFXXYgb3eQ3IPa8Ncwf/FZIJGgeToLZ+peBstg+/AIS0a72COU9OPUg69atV2AWWKN+I=?cssminify=yes
11680
1230
https://s2.wp.com/_static/??/wp-includes/js/jquery/jquery.js,/wp-content/js/postmessage.js,/wp-content/js/mobile-useragent-info.js?m=1558356653j
43192
1830
https://s1.wp.com/?custom-css=1&csblog=83xvQ&cscache=6&csrev=4
1955
780
Properly size images — Potential savings of 353 KiB
Images can slow down the page's load time. Travel.blog should consider serving more appropriate-sized images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://a8ctraveldotblog.files.wordpress.com/2017/12/travel_1600_90.jpg?w=924&h=1&crop=1
479604
353940
https://s2.wp.com/i/logo/wpcom-gray-white.png
8203
7638

Diagnostics

Ensure text remains visible during webfont load
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
URL Potential Savings (Ms)
https://fonts.gstatic.com/s/karla/v14/qkBbXvYC6trAT7RVLtyU5rZP.woff2
6.2489999691024
100

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of travel.blog. This includes details about various page attributes that can be optimized.

Navigation

`[accesskey]` values are unique
Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.
The page contains a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.
`[id]` attributes on active, focusable elements are unique
Ensure all focusable elements have a unique id value to allow them to be visible to users of assistive technologies, like a screen reader.
Heading elements appear in a sequentially-descending order
Properly order all headers and do not skip heading levels to better the navigation and readability for users of assistive technologies, like a screen reader.
No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
`[aria-hidden="true"]` is not present on the document `<body>`
If aria-hidden=true is set on the document body, assistive technologies, like a screen reader will work inconsistently.
`[aria-hidden="true"]` elements do not contain focusable descendents
Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.
ARIA input fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when an input field does not have an accessible name specified.
`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.
`[role]`s are contained by their required parent element
Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.
`[role]` values are valid
All ARIA roles require valid values to perform their intended functions.
ARIA toggle fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when a toggle field does not have an accessible name specified.
`[aria-*]` attributes have valid values
ARIA attributes cannot be interpreted with invalid values when used by screen readers and other assistive technologies.
`[aria-*]` attributes are valid and not misspelled
ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.
ARIA IDs are unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.

Names and labels

Buttons have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
`<frame>` or `<iframe>` elements have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Form elements have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
Links have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.
`<object>` elements have `[alt]` text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Contrast

Background and foreground colors have a sufficient contrast ratio
Many (if not most) users find low-contrast text difficult or impossible to read.

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Screen readers and other assistive technologies may produce poor and inaccurate output when definition lists are not properly marked up.
Definition list items are wrapped in `<dl>` elements
In order for screen readers and other assistive technologies to properly announce definition list items ('<dt>' and '<dd>'), they must be wrapped in parent a '<dl>' element.
Presentational `<table>` elements avoid using `<th>`, `<caption>` or the `[summary]` attribute.
It is advised to not include data elements in tables which are used for layout purposes, as it may create confusion for screen reader and other assistive technology users.
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Use proper list structure to aid screen readers and other assistive technologies.
List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
In order for screen readers to announce list items, ensure that list items ('<li>') are contained within parent '<ul>' or '<ol>' tags.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that '<td>' cells using the headers attribute only refer to other cells in the same table, to improve screen reader user experience.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that table headers refer to some set of cells, to improve screen reader user experience.

Internationalization and localization

`<html>` element has a `[lang]` attribute
It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.
`<html>` element has a valid value for its `[lang]` attribute
Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.
`[lang]` attributes have a valid value
Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.

Best practices

The document does not use `<meta http-equiv="refresh">`
Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.

Audio and video

`<video>` elements contain a `<track>` element with `[kind="captions"]`
Travel.blog may provide assistance to deaf or hearing-impaired users with captions on videos.
`<video>` elements contain a `<track>` element with `[kind="description"]`
Travel.blog may provide relevant information that dialogue cannot, by using audio descriptions.

Manual Checks

The page has a logical tab order
The visual layout should be logical in its tab order and users cannot focus elements that are offscreen.
Interactive controls are keyboard focusable
Ensure that custom interactive controls are keyboard focusable and that a focus indicator is displayed.
Interactive elements indicate their purpose and state
Ensure that interactive elements (such as links and buttons) are distinguishable from non-interactive elements and that they indicate their state.
The user's focus is directed to new content added to the page
When new content (such as a dialogue) is added to the page, the user's focus should be directed to it.
User focus is not accidentally trapped in a region
Avoid focus being accidentally trapped when a user tabs in and out of controls or regions on page.
Custom controls have associated labels
Ensure that custom interactive controls have associated labels, which are provided by aria-label and aria-labelledby attributes.
Custom controls have ARIA roles
Ensure that all custom interactive controls have appropriate ARIA roles.
Visual order on the page follows DOM order
Ensure that the DOM order matches with the page's visual order, in order to improve navigation for screen readers and other assistive technologies.
Offscreen content is hidden from assistive technology
Ensure that offscreen content is hidden through the use of "display:none" styling or the aria-hidden attribute.
HTML5 landmark elements are used to improve navigation
Elements such as <main> and <nav> are recommended as they are used by screen readers and other assistive technologies to improve keyboard navigation.
86

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that travel.blog should incorporate. This includes practices such as protecting pages with HTTPS.

Audits

Links to cross-origin destinations are safe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.
Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.

Audits

Allows users to paste into password fields
Ensure that password inputs may be pasted into to aid in the user's ability to use password managers and improve security.
Displays images with correct aspect ratio
Ensure that image display dimensions match their natural aspect ratio.
Serves images with appropriate resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.
Fonts with `font-display: optional` are preloaded
It is recommended that optional fonts are preloaded.

Audits

Page has the HTML doctype
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
Properly defines charset
It is advised to declare a character encoding, optionally via a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header.

Audits

Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.
Avoids Application Cache
Application cache is deprecated and is no longer recommended.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
jQuery
1.12.4
WordPress
WordPress.com
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.

Audits

Does not use HTTPS — 1 insecure request found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL
http://travel.blog/
Includes front-end JavaScript libraries with known security vulnerabilities — 4 vulnerabilities detected
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Library Version Vulnerability Count Highest Severity
SHOW DETAILS
4
Medium
100

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for travel.blog. This includes optimizations such as providing meta data.

Mobile Friendly

Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of travel.blog on mobile screens.
Document uses legible font sizes — 100% legible text
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.
Source Selector % of Page Text Font Size
SHOW DETAILS
100.00%
≥ 12px
Tap targets are sized appropriately — 100% appropriately sized tap targets
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.

Content Best Practices

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
Document has a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.
Links have descriptive text
Make use of descriptive link text to assist search engines in understanding the content.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Document has a valid `hreflang`
Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.
Document has a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.
Document avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
Links are crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.
Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.
robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Manual Checks

Structured data is valid
Structured data can be validated through the use of the Structured Data Testing Tool and the Structured Data Linter.
50

Progressive Web App

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of travel.blog. This includes details about web app manifests.

Fast and reliable

Page load is fast enough on mobile networks
Ensure that the page loads fast enough over a cellular network, to ensure good mobile user experience.

PWA Optimized

Redirects HTTP traffic to HTTPS
It is advised to redirect all HTTP traffic to HTTPS, in order to enable secure web features for all users.
Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of travel.blog on mobile screens.
Contains some content when JavaScript is not available
Apps should display alternative content for when JavaScript is disabled.
Provides a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.

Fast and reliable

Current page does not respond with a 200 when offline
In order for Progressive Web Apps to be made available offline, ensure that the app is using a service worker.
`start_url` does not respond with a 200 when offline
Consider using a service worker for Progressive Web Apps to ensure greater reliability for the user, in the case of poor network conditions.

Installable

Does not use HTTPS — 1 insecure request found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL
http://travel.blog/
Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Web app manifest does not meet the installability requirements
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
View Data

PWA Optimized

Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Does not set a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Manifest doesn't have a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

Manual Checks

Site works cross-browser
Ensure that the Progressive Web App works correctly across every major browser.
Page transitions don't feel like they block on the network
Users perceive apps with responsive, snappy transitions as higher peforming and ensures a great user experience, even on a slow network.
Each page has a URL
Ensure that all pages are deep linkable via URL. They should also be unique for the purpose of shareability on social media.
Hosting

Server Location

Server IP Address: 192.0.78.31
Continent: North America
Country: United States
United States Flag
Region:
City:
Longitude: -97.822
Latitude: 37.751
Currencies: USD
USN
USS
Languages: English

Web Hosting Provider

Name IP Address
Automattic, Inc
Registration

Domain Registrant

Private Registration: No
Name:
Organization:
Country:
City:
State:
Post Code:
Email:
Phone:
Note: Registration information is derived from various sources and may be inaccurate.

Domain Registrar

Security

Visitor Safety

Mature Content: Not Likely
McAfee WebAdvisor Rating: Safe
WOT Rating: 0.1/5 (0 reviews)
WOT Trustworthiness: 2/100
WOT Child Safety: 1/100
Note: Safety information is not guaranteed.

SSL/TLS Certificate

Issued To: *.travel.blog
Issued By: Sectigo RSA Domain Validation Secure Server CA
Valid From: 28th February, 2020
Valid To: 28th February, 2022
Subject: CN = *.travel.blog
Hash: 0e34d492
Issuer: CN = Sectigo RSA Domain Validation Secure Server CA
O = Sectigo Limited
S = GB
Version: 2
Serial Number: 0x97D8672EF2168A655DBA79A50D4E3BC4
Serial Number (Hex): 97D8672EF2168A655DBA79A50D4E3BC4
Valid From: 28th February, 2024
Valid To: 28th February, 2024
Signature Algorithm (Short Name): RSA-SHA256
Signature Algorithm (Long Name): sha256WithRSAEncryption
Authority Key Identifier: keyid:8D:8C:5E:C4:54:AD:8A:E1:77:E9:9B:F9:9B:05:E1:B8:01:8D:61:E1
Extended Key Usage: TLS Web Server Authentication, TLS Web Client Authentication
Certificate Policies: Policy: 1.3.6.1.4.1.6449.1.2.2.7
CPS: https://sectigo.com/CPS
Policy: 2.23.140.1.2.1
Authority Information Access: CA Issuers - URI:http://crt.sectigo.com/SectigoRSADomainValidationSecureServerCA.crt
OCSP - URI:http://ocsp.sectigo.com
SCT List: Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 46:A5:55:EB:75:FA:91:20:30:B5:A2:89:69:F4:F3:7D:
11:2C:41:74:BE:FD:49:B8:85:AB:F2:FC:70:FE:6D:47
Timestamp : Feb 28 06:05:59.533 2020 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:46:02:21:00:FB:EA:9E:94:B1:9F:B3:FD:DF:0C:65:
F9:4D:16:33:D1:80:A5:D3:42:E3:27:32:F0:43:1D:C5:
EF:AD:16:71:E9:02:21:00:C6:AC:4B:6C:BC:5A:AE:82:
F4:FC:AC:74:70:52:EA:AF:5D:D0:2C:30:D7:D0:1A:82:
5E:4F:30:33:5A:BE:F5:76
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : DF:A5:5E:AB:68:82:4F:1F:6C:AD:EE:B8:5F:4E:3E:5A:
EA:CD:A2:12:A4:6A:5E:8E:3B:12:C0:20:44:5C:2A:73
Timestamp : Feb 28 06:05:59.481 2020 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:21:00:F8:51:77:53:52:73:C6:2F:3A:65:73:
C6:AB:AE:A8:D0:B9:19:88:1C:DB:4D:59:94:3A:21:CB:
F1:CB:26:66:CE:02:20:5D:BD:C1:4E:C9:0C:40:07:AA:
19:1D:BA:BC:4B:69:8B:33:12:3D:7C:A8:EC:6A:C6:33:
32:CD:38:27:0D:0B:57
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 41:C8:CA:B1:DF:22:46:4A:10:C6:A1:3A:09:42:87:5E:
4E:31:8B:1B:03:EB:EB:4B:C7:68:F0:90:62:96:06:F6
Timestamp : Feb 28 06:05:59.534 2020 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:20:7C:48:BF:32:A5:D3:D6:16:D3:3B:AE:29:
A5:77:AA:0B:A4:6F:ED:20:C2:5E:E3:F4:D4:95:50:6A:
05:B4:D7:AF:02:21:00:F4:0B:18:9C:26:76:DB:B1:B9:
12:D4:B0:64:48:B2:67:FF:0A:71:25:17:7B:CD:A3:35:
7B:5A:E8:D8:B6:1E:A1
Key Usage: Digital Signature, Key Encipherment
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:travel.blog
DNS:*.travel.blog
Technical

DNS Lookup

A Records

Host IP Address Class TTL
travel.blog. 192.0.78.31 IN 599
travel.blog. 192.0.78.30 IN 599

NS Records

Host Nameserver Class TTL
travel.blog. ns1.automattic.com. IN 21599
travel.blog. ns2.automattic.com. IN 21599
travel.blog. ns3.automattic.com. IN 21599
travel.blog. ns4.automattic.com. IN 21599

SOA Records

Domain Name Primary NS Responsible Email TTL
travel.blog. ns1.automattic.com. hostmaster.automattic.com. 21599

TXT Records

Host Value Class TTL
travel.blog. v=spf1 IN 14399

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Server: nginx
Date: 7th December, 2020
Content-Type: text/html; charset=UTF-8
Connection: keep-alive
Vary: Cookie
X-hacker: If you're reading this, you should visit automattic.com/jobs and apply to join the fun, mention this header.
X-Frame-Options: SAMEORIGIN
Link: <https://wp.me/P83xvQ-i>; rel=shortlink
X-ac: 3.ewr _dca
Strict-Transport-Security: max-age=15552000

Whois Lookup

Created:
Changed:
Expires:
Status:
Nameservers:
Full Whois: travel.blog domain is not supported
View Raw Whois

Nameservers

Related

Subdomains

Domain Subdomain
affinitytravels.travel.blog
affinitytravels

Similar Sites

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Domain Valuation Snoop Score
travel.com
$3,740 USD 2/5
travel.de
0/5
travel.info
0/5
travel.net
$10 USD
travel.org
$911 USD 1/5

Sites hosted on the same IP address

Domain Valuation Snoop Score
business.blog
$15,306 USD 3/5
code.blog
$3,848 USD 2/5
game.blog
$4,398 USD 2/5
home.blog
$2,887,208 USD 4/5
Love W3 Snoop?
Update Now

Recently Updated

mathsspot.com
mope.io
readmng.com
jumia.com
jumia.com.ng
vimeocdn.com
mail2phone.com
matanga.cc
heraldscotland.com
riyadonline.com

Recently Viewed

wstter.com
filehold.com
vbaf.com
unfiltered.in
khu3s.net
toko.ly
wwbinhinsi.com
wwbinhindi.com
xtcrr.com
casaclip.com