theinsatiabletraveler.com

theinsatiabletraveler.com is SSL secured

Free website and domain report on theinsatiabletraveler.com

Last Updated: 25th August, 2022 Update Now
Overview

Snoop Summary for theinsatiabletraveler.com

This is a free and comprehensive report about theinsatiabletraveler.com. The domain theinsatiabletraveler.com is currently hosted on a server located in United States with the IP address 104.18.41.185, where USD is the local currency and the local language is English. Our records indicate that theinsatiabletraveler.com is privately registered by Domains By Proxy, LLC. Theinsatiabletraveler.com has the potential to be earning an estimated $1 USD per day from advertising revenue. If theinsatiabletraveler.com was to be sold it would possibly be worth $749 USD (based on the daily revenue potential of the website over a 24 month period). Theinsatiabletraveler.com receives an estimated 355 unique visitors every day - a decent amount of traffic! This report was last updated 25th August, 2022.

About theinsatiabletraveler.com

Site Preview: theinsatiabletraveler.com theinsatiabletraveler.com
Title: Home –
Description: Educating readers about travel with great photography, inspiring articles about amazing adventures, plus travel and photography advice!
Keywords and Tags: sports
Related Terms:
Fav Icon:
Age: Over 10 years old
Domain Created: 31st July, 2013
Domain Updated: 1st July, 2022
Domain Expires: 31st July, 2024
Review

Snoop Score

2/5

Valuation

$749 USD
Note: All valuation figures are estimates.

Popularity

Low
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 3,653,391
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: 355
Monthly Visitors: 10,805
Yearly Visitors: 129,575
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $1 USD
Monthly Revenue: $31 USD
Yearly Revenue: $369 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: theinsatiabletraveler.com 25
Domain Name: theinsatiabletraveler 21
Extension (TLD): com 3
Expiry Check:

Page Speed Analysis

Average Load Time: 4.95 seconds
Load Time Comparison: Faster than 8% of sites

PageSpeed Insights

Avg. (All Categories) 75
Performance 98
Accessibility 78
Best Practices 92
SEO 75
PWA 33
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://theinsatiabletraveler.com
Updated: 25th August, 2022

1.75 seconds
First Contentful Paint (FCP)
76%
15%
9%

0.00 seconds
First Input Delay (FID)
99%
0%
1%

Simulate loading on desktop
98

Performance

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

Metrics

First Contentful Paint — 0.5 s
The time taken for the first image or text on the page to be rendered.
Time to Interactive — 0.6 s
The time taken for the page to become fully interactive.
Speed Index — 0.7 s
The time taken for the page contents to be visibly populated.
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).
Largest Contentful Paint — 1.0 s
The timing of the largest text or image that is painted.
Cumulative Layout Shift — 0
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Audits

Max Potential First Input Delay — 20 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 0.6 s
The time taken for the primary content of the page to be rendered.
Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://theinsatiabletraveler.com/
http/1.1
0
92.440000036731
450
0
301
text/html
https://theinsatiabletraveler.com/
h2
92.738999985158
200.99599997047
40581
255661
200
text/html
Document
https://theinsatiabletraveler.com/wp-content/cache/autoptimize/css/autoptimize_single_c89e84ad12af687b97f85adc6bee8219.css?ver=2.16.1
h2
213.00300001167
293.71600004379
10430
101485
200
text/css
Stylesheet
https://theinsatiabletraveler.com/wp-content/cache/autoptimize/css/autoptimize_single_ed118ba32d919597ca2f2e4525bb9461.css?ver=3.15.5
h2
213.10000005178
300.31500000041
34259
177696
200
text/css
Stylesheet
https://theinsatiabletraveler.com/wp-content/themes/flatsome/style.css?ver=3.15.5
h2
213.32099998835
342.80199999921
1003
628
200
text/css
Stylesheet
https://theinsatiabletraveler.com/wp-content/cache/autoptimize/css/autoptimize_single_ec6a0b120600a6c45807c38a3cb6b535.css?ver=11.2
h2
213.53499998804
259.73900000099
17433
85882
200
text/css
Stylesheet
https://theinsatiabletraveler.com/wp-includes/js/jquery/jquery.min.js?ver=3.6.0
h2
213.89500005171
272.4360000575
32695
89521
200
application/javascript
Script
https://theinsatiabletraveler.com/wp-content/plugins/bigscoots-cache/assets/js/instantpage.min.js
h2
214.26000003703
293.18599996623
2114
3898
200
application/javascript
Script
https://theinsatiabletraveler.com/wp-content/plugins/autoptimize/classes/external/js/lazysizes.min.js?ao_version=3.1.1.1
h2
309.20899997
354.80500000995
4934
9813
200
application/javascript
Script
https://theinsatiabletraveler.com/wp-content/cache/autoptimize/js/autoptimize_single_57c5a1db93edcd93887426aca9beb73c.js?ver=2.16.1
h2
344.01899995282
415.34399997909
9447
30365
200
application/javascript
Script
https://theinsatiabletraveler.com/wp-content/plugins/bigscoots-cache/assets/js/instantpage.min.js?ver=5.1.0.3
h2
355.48200004268
431.23700004071
2127
3898
200
application/javascript
Script
https://theinsatiabletraveler.com/wp-includes/js/dist/vendor/regenerator-runtime.min.js?ver=0.13.9
h2
214.82600003947
294.0139999846
3205
6475
200
application/javascript
Script
https://theinsatiabletraveler.com/wp-includes/js/dist/vendor/wp-polyfill.min.js?ver=3.15.0
h2
215.11700004339
302.30300000403
7959
19142
200
application/javascript
Script
https://stats.wp.com/e-202233.js
h2
356.06200003531
379.73699998111
3322
8970
200
application/javascript
Script
https://theinsatiabletraveler.com/wp-content/cache/autoptimize/js/autoptimize_7b887d747b65d36c9265d1accd166838.js
h2
356.16299998946
432.56600003224
26160
83026
200
application/javascript
Script
https://theinsatiabletraveler.com/wp-content/themes/flatsome/assets/js/chunk.countup.fe2c1016.js
h2
356.32599995006
432.10199999157
2286
0
200
application/javascript
Other
https://theinsatiabletraveler.com/wp-content/themes/flatsome/assets/js/chunk.sticky-sidebar.a58a6557.js
h2
356.44600004889
442.43199995253
4063
0
200
application/javascript
Other
https://theinsatiabletraveler.com/wp-content/themes/flatsome/assets/js/chunk.tooltips.29144c1c.js
h2
356.56099999323
424.766000011
5706
0
200
application/javascript
Other
https://theinsatiabletraveler.com/wp-content/themes/flatsome/assets/js/chunk.vendors-popups.947eca5c.js
h2
356.68199998327
425.62800005544
8070
0
200
application/javascript
Other
https://theinsatiabletraveler.com/wp-content/themes/flatsome/assets/js/chunk.vendors-slider.f0d2cbc9.js
h2
356.81699996348
403.88100000564
14526
0
200
application/javascript
Other
data
357.73899999913
357.81499999575
0
68
200
image/svg+xml
Image
https://theinsatiabletraveler.com/wp-content/themes/flatsome/assets/css/icons/fl-icons.woff2?v=3.15.5
h2
365.74599996675
409.32400000747
7480
6752
200
font/woff2
Font
data
387.41299998946
387.50700000674
0
68
200
image/svg+xml
Image
data
388.34099995438
388.39900004677
0
69
200
image/svg+xml
Image
data
396.8660000246
396.940000006
0
70
200
image/svg+xml
Image
data
398.02299998701
398.09499995317
0
69
200
image/svg+xml
Image
data
399.01699998882
399.08000000287
0
70
200
image/svg+xml
Image
data
399.88499996252
399.93800001685
0
69
200
image/svg+xml
Image
data
400.68099997006
400.74099996127
0
69
200
image/svg+xml
Image
data
401.46700001787
401.51999995578
0
70
200
image/svg+xml
Image
data
402.27900003083
402.3359999992
0
70
200
image/svg+xml
Image
data
403.24999997392
403.31199998036
0
70
200
image/svg+xml
Image
data
404.48799997102
404.57699995022
0
68
200
image/svg+xml
Image
data
405.51900002174
405.58200003579
0
68
200
image/svg+xml
Image
data
406.40800003894
406.45600005519
0
68
200
image/svg+xml
Image
data
407.47099998407
407.52400003839
0
68
200
image/svg+xml
Image
data
408.33600005135
408.38599996641
0
68
200
image/svg+xml
Image
data
409.26900005434
409.32099998463
0
68
200
image/svg+xml
Image
data
410.26399994735
410.30999994837
0
68
200
image/svg+xml
Image
https://theinsatiabletraveler.com/wp-content/uploads/2021/06/Chris-Pic-of-me-1-1.jpg
h2
429.56399999093
551.59799999092
226931
226127
200
image/jpeg
Image
https://theinsatiabletraveler.com/wp-content/uploads/2020/05/The-Insatiable-Traveler-Logo-20170527.jpg
h2
504.37600002624
548.54800004978
7149
6256
200
image/webp
Image
https://pixel.wp.com/g.gif?v=ext&j=1%3A11.2&blog=161129945&post=66920&tz=-4&srv=theinsatiabletraveler.com&host=theinsatiabletraveler.com&ref=&fcp=387&rand=0.8336191057570606
h2
516.71100000385
540.51399999298
218
50
200
image/gif
Image
https://theinsatiabletraveler.com/wp-content/uploads/2021/12/COVER_IMAGE-618x800.jpg
h2
754.13699995261
835.89700004086
99072
98204
200
image/webp
Image
https://theinsatiabletraveler.com/wp-content/uploads/2016/07/Mongolia-9735.jpg
h2
1620.9030000027
1733.0579999834
190765
189902
200
image/webp
Image
https://theinsatiabletraveler.com/wp-content/uploads/2019/04/Selinda-Explorers-Camp-Botswana-Safari-064401-1.jpg
h2
1621.1540000513
1709.9750000052
180169
179272
200
image/webp
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)
206.16
14.674
221.165
6.665
301.786
5.831
345.034
9.663
358.964
16.594
377.449
7.865
390.17
30.874
421.291
61.808
499.344
5.451
506.312
8.504
515.077
43.448
558.911
13.662
576.247
7.547
583.813
17.294
604.223
7.695
619.477
16.091
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Other

Eliminate render-blocking resources
Resources, such as JavaScript and style sheets, can block the first paint of the page. Theinsatiabletraveler.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Theinsatiabletraveler.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Theinsatiabletraveler.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Theinsatiabletraveler.com should consider minifying JS files.
Reduce unused CSS — Potential savings of 55 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Theinsatiabletraveler.com 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://theinsatiabletraveler.com/wp-content/cache/autoptimize/css/autoptimize_single_ed118ba32d919597ca2f2e4525bb9461.css?ver=3.15.5
34259
28635
https://theinsatiabletraveler.com/wp-content/cache/autoptimize/css/autoptimize_single_ec6a0b120600a6c45807c38a3cb6b535.css?ver=11.2
17433
17338
https://theinsatiabletraveler.com/wp-content/cache/autoptimize/css/autoptimize_single_c89e84ad12af687b97f85adc6bee8219.css?ver=2.16.1
10430
10390
Reduce unused JavaScript
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats — Potential savings of 70 KiB
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://theinsatiabletraveler.com/wp-content/uploads/2021/06/Chris-Pic-of-me-1-1.jpg
226127
71402.45
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 110 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://theinsatiabletraveler.com/
109.251
Avoid multiple page redirects — Potential savings of 190 ms
Redirects can cause additional delays before the page can begin loading. Theinsatiabletraveler.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://theinsatiabletraveler.com/
190
https://theinsatiabletraveler.com/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Theinsatiabletraveler.com 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 0 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://theinsatiabletraveler.com/
167
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
URL Potential Savings (Ms)
https://theinsatiabletraveler.com/wp-content/uploads/2021/06/Chris-Pic-of-me-1-1.jpg
0
Avoids enormous network payloads — Total size was 920 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://theinsatiabletraveler.com/wp-content/uploads/2021/06/Chris-Pic-of-me-1-1.jpg
226931
https://theinsatiabletraveler.com/wp-content/uploads/2016/07/Mongolia-9735.jpg
190765
https://theinsatiabletraveler.com/wp-content/uploads/2019/04/Selinda-Explorers-Camp-Botswana-Safari-064401-1.jpg
180169
https://theinsatiabletraveler.com/wp-content/uploads/2021/12/COVER_IMAGE-618x800.jpg
99072
https://theinsatiabletraveler.com/
40581
https://theinsatiabletraveler.com/wp-content/cache/autoptimize/css/autoptimize_single_ed118ba32d919597ca2f2e4525bb9461.css?ver=3.15.5
34259
https://theinsatiabletraveler.com/wp-includes/js/jquery/jquery.min.js?ver=3.6.0
32695
https://theinsatiabletraveler.com/wp-content/cache/autoptimize/js/autoptimize_7b887d747b65d36c9265d1accd166838.js
26160
https://theinsatiabletraveler.com/wp-content/cache/autoptimize/css/autoptimize_single_ec6a0b120600a6c45807c38a3cb6b535.css?ver=11.2
17433
https://theinsatiabletraveler.com/wp-content/themes/flatsome/assets/js/chunk.vendors-slider.f0d2cbc9.js
14526
Uses efficient cache policy on static assets — 0 resources found
Theinsatiabletraveler.com can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
Avoid chaining critical requests — 8 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Theinsatiabletraveler.com 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.1 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://theinsatiabletraveler.com/
192.556
21.889
2.235
https://theinsatiabletraveler.com/wp-includes/js/jquery/jquery.min.js?ver=3.6.0
114
50.684
0.599
Minimizes main-thread work — 0.4 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
127.407
Style & Layout
120.048
Other
108.326
Rendering
50.058
Parse HTML & CSS
28.527
Script Parsing & Compilation
4.657
All text remains visible during webfont loads
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
Keep request counts low and transfer sizes small — 27 requests • 920 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
27
942554
Image
6
704304
Script
9
91963
Stylesheet
4
63125
Document
1
40581
Other
6
35101
Font
1
7480
Media
0
0
Third-party
2
3540
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)
3540
0
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.
Element
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
8.6681782477046E-5
2.5239656497369E-5
6.4336379307019E-6
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.
Image elements have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
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 theinsatiabletraveler.com on mobile screens.
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.

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.

Other

Properly size images — Potential savings of 359 KiB
Images can slow down the page's load time. Theinsatiabletraveler.com should consider serving more appropriate-sized images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://theinsatiabletraveler.com/wp-content/uploads/2016/07/Mongolia-9735.jpg
189902
147833
https://theinsatiabletraveler.com/wp-content/uploads/2019/04/Selinda-Explorers-Camp-Botswana-Safari-064401-1.jpg
179272
139633
https://theinsatiabletraveler.com/wp-content/uploads/2021/12/COVER_IMAGE-618x800.jpg
98204
79732
Avoid an excessive DOM size — 1,213 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
1213
Maximum DOM Depth
20
Maximum Child Elements
32

Other

Does not use passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Source
78

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of theinsatiabletraveler.com. 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.
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.
`button`, `link`, and `menuitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[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.
ARIA `meter` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `progressbar` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[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 `tooltip` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `treeitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[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.
`<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.
`<object>` elements have alternate 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.

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

Audio and video

`<video>` elements contain a `<track>` element with `[kind="captions"]`
Theinsatiabletraveler.com may provide assistance to deaf or hearing-impaired users with captions on videos.

Contrast

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

Navigation

Heading elements are not 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.
Failing Elements

Names and labels

Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements
Links do not 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.

Best practices

`[user-scalable="no"]` is used in the `<meta name="viewport">` element or the `[maximum-scale]` attribute is less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.
Failing Elements

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.
92

Best Practices

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

Audits

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.
Avoids front-end JavaScript libraries with known security vulnerabilities
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.
Ensure CSP is effective against XSS attacks
Significantly reduce the risk of cross-site scripting attacks (XSS) by ensuring you have a strong Content Security Policy (CSP).
Description Directive Severity
No CSP found in enforcement mode
High

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

Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
jQuery
3.6.0
WordPress
6.0.1
core-js
core-js-global@3.19.1
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.
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

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 Request Resolution
http://theinsatiabletraveler.com/
Allowed
75

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for theinsatiabletraveler.com. 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 theinsatiabletraveler.com 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.
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.

Content Best Practices

Links do not have descriptive text — 6 links found
Make use of descriptive link text to assist search engines in understanding the content.
Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements

Crawling and Indexing

robots.txt is not valid — 3 errors found
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.
Line # Content Error
4
Disallow; /wp-admin/
Syntax not understood
5
Disallow; /readme.html
Syntax not understood
6
Disallow; /refer/
Syntax not understood

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.
33

PWA

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

PWA Optimized

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 theinsatiabletraveler.com on mobile screens.
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.

Installable

Web app manifest or service worker do not meet the installability requirements — 1 reason
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
Failure reason
No manifest was fetched

PWA Optimized

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.
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) 74
Performance 81
Accessibility 80
Best Practices 92
SEO 78
PWA 40
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://theinsatiabletraveler.com
Updated: 25th August, 2022

1.73 seconds
First Contentful Paint (FCP)
80%
15%
5%

0.02 seconds
First Input Delay (FID)
95%
2%
3%

Simulate loading on mobile
81

Performance

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

Metrics

Time to Interactive — 3.8 s
The time taken for the page to become fully interactive.
Speed Index — 2.6 s
The time taken for the page contents to be visibly populated.
Total Blocking Time — 30 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).
Cumulative Layout Shift — 0
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Audits

Max Potential First Input Delay — 80 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 2.2 s
The time taken for the primary content of the page to be rendered.
Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://theinsatiabletraveler.com/
http/1.1
0
116.74700002186
472
0
301
text/html
https://theinsatiabletraveler.com/
h2
117.10300017148
307.26300016977
40581
255661
200
text/html
Document
https://theinsatiabletraveler.com/wp-content/cache/autoptimize/css/autoptimize_single_c89e84ad12af687b97f85adc6bee8219.css?ver=2.16.1
h2
319.22399997711
438.41599998996
10443
101485
200
text/css
Stylesheet
https://theinsatiabletraveler.com/wp-content/cache/autoptimize/css/autoptimize_single_ed118ba32d919597ca2f2e4525bb9461.css?ver=3.15.5
h2
319.35500004329
411.34600015357
34259
177696
200
text/css
Stylesheet
https://theinsatiabletraveler.com/wp-content/themes/flatsome/style.css?ver=3.15.5
h2
319.52700018883
428.99899999611
1005
628
200
text/css
Stylesheet
https://theinsatiabletraveler.com/wp-content/cache/autoptimize/css/autoptimize_single_ec6a0b120600a6c45807c38a3cb6b535.css?ver=11.2
h2
320.2520001214
444.06900019385
17434
85882
200
text/css
Stylesheet
https://theinsatiabletraveler.com/wp-includes/js/jquery/jquery.min.js?ver=3.6.0
h2
320.41300018318
407.11600007489
32696
89521
200
application/javascript
Script
https://theinsatiabletraveler.com/wp-content/plugins/bigscoots-cache/assets/js/instantpage.min.js
h2
320.56999998167
405.11799999513
2126
3898
200
application/javascript
Script
https://theinsatiabletraveler.com/wp-content/plugins/autoptimize/classes/external/js/lazysizes.min.js?ao_version=3.1.1.1
h2
439.96300012805
482.25800017826
4935
9813
200
application/javascript
Script
https://theinsatiabletraveler.com/wp-content/cache/autoptimize/js/autoptimize_single_57c5a1db93edcd93887426aca9beb73c.js?ver=2.16.1
h2
445.03900012933
524.65900010429
9447
30365
200
application/javascript
Script
https://theinsatiabletraveler.com/wp-content/plugins/bigscoots-cache/assets/js/instantpage.min.js?ver=5.1.0.3
h2
459.20500019565
515.11700008996
2127
3898
200
application/javascript
Script
https://theinsatiabletraveler.com/wp-includes/js/dist/vendor/regenerator-runtime.min.js?ver=0.13.9
h2
321.00100000389
398.4590000473
3218
6475
200
application/javascript
Script
https://theinsatiabletraveler.com/wp-includes/js/dist/vendor/wp-polyfill.min.js?ver=3.15.0
h2
321.24499999918
413.40000019409
7962
19142
200
application/javascript
Script
https://stats.wp.com/e-202233.js
h2
459.74100008607
476.83400008827
3322
8970
200
application/javascript
Script
https://theinsatiabletraveler.com/wp-content/cache/autoptimize/js/autoptimize_7b887d747b65d36c9265d1accd166838.js
h2
459.89400008693
525.9420000948
26173
83026
200
application/javascript
Script
https://theinsatiabletraveler.com/wp-content/themes/flatsome/assets/js/chunk.countup.fe2c1016.js
h2
460.50100005232
522.12100010365
2300
0
200
application/javascript
Other
https://theinsatiabletraveler.com/wp-content/themes/flatsome/assets/js/chunk.sticky-sidebar.a58a6557.js
h2
460.62400005758
509.53300017864
4076
0
200
application/javascript
Other
https://theinsatiabletraveler.com/wp-content/themes/flatsome/assets/js/chunk.tooltips.29144c1c.js
h2
460.74700006284
516.46900014021
5719
0
200
application/javascript
Other
https://theinsatiabletraveler.com/wp-content/themes/flatsome/assets/js/chunk.vendors-popups.947eca5c.js
h2
460.92900005169
546.6599999927
8083
0
200
application/javascript
Other
https://theinsatiabletraveler.com/wp-content/themes/flatsome/assets/js/chunk.vendors-slider.f0d2cbc9.js
h2
461.16900001653
570.69500000216
14526
0
200
application/javascript
Other
data
461.82900015265
461.89600019716
0
68
200
image/svg+xml
Image
data
473.26600016095
473.34800008684
0
68
200
image/svg+xml
Image
data
474.2410001345
474.30200013332
0
69
200
image/svg+xml
Image
https://theinsatiabletraveler.com/wp-content/uploads/2021/06/Chris-Pic-of-me-1-1.jpg
h2
477.46099997312
588.68200005963
226931
226127
200
image/jpeg
Image
https://theinsatiabletraveler.com/wp-content/themes/flatsome/assets/css/icons/fl-icons.woff2?v=3.15.5
h2
479.68100011349
525.08700010367
7482
6752
200
font/woff2
Font
data
503.93800018355
504.03700000606
0
70
200
image/svg+xml
Image
data
505.28600020334
505.38900005631
0
69
200
image/svg+xml
Image
data
506.56400015578
506.65200012736
0
70
200
image/svg+xml
Image
data
507.72400014102
507.79800000601
0
69
200
image/svg+xml
Image
data
508.72200005688
508.81900009699
0
69
200
image/svg+xml
Image
data
509.71100013703
509.77400015108
0
70
200
image/svg+xml
Image
data
510.60100016184
510.66700019874
0
70
200
image/svg+xml
Image
data
511.60700013861
511.69600011781
0
70
200
image/svg+xml
Image
data
512.58400012739
512.64800014906
0
68
200
image/svg+xml
Image
data
513.54700000957
513.60700000077
0
68
200
image/svg+xml
Image
data
514.4319999963
514.49000020511
0
68
200
image/svg+xml
Image
data
515.36200009286
515.41600003839
0
68
200
image/svg+xml
Image
data
516.50400017388
516.56600018032
0
68
200
image/svg+xml
Image
data
517.46800006367
517.53000007011
0
68
200
image/svg+xml
Image
data
518.40599998832
518.4710000176
0
68
200
image/svg+xml
Image
https://pixel.wp.com/g.gif?v=ext&j=1%3A11.2&blog=161129945&post=66920&tz=-4&srv=theinsatiabletraveler.com&host=theinsatiabletraveler.com&ref=&fcp=476&rand=0.007992625248433471
h2
615.07100006565
629.64300019667
218
50
200
image/gif
Image
https://theinsatiabletraveler.com/wp-content/uploads/2020/05/The-Insatiable-Traveler-Logo-20170527.jpg
h2
666.21200018562
712.36400003545
7152
6256
200
image/webp
Image
https://theinsatiabletraveler.com/wp-content/uploads/2021/12/COVER_IMAGE.jpg
h2
841.50900016539
983.76099998131
315058
314338
200
image/jpeg
Image
https://theinsatiabletraveler.com/wp-content/uploads/2016/07/Mongolia-9735-768x512.jpg
h2
841.69999998994
948.61300010234
115166
114446
200
image/jpeg
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)
311.162
13.692
325.086
7.481
412.541
5.762
448.396
9.459
457.883
5.113
463.005
7.948
475.804
19.702
495.552
33.468
531.013
47.158
596.001
17.367
613.671
40.006
653.77
9.965
671.174
6.819
678.003
15.398
839.552
6.445
1006.077
5.312
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Other

Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Theinsatiabletraveler.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Theinsatiabletraveler.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Theinsatiabletraveler.com should consider minifying JS files.
Reduce unused JavaScript
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
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 190 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://theinsatiabletraveler.com/
191.153
Avoid multiple page redirects — Potential savings of 630 ms
Redirects can cause additional delays before the page can begin loading. Theinsatiabletraveler.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://theinsatiabletraveler.com/
630
https://theinsatiabletraveler.com/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Theinsatiabletraveler.com 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 0 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://theinsatiabletraveler.com/
167
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
URL Potential Savings (Ms)
https://theinsatiabletraveler.com/wp-content/uploads/2021/06/Chris-Pic-of-me-1-1.jpg
0
Avoids enormous network payloads — Total size was 882 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://theinsatiabletraveler.com/wp-content/uploads/2021/12/COVER_IMAGE.jpg
315058
https://theinsatiabletraveler.com/wp-content/uploads/2021/06/Chris-Pic-of-me-1-1.jpg
226931
https://theinsatiabletraveler.com/wp-content/uploads/2016/07/Mongolia-9735-768x512.jpg
115166
https://theinsatiabletraveler.com/
40581
https://theinsatiabletraveler.com/wp-content/cache/autoptimize/css/autoptimize_single_ed118ba32d919597ca2f2e4525bb9461.css?ver=3.15.5
34259
https://theinsatiabletraveler.com/wp-includes/js/jquery/jquery.min.js?ver=3.6.0
32696
https://theinsatiabletraveler.com/wp-content/cache/autoptimize/js/autoptimize_7b887d747b65d36c9265d1accd166838.js
26173
https://theinsatiabletraveler.com/wp-content/cache/autoptimize/css/autoptimize_single_ec6a0b120600a6c45807c38a3cb6b535.css?ver=11.2
17434
https://theinsatiabletraveler.com/wp-content/themes/flatsome/assets/js/chunk.vendors-slider.f0d2cbc9.js
14526
https://theinsatiabletraveler.com/wp-content/cache/autoptimize/css/autoptimize_single_c89e84ad12af687b97f85adc6bee8219.css?ver=2.16.1
10443
Uses efficient cache policy on static assets — 0 resources found
Theinsatiabletraveler.com can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
Avoid chaining critical requests — 8 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Theinsatiabletraveler.com 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://theinsatiabletraveler.com/
778.016
89.128
9.876
https://theinsatiabletraveler.com/wp-includes/js/jquery/jquery.min.js?ver=3.6.0
406.336
176.656
4.836
Unattributable
124.352
10.528
0.56
https://theinsatiabletraveler.com/wp-content/cache/autoptimize/js/autoptimize_7b887d747b65d36c9265d1accd166838.js
91
61.156
4.736
https://theinsatiabletraveler.com/wp-content/plugins/autoptimize/classes/external/js/lazysizes.min.js?ao_version=3.1.1.1
83.204
52.472
0.732
Minimizes main-thread work — 1.6 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)
Other
452.416
Script Evaluation
442.836
Style & Layout
423.468
Rendering
146.268
Parse HTML & CSS
120.696
Script Parsing & Compilation
25.892
All text remains visible during webfont loads
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
Keep request counts low and transfer sizes small — 26 requests • 882 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
26
902911
Image
5
664525
Script
9
92006
Stylesheet
4
63141
Document
1
40581
Other
6
35176
Font
1
7482
Media
0
0
Third-party
2
3540
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)
3540
0
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.
Element
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
5.0485839570019E-5
3.8637122119913E-5
1.2982073032291E-5
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 — 6 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://theinsatiabletraveler.com/
1410
94
https://stats.wp.com/e-202233.js
4560
80
https://theinsatiabletraveler.com/
1504
69
https://theinsatiabletraveler.com/wp-includes/js/dist/vendor/regenerator-runtime.min.js?ver=0.13.9
3060
67
https://theinsatiabletraveler.com/wp-includes/js/jquery/jquery.min.js?ver=3.6.0
4640
62
https://theinsatiabletraveler.com/
1260
55
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Image elements have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
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 theinsatiabletraveler.com on mobile screens.
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.

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 — 2.0 s
The time taken for the first image or text on the page to be rendered.

Other

Eliminate render-blocking resources — Potential savings of 640 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Theinsatiabletraveler.com 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://theinsatiabletraveler.com/wp-content/cache/autoptimize/css/autoptimize_single_c89e84ad12af687b97f85adc6bee8219.css?ver=2.16.1
10443
300
https://theinsatiabletraveler.com/wp-content/cache/autoptimize/css/autoptimize_single_ed118ba32d919597ca2f2e4525bb9461.css?ver=3.15.5
34259
150
https://theinsatiabletraveler.com/wp-includes/js/jquery/jquery.min.js?ver=3.6.0
32696
150
Reduce unused CSS — Potential savings of 45 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Theinsatiabletraveler.com 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://theinsatiabletraveler.com/wp-content/cache/autoptimize/css/autoptimize_single_ed118ba32d919597ca2f2e4525bb9461.css?ver=3.15.5
34259
29120
https://theinsatiabletraveler.com/wp-content/cache/autoptimize/css/autoptimize_single_ec6a0b120600a6c45807c38a3cb6b535.css?ver=11.2
17434
17339
Efficiently encode images — Potential savings of 92 KiB
Unoptimized images can consume more cellular data than what is necessary.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://theinsatiabletraveler.com/wp-content/uploads/2021/12/COVER_IMAGE.jpg
314338
78095
https://theinsatiabletraveler.com/wp-content/uploads/2016/07/Mongolia-9735-768x512.jpg
114446
16415
Avoid an excessive DOM size — 1,213 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
1213
Maximum DOM Depth
20
Maximum Child Elements
32
First Contentful Paint (3G) — 3960 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.

Metrics

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

Other

Properly size images — Potential savings of 226 KiB
Images can slow down the page's load time. Theinsatiabletraveler.com should consider serving more appropriate-sized images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://theinsatiabletraveler.com/wp-content/uploads/2021/12/COVER_IMAGE.jpg
314338
231826
Serve images in next-gen formats — Potential savings of 328 KiB
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://theinsatiabletraveler.com/wp-content/uploads/2021/12/COVER_IMAGE.jpg
314338
203015.65
https://theinsatiabletraveler.com/wp-content/uploads/2021/06/Chris-Pic-of-me-1-1.jpg
226127
71402.45
https://theinsatiabletraveler.com/wp-content/uploads/2016/07/Mongolia-9735-768x512.jpg
114446
61581.45
Does not use passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Source
80

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of theinsatiabletraveler.com. 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.
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.
`button`, `link`, and `menuitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[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.
ARIA `meter` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `progressbar` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[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 `tooltip` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `treeitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[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.
`<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.
`<object>` elements have alternate 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.
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.

Audio and video

`<video>` elements contain a `<track>` element with `[kind="captions"]`
Theinsatiabletraveler.com may provide assistance to deaf or hearing-impaired users with captions on videos.

Navigation

`[id]` attributes on active, focusable elements are not 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.
Failing Elements
Heading elements are not 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.
Failing Elements

Names and labels

Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements
Links do not 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.

Best practices

`[user-scalable="no"]` is used in the `<meta name="viewport">` element or the `[maximum-scale]` attribute is less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.
Failing Elements

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.
92

Best Practices

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

Audits

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.
Avoids front-end JavaScript libraries with known security vulnerabilities
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.
Ensure CSP is effective against XSS attacks
Significantly reduce the risk of cross-site scripting attacks (XSS) by ensuring you have a strong Content Security Policy (CSP).
Description Directive Severity
No CSP found in enforcement mode
High

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

Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
jQuery
3.6.0
WordPress
6.0.1
core-js
core-js-global@3.19.1
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.
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

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 Request Resolution
http://theinsatiabletraveler.com/
Allowed
78

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for theinsatiabletraveler.com. 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 theinsatiabletraveler.com on mobile screens.
Document uses legible font sizes — 99.22% 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
.is-xsmall
0.68%
11.2px
.button, button, input[type=submit], input[type=reset], input[type=button]
0.07%
10.67px
.is-large
0.04%
9.02px
99.22%
≥ 12px

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

Mobile Friendly

Tap targets are not sized appropriately — 96% 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.
Tap Target Size Overlapping Target
42x41

Content Best Practices

Links do not have descriptive text — 6 links found
Make use of descriptive link text to assist search engines in understanding the content.
Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements

Crawling and Indexing

robots.txt is not valid — 3 errors found
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.
Line # Content Error
4
Disallow; /wp-admin/
Syntax not understood
5
Disallow; /readme.html
Syntax not understood
6
Disallow; /refer/
Syntax not understood

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.
40

PWA

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

PWA Optimized

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 theinsatiabletraveler.com on mobile screens.
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.

Installable

Web app manifest or service worker do not meet the installability requirements — 1 reason
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
Failure reason
No manifest was fetched

PWA Optimized

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.
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: 104.18.41.185
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
Cloudflare, Inc.
Registration

Domain Registrant

Private Registration: Yes
Name: Registration Private
Organization: Domains By Proxy, LLC
Country: US
City: Scottsdale
State: Arizona
Post Code: 85260
Email: THEINSATIABLETRAVELER.COM@domainsbyproxy.com
Phone: +1.4806242599
Note: Registration information is derived from various sources and may be inaccurate.

Domain Registrar

Name IP Address
GoDaddy.com, LLC 23.208.40.188
Security

Visitor Safety

Mature Content: Not Likely
McAfee WebAdvisor Rating: Safe
WOT Rating:
WOT Trustworthiness:
WOT Child Safety:
Note: Safety information is not guaranteed.

SSL/TLS Certificate

Issued To: theinsatiabletraveler.com
Issued By: Cloudflare Inc ECC CA-3
Valid From: 1st May, 2022
Valid To: 1st May, 2023
Subject: CN = theinsatiabletraveler.com
O = Cloudflare, Inc.
L = San Francisco
S = US
Hash: 7e1ca320
Issuer: CN = Cloudflare Inc ECC CA-3
O = Cloudflare, Inc.
S = US
Version: 2
Serial Number: 1576287126681043210670739422533778331
Serial Number (Hex): 012F94F4A25F7A2D79B272D866E1FB9B
Valid From: 1st May, 2024
Valid To: 1st May, 2024
Signature Algorithm (Short Name): ecdsa-with-SHA256
Signature Algorithm (Long Name): ecdsa-with-SHA256
Authority Key Identifier: keyid:A5:CE:37:EA:EB:B0:75:0E:94:67:88:B4:45:FA:D9:24:10:87:96:1F
Extended Key Usage: TLS Web Server Authentication, TLS Web Client Authentication
CRL Distribution Points:
Full Name:
URI:http://crl3.digicert.com/CloudflareIncECCCA-3.crl

Full Name:
URI:http://crl4.digicert.com/CloudflareIncECCCA-3.crl

Certificate Policies: Policy: 2.23.140.1.2.2
CPS: http://www.digicert.com/CPS

Authority Information Access: OCSP - URI:http://ocsp.digicert.com
CA Issuers - URI:http://cacerts.digicert.com/CloudflareIncECCCA-3.crt

SCT List: Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : AD:F7:BE:FA:7C:FF:10:C8:8B:9D:3D:9C:1E:3E:18:6A:
B4:67:29:5D:CF:B1:0C:24:CA:85:86:34:EB:DC:82:8A
Timestamp : May 1 01:26:40.475 2022 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:21:00:FA:0E:4F:24:BF:90:A8:27:99:A0:9A:
73:EB:8C:74:1E:D5:03:96:6C:E9:C6:E0:C5:3C:3A:06:
7E:9A:B2:7E:DA:02:20:56:0B:F6:A0:B0:73:4C:C4:65:
A6:7D:00:C8:21:9F:8B:7B:E0:80:AC:87:39:8B:99:5B:
03:6C:DD:7B:25:A5:BD
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 35:CF:19:1B:BF:B1:6C:57:BF:0F:AD:4C:6D:42:CB:BB:
B6:27:20:26:51:EA:3F:E1:2A:EF:A8:03:C3:3B:D6:4C
Timestamp : May 1 01:26:40.465 2022 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:44:02:20:4A:7B:E8:3A:73:18:25:A2:BC:81:EB:CA:
DC:6D:45:A5:06:1C:70:AD:40:9B:55:3B:E0:33:60:C5:
B6:9F:73:35:02:20:13:11:0B:04:0E:FD:2B:8E:8C:FE:
E2:E6:43:4D:0D:83:96:BF:38:0A:B6:75:5A:DA:D2:31:
37:5A:4C:78:00:BC
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : B3:73:77:07:E1:84:50:F8:63:86:D6:05:A9:DC:11:09:
4A:79:2D:B1:67:0C:0B:87:DC:F0:03:0E:79:36:A5:9A
Timestamp : May 1 01:26:40.525 2022 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:46:02:21:00:F1:23:ED:78:14:55:74:64:4C:8B:9F:
CE:50:D7:73:C1:01:DC:7B:6E:60:88:13:81:1F:74:B0:
5E:DA:85:92:D2:02:21:00:86:0D:61:22:A3:36:05:B3:
29:AE:52:83:27:5C:FC:09:F7:D1:49:F4:16:2D:FF:64:
4C:CB:19:E0:EA:78:E9:16
Key Usage: Digital Signature
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:theinsatiabletraveler.com
Technical

DNS Lookup

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Date: 25th August, 2022
Content-Type: text/html; charset=UTF-8
Cache-Control: s-maxage=31536000, max-age=60
Server: cloudflare
Connection: keep-alive
CF-Ray: 7400bdbffc5e8cdd-EWR
Link: <https://theinsatiabletraveler.com/wp-json/>; rel="https://api.w.org/", <https://theinsatiabletraveler.com/wp-json/wp/v2/pages/66920>; rel="alternate"; type="application/json", <https://wp.me/PaU5g5-hpm>; rel=shortlink
Strict-Transport-Security: max-age=15552000; preload
Vary: Accept-Encoding
CF-Cache-Status: DYNAMIC
Expect-CT: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
X-BigScoots-Cache: cache
X-BigScoots-Cache-Active: 1
X-BigScoots-Cache-Control: s-maxage=31536000, max-age=60
X-BigScoots-Cache-Cookies-Bypass: bscache-feature-not-enabled
x-bigscoots-cache-worker-status: miss
X-Content-Type-Options: nosniff
X-Hosted-By: BigScoots
X-Powered-By: centminmod
alt-svc: h3=":443"; ma=86400, h3-29=":443"; ma=86400

Whois Lookup

Created: 31st July, 2013
Changed: 1st July, 2022
Expires: 31st July, 2024
Registrar: GoDaddy.com, LLC
Status: clientTransferProhibited
clientUpdateProhibited
clientRenewProhibited
clientDeleteProhibited
Nameservers: gerald.ns.cloudflare.com
nola.ns.cloudflare.com
Owner Name: Registration Private
Owner Organization: Domains By Proxy, LLC
Owner Street: DomainsByProxy.com
2155 E Warner Rd
Owner Post Code: 85284
Owner City: Tempe
Owner State: Arizona
Owner Country: US
Owner Phone: +1.4806242599
Owner Email: Select Contact Domain Holder link at https://www.godaddy.com/whois/results.aspx?domain=THEINSATIABLETRAVELER.COM
Admin Name: Registration Private
Admin Organization: Domains By Proxy, LLC
Admin Street: DomainsByProxy.com
2155 E Warner Rd
Admin Post Code: 85284
Admin City: Tempe
Admin State: Arizona
Admin Country: US
Admin Phone: +1.4806242599
Admin Email: Select Contact Domain Holder link at https://www.godaddy.com/whois/results.aspx?domain=THEINSATIABLETRAVELER.COM
Tech Name: Registration Private
Tech Organization: Domains By Proxy, LLC
Tech Street: DomainsByProxy.com
2155 E Warner Rd
Tech Post Code: 85284
Tech City: Tempe
Tech State: Arizona
Tech Country: US
Tech Phone: +1.4806242599
Tech Email: Select Contact Domain Holder link at https://www.godaddy.com/whois/results.aspx?domain=THEINSATIABLETRAVELER.COM
Full Whois: Domain Name: THEINSATIABLETRAVELER.COM
Registry Domain ID: 1818903019_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.godaddy.com
Registrar URL: https://www.godaddy.com
Updated Date: 2022-07-01T13:05:54Z
Creation Date: 2013-07-31T14:32:43Z
Registrar Registration Expiration Date: 2024-07-31T14:32:43Z
Registrar: GoDaddy.com, LLC
Registrar IANA ID: 146
Registrar Abuse Contact Email: abuse@godaddy.com
Registrar Abuse Contact Phone: +1.4806242505
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Domain Status: clientUpdateProhibited https://icann.org/epp#clientUpdateProhibited
Domain Status: clientRenewProhibited https://icann.org/epp#clientRenewProhibited
Domain Status: clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited
Registry Registrant ID: Not Available From Registry
Registrant Name: Registration Private
Registrant Organization: Domains By Proxy, LLC
Registrant Street: DomainsByProxy.com
Registrant Street: 2155 E Warner Rd
Registrant City: Tempe
Registrant State/Province: Arizona
Registrant Postal Code: 85284
Registrant Country: US
Registrant Phone: +1.4806242599
Registrant Phone Ext:
Registrant Fax: +1.4806242598
Registrant Fax Ext:
Registrant Email: Select Contact Domain Holder link at https://www.godaddy.com/whois/results.aspx?domain=THEINSATIABLETRAVELER.COM
Registry Admin ID: Not Available From Registry
Admin Name: Registration Private
Admin Organization: Domains By Proxy, LLC
Admin Street: DomainsByProxy.com
Admin Street: 2155 E Warner Rd
Admin City: Tempe
Admin State/Province: Arizona
Admin Postal Code: 85284
Admin Country: US
Admin Phone: +1.4806242599
Admin Phone Ext:
Admin Fax: +1.4806242598
Admin Fax Ext:
Admin Email: Select Contact Domain Holder link at https://www.godaddy.com/whois/results.aspx?domain=THEINSATIABLETRAVELER.COM
Registry Tech ID: Not Available From Registry
Tech Name: Registration Private
Tech Organization: Domains By Proxy, LLC
Tech Street: DomainsByProxy.com
Tech Street: 2155 E Warner Rd
Tech City: Tempe
Tech State/Province: Arizona
Tech Postal Code: 85284
Tech Country: US
Tech Phone: +1.4806242599
Tech Phone Ext:
Tech Fax: +1.4806242598
Tech Fax Ext:
Tech Email: Select Contact Domain Holder link at https://www.godaddy.com/whois/results.aspx?domain=THEINSATIABLETRAVELER.COM
Name Server: GERALD.NS.CLOUDFLARE.COM
Name Server: NOLA.NS.CLOUDFLARE.COM
DNSSEC: unsigned
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/
>>> Last update of WHOIS database: 2022-08-25T02:01:42Z <<<
For more information on Whois status codes, please visit https://icann.org/epp

TERMS OF USE: The data contained in this registrar's Whois database, while believed by the
registrar to be reliable, is provided "as is" with no guarantee or warranties regarding its
accuracy. This information is provided for the sole purpose of assisting you in obtaining
information about domain name registration records. Any use of this data for any other purpose
is expressly forbidden without the prior written permission of this registrar. By submitting
an inquiry, you agree to these terms and limitations of warranty. In particular, you agree not
to use this data to allow, enable, or otherwise support the dissemination or collection of this
data, in part or in its entirety, for any purpose, such as transmission by e-mail, telephone,
postal mail, facsimile or other means of mass unsolicited, commercial advertising or solicitations
of any kind, including spam. You further agree not to use this data to enable high volume, automated
or robotic electronic processes designed to collect or compile this data for any purpose, including
mining this data for your own personal or commercial purposes. Failure to comply with these terms
may result in termination of access to the Whois database. These terms may be subject to modification
at any time without notice.

Nameservers

Name IP Address
gerald.ns.cloudflare.com 108.162.193.168
nola.ns.cloudflare.com 172.64.32.212
Related

Subdomains

Similar Sites

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Sites hosted on the same IP address

Domain Valuation Snoop Score
0/5
$3,410 USD 2/5
$245 USD 1/5
$4,312 USD 2/5