gemtravels.com

gemtravels.com is SSL secured

Free website and domain report on gemtravels.com

Last Updated: 18th May, 2020 Update Now
Overview

Snoop Summary for gemtravels.com

This is a free and comprehensive report about gemtravels.com. The domain gemtravels.com is currently hosted on a server located in Singapore in Singapore with the IP address 172.104.171.194, where SGD is the local currency and the local language is Mandarin. Gemtravels.com has the potential to be earning an estimated $1 USD per day from advertising revenue. If gemtravels.com was to be sold it would possibly be worth $903 USD (based on the daily revenue potential of the website over a 24 month period). Gemtravels.com is somewhat popular with an estimated 429 daily unique visitors. This report was last updated 18th May, 2020.

About gemtravels.com

Site Preview: gemtravels.com gemtravels.com
Title: Home
Description:
Keywords and Tags: travel
Related Terms:
Fav Icon:
Age: Over 22 years old
Domain Created: 19th March, 2002
Domain Updated: 11th September, 2015
Domain Expires: 19th March, 2025
Review

Snoop Score

1/5

Valuation

$903 USD
Note: All valuation figures are estimates.

Popularity

Low
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 2,344,953
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: 429
Monthly Visitors: 13,057
Yearly Visitors: 156,585
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $1 USD
Monthly Revenue: $37 USD
Yearly Revenue: $446 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: gemtravels.com 14
Domain Name: gemtravels 10
Extension (TLD): com 3
Expiry Check:

Page Speed Analysis

Average Load Time:
Load Time Comparison:

PageSpeed Insights

Avg. (All Categories) 75
Performance 80
Accessibility 77
Best Practices 85
SEO 88
Progressive Web App 46
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
Simulate loading on desktop
80

Performance

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

Metrics

Time to Interactive — 1.2 s
The time taken for the page to become fully interactive.
First CPU Idle — 1.2 s
The time taken for the page's main thread to be quiet enough to handle input.
Max Potential First Input Delay — 30 ms
Users could experience a delay when interacting with the page.

Other

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 gemtravels.com as laggy when the latency is higher than 0.05 seconds.
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).
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://gemtravels.com/
0
483.98399999132
392
0
301
text/html
https://gemtravels.com/
484.33799999475
1417.1919999935
1196
2503
200
text/html
Document
https://gemtravels.com/assets/mobirise/css/mbr-additional.css
1427.8169999889
2315.3809999931
3445
17312
200
text/css
Stylesheet
https://gemtravels.com/assets/web/assets/mobirise-icons/mobirise-icons.css
1428.6299999949
2487.4359999958
1913
7613
200
text/css
Stylesheet
https://gemtravels.com/assets/bootstrap/css/bootstrap.min.css
1428.8299999898
2686.8810000014
21039
153182
200
text/css
Stylesheet
https://gemtravels.com/assets/bootstrap/css/bootstrap-grid.min.css
1429.0829999954
2406.0210000025
5275
48488
200
text/css
Stylesheet
https://gemtravels.com/assets/bootstrap/css/bootstrap-reboot.min.css
1429.3319999997
2453.7310000014
1870
3836
200
text/css
Stylesheet
https://gemtravels.com/assets/tether/tether.min.css
1429.4430000009
2469.471999997
602
237
200
text/css
Stylesheet
https://gemtravels.com/assets/theme/css/style.css
1429.6719999984
2355.9830000013
4256
23019
200
text/css
Stylesheet
https://gemtravels.com/assets/web/assets/jquery/jquery.min.js
1429.9219999957
2604.1289999994
32926
95931
200
application/javascript
Script
https://gemtravels.com/assets/popper/popper.min.js
1430.0119999971
2468.9720000024
7074
18994
200
application/javascript
Script
https://gemtravels.com/assets/bootstrap/js/bootstrap.min.js
1430.5999999924
2583.0999999889
14429
55775
200
application/javascript
Script
https://gemtravels.com/assets/tether/tether.min.js
1430.9419999918
2420.736
7100
23217
200
application/javascript
Script
https://gemtravels.com/assets/smoothscroll/smooth-scroll.js
1431.0330000008
2496.0730000021
7227
25569
200
application/javascript
Script
https://gemtravels.com/assets/theme/js/script.js
1431.1809999926
1666.3029999909
9514
49077
200
application/javascript
Script
https://fonts.googleapis.com/css?family=Rubik:300,300i,400,400i,500,500i,700,700i,900,900i&display=swap
2316.6939999937
2331.9059999922
1892
14733
200
text/css
Stylesheet
https://fonts.gstatic.com/s/rubik/v9/iJWHBXyIfDnIV7Fqj2md8WA.woff2
2734.2449999996
2737.1869999915
21637
20988
200
font/woff2
Font
https://fonts.gstatic.com/s/rubik/v9/iJWKBXyIfDnIV7nBrXw.woff2
2735.3969999967
2740.2529999963
23304
22656
200
font/woff2
Font
https://fonts.gstatic.com/s/rubik/v9/iJWHBXyIfDnIV7Eyjmmd8WA.woff2
2736.5529999952
2739.7479999927
23820
23172
200
font/woff2
Font
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)
1439.445
7.394
2713.065
67.442
2789.375
9.59
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data

Opportunities

Properly size images
Images can slow down the page's load time. Gemtravels.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Gemtravels.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Gemtravels.com should consider minifying CSS files.
Minify JavaScript — Potential savings of 8 KB
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Gemtravels.com should consider minifying JS files.
URL Size (Bytes) Potential Savings (Bytes)
https://gemtravels.com/assets/theme/js/script.js
9514
4676
https://gemtravels.com/assets/smoothscroll/smooth-scroll.js
7227
3713
Remove unused CSS — Potential savings of 20 KB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Gemtravels.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
URL Size (Bytes) Potential Savings (Bytes)
https://gemtravels.com/assets/bootstrap/css/bootstrap.min.css
21039
20554
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.
Avoid multiple page redirects — Potential savings of 190 ms
Redirects can cause additional delays before the page can begin loading. Gemtravels.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
(Start) http://gemtravels.com/
0
https://gemtravels.com/
190
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Gemtravels.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.

Diagnostics

Avoids enormous network payloads — Total size was 184 KB
Large network payloads can cost users money and are linked to long load times.
URL Size (Bytes)
https://gemtravels.com/assets/web/assets/jquery/jquery.min.js
32926
https://fonts.gstatic.com/s/rubik/v9/iJWHBXyIfDnIV7Eyjmmd8WA.woff2
23820
https://fonts.gstatic.com/s/rubik/v9/iJWKBXyIfDnIV7nBrXw.woff2
23304
https://fonts.gstatic.com/s/rubik/v9/iJWHBXyIfDnIV7Fqj2md8WA.woff2
21637
https://gemtravels.com/assets/bootstrap/css/bootstrap.min.css
21039
https://gemtravels.com/assets/bootstrap/js/bootstrap.min.js
14429
https://gemtravels.com/assets/theme/js/script.js
9514
https://gemtravels.com/assets/smoothscroll/smooth-scroll.js
7227
https://gemtravels.com/assets/tether/tether.min.js
7100
https://gemtravels.com/assets/popper/popper.min.js
7074
Uses efficient cache policy on static assets — 13 resources found
Gemtravels.com can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Size (Bytes)
https://gemtravels.com/assets/web/assets/jquery/jquery.min.js
2592000000
32926
https://gemtravels.com/assets/bootstrap/css/bootstrap.min.css
2592000000
21039
https://gemtravels.com/assets/bootstrap/js/bootstrap.min.js
2592000000
14429
https://gemtravels.com/assets/theme/js/script.js
2592000000
9514
https://gemtravels.com/assets/smoothscroll/smooth-scroll.js
2592000000
7227
https://gemtravels.com/assets/tether/tether.min.js
2592000000
7100
https://gemtravels.com/assets/popper/popper.min.js
2592000000
7074
https://gemtravels.com/assets/bootstrap/css/bootstrap-grid.min.css
2592000000
5275
https://gemtravels.com/assets/theme/css/style.css
2592000000
4256
https://gemtravels.com/assets/mobirise/css/mbr-additional.css
2592000000
3445
https://gemtravels.com/assets/web/assets/mobirise-icons/mobirise-icons.css
2592000000
1913
https://gemtravels.com/assets/bootstrap/css/bootstrap-reboot.min.css
2592000000
1870
https://gemtravels.com/assets/tether/tether.min.css
2592000000
602
Avoids an excessive DOM size — 19 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
19
Maximum DOM Depth
7
Maximum Child Elements
9
Avoid chaining critical requests — 15 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Gemtravels.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.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)
Other
51.278
3.394
0.969
Minimizes main-thread work — 0.1 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
41.468
Other
31.036
Style & Layout
27.111
Parse HTML & CSS
13.015
Script Parsing & Compilation
8.198
Rendering
3.62
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 — 19 requests • 184 KB
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
19
188911
Script
6
78270
Font
3
68761
Stylesheet
8
40292
Document
1
1196
Other
1
392
Image
0
0
Media
0
0
Third-party
4
70653
Minimize third-party usage
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load 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.

Metrics

First Contentful Paint — 1.2 s
The time taken for the first image or text on the page to be rendered.
First Meaningful Paint — 1.2 s
The time taken for the primary content of the page to be rendered.

Opportunities

Eliminate render-blocking resources — Potential savings of 420 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Gemtravels.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Size (Bytes) Potential Savings (Ms)
https://gemtravels.com/assets/web/assets/mobirise-icons/mobirise-icons.css
1913
150
https://gemtravels.com/assets/bootstrap/css/bootstrap.min.css
21039
230
https://gemtravels.com/assets/bootstrap/css/bootstrap-grid.min.css
5275
150
https://gemtravels.com/assets/bootstrap/css/bootstrap-reboot.min.css
1870
150
https://gemtravels.com/assets/tether/tether.min.css
602
150
https://gemtravels.com/assets/theme/css/style.css
4256
70

Metrics

Speed Index — 2.4 s
The time taken for the page contents to be visibly populated.

Opportunities

Reduce server response times (TTFB) — Root document took 930 ms
Time to First Byte (TTFB) identifies the time at which the server sends a response.
77

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of gemtravels.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.
`[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-*]` 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.

Audio and video

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

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

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>` or `<template>` 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.

Best practices

`[id]` attributes on the page are unique
It is advised to keep all id attributes unique in order to prevent instances from being overlooked by screen readers and other assistive technologies.
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.

Internationalization and localization

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

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

Internationalization and localization

`<html>` element does not have 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.
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.
Headings don't skip levels
Ensure that headings create an outline for the page and that heading levels are not skipped.
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.
85

Best Practices

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

Other

Avoids Application Cache
Application cache is deprecated and is no longer recommended.
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.
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.
Page has the HTML doctype
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
Bootstrap
4.2.1
jQuery
1.11.2
jQuery (Fast path)
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 deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
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.
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.
Displays images with correct aspect ratio
Ensure that image display dimensions match their natural aspect ratio.

Other

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://gemtravels.com/
Includes front-end JavaScript libraries with known security vulnerabilities — 3 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
1
Medium
2
Medium
88

SEO

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

Content Best Practices

Document does not have 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.

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

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 gemtravels.com. 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 gemtravels.com on mobile screens.
Contains some content when JavaScript is not available
Apps should display alternative content for when JavaScript is disabled.

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://gemtravels.com/
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
Does not provide 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.

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) 75
Performance 73
Accessibility 77
Best Practices 85
SEO 90
Progressive Web App 48
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
Simulate loading on mobile
73

Performance

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

Metrics

Time to Interactive — 3.6 s
The time taken for the page to become fully interactive.
First CPU Idle — 3.6 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.

Other

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 gemtravels.com as laggy when the latency is higher than 0.05 seconds.
Total Blocking Time — 50 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).
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://gemtravels.com/
0
474.0949999541
377
0
301
text/html
https://gemtravels.com/
474.5389999589
704.28099995479
1196
2503
200
text/html
Document
https://gemtravels.com/assets/mobirise/css/mbr-additional.css
714.06799997203
946.56399998348
3445
17312
200
text/css
Stylesheet
https://gemtravels.com/assets/web/assets/mobirise-icons/mobirise-icons.css
715.01299994998
953.77299998654
1913
7613
200
text/css
Stylesheet
https://gemtravels.com/assets/bootstrap/css/bootstrap.min.css
715.17199999653
1935.8649999485
21039
153182
200
text/css
Stylesheet
https://gemtravels.com/assets/bootstrap/css/bootstrap-grid.min.css
715.41799994884
949.077999976
5275
48488
200
text/css
Stylesheet
https://gemtravels.com/assets/bootstrap/css/bootstrap-reboot.min.css
715.6219999888
947.05600000452
1870
3836
200
text/css
Stylesheet
https://gemtravels.com/assets/tether/tether.min.css
715.81099997275
955.50300000468
602
237
200
text/css
Stylesheet
https://gemtravels.com/assets/theme/css/style.css
716.0079999594
947.5509999902
4256
23019
200
text/css
Stylesheet
https://gemtravels.com/assets/web/assets/jquery/jquery.min.js
716.27999999328
1184.7259999486
32926
95931
200
application/javascript
Script
https://gemtravels.com/assets/popper/popper.min.js
716.50399995269
1634.0179999825
7074
18994
200
application/javascript
Script
https://gemtravels.com/assets/bootstrap/js/bootstrap.min.js
716.84199996525
1177.4899999727
14429
55775
200
application/javascript
Script
https://gemtravels.com/assets/tether/tether.min.js
717.04799996223
1610.5079999543
7100
23217
200
application/javascript
Script
https://gemtravels.com/assets/smoothscroll/smooth-scroll.js
717.25599997444
951.13999996101
7227
25569
200
application/javascript
Script
https://gemtravels.com/assets/theme/js/script.js
717.3789999797
952.12799997535
9514
49077
200
application/javascript
Script
https://fonts.googleapis.com/css?family=Rubik:300,300i,400,400i,500,500i,700,700i,900,900i&display=swap
947.96699995641
966.88500000164
1839
14948
200
text/css
Stylesheet
https://fonts.gstatic.com/s/rubik/v9/iJWHBXyIfDnIV7Fqj2md8WD07oB-.woff2
1988.6849999893
1992.9179999745
15476
14828
200
font/woff2
Font
https://fonts.gstatic.com/s/rubik/v9/iJWKBXyIfDnIV7nBrXyw023e.woff2
1989.5689999685
1993.3999999776
16917
16268
200
font/woff2
Font
https://fonts.gstatic.com/s/rubik/v9/iJWHBXyIfDnIV7Eyjmmd8WD07oB-.woff2
1990.5429999926
1993.6499999603
17106
16456
200
font/woff2
Font
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)
725.551
6.47
1956.264
5.712
1962.022
73.038
2040.919
5.587
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data

Opportunities

Properly size images
Images can slow down the page's load time. Gemtravels.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Gemtravels.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Gemtravels.com should consider minifying CSS files.
Minify JavaScript — Potential savings of 8 KB
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Gemtravels.com should consider minifying JS files.
URL Size (Bytes) Potential Savings (Bytes)
https://gemtravels.com/assets/theme/js/script.js
9514
4676
https://gemtravels.com/assets/smoothscroll/smooth-scroll.js
7227
3713
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.
Server response times are low (TTFB) — Root document took 230 ms
Time to First Byte (TTFB) identifies the time at which the server sends a response.
Avoid multiple page redirects — Potential savings of 630 ms
Redirects can cause additional delays before the page can begin loading. Gemtravels.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
(Start) http://gemtravels.com/
0
https://gemtravels.com/
630
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Gemtravels.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.

Diagnostics

Avoids enormous network payloads — Total size was 166 KB
Large network payloads can cost users money and are linked to long load times.
URL Size (Bytes)
https://gemtravels.com/assets/web/assets/jquery/jquery.min.js
32926
https://gemtravels.com/assets/bootstrap/css/bootstrap.min.css
21039
https://fonts.gstatic.com/s/rubik/v9/iJWHBXyIfDnIV7Eyjmmd8WD07oB-.woff2
17106
https://fonts.gstatic.com/s/rubik/v9/iJWKBXyIfDnIV7nBrXyw023e.woff2
16917
https://fonts.gstatic.com/s/rubik/v9/iJWHBXyIfDnIV7Fqj2md8WD07oB-.woff2
15476
https://gemtravels.com/assets/bootstrap/js/bootstrap.min.js
14429
https://gemtravels.com/assets/theme/js/script.js
9514
https://gemtravels.com/assets/smoothscroll/smooth-scroll.js
7227
https://gemtravels.com/assets/tether/tether.min.js
7100
https://gemtravels.com/assets/popper/popper.min.js
7074
Uses efficient cache policy on static assets — 13 resources found
Gemtravels.com can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Size (Bytes)
https://gemtravels.com/assets/web/assets/jquery/jquery.min.js
2592000000
32926
https://gemtravels.com/assets/bootstrap/css/bootstrap.min.css
2592000000
21039
https://gemtravels.com/assets/bootstrap/js/bootstrap.min.js
2592000000
14429
https://gemtravels.com/assets/theme/js/script.js
2592000000
9514
https://gemtravels.com/assets/smoothscroll/smooth-scroll.js
2592000000
7227
https://gemtravels.com/assets/tether/tether.min.js
2592000000
7100
https://gemtravels.com/assets/popper/popper.min.js
2592000000
7074
https://gemtravels.com/assets/bootstrap/css/bootstrap-grid.min.css
2592000000
5275
https://gemtravels.com/assets/theme/css/style.css
2592000000
4256
https://gemtravels.com/assets/mobirise/css/mbr-additional.css
2592000000
3445
https://gemtravels.com/assets/web/assets/mobirise-icons/mobirise-icons.css
2592000000
1913
https://gemtravels.com/assets/bootstrap/css/bootstrap-reboot.min.css
2592000000
1870
https://gemtravels.com/assets/tether/tether.min.css
2592000000
602
Avoids an excessive DOM size — 19 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
19
Maximum DOM Depth
7
Maximum Child Elements
9
Avoid chaining critical requests — 15 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Gemtravels.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.2 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)
Other
200.376
12.216
3.28
https://gemtravels.com/assets/web/assets/jquery/jquery.min.js
128.704
115.764
7.064
https://gemtravels.com/assets/theme/js/script.js
100.952
24.868
4.556
Minimizes main-thread work — 0.5 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
191.012
Other
113.308
Style & Layout
83.06
Parse HTML & CSS
59.488
Script Parsing & Compilation
37.888
Rendering
6.428
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 — 19 requests • 166 KB
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
19
169581
Script
6
78270
Font
3
49499
Stylesheet
8
40239
Document
1
1196
Other
1
377
Image
0
0
Media
0
0
Third-party
4
51338
Minimize third-party usage
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load 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.

Metrics

First Contentful Paint — 3.6 s
The time taken for the first image or text on the page to be rendered.
First Meaningful Paint — 3.6 s
The time taken for the primary content of the page to be rendered.
Speed Index — 5.6 s
The time taken for the page contents to be visibly populated.

Opportunities

Remove unused CSS — Potential savings of 20 KB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Gemtravels.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
URL Size (Bytes) Potential Savings (Bytes)
https://gemtravels.com/assets/bootstrap/css/bootstrap.min.css
21039
20580

Opportunities

Eliminate render-blocking resources — Potential savings of 930 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Gemtravels.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Size (Bytes) Potential Savings (Ms)
https://gemtravels.com/assets/web/assets/mobirise-icons/mobirise-icons.css
1913
480
https://gemtravels.com/assets/bootstrap/css/bootstrap.min.css
21039
1080
https://gemtravels.com/assets/bootstrap/css/bootstrap-grid.min.css
5275
630
https://gemtravels.com/assets/bootstrap/css/bootstrap-reboot.min.css
1870
480
https://gemtravels.com/assets/tether/tether.min.css
602
480
https://gemtravels.com/assets/theme/css/style.css
4256
180

Other

First Contentful Paint (3G) — 7273 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.
77

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of gemtravels.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.
`[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-*]` 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.

Audio and video

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

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

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>` or `<template>` 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.

Best practices

`[id]` attributes on the page are unique
It is advised to keep all id attributes unique in order to prevent instances from being overlooked by screen readers and other assistive technologies.
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.

Internationalization and localization

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

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

Internationalization and localization

`<html>` element does not have 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.
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.
Headings don't skip levels
Ensure that headings create an outline for the page and that heading levels are not skipped.
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.
85

Best Practices

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

Other

Avoids Application Cache
Application cache is deprecated and is no longer recommended.
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.
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.
Page has the HTML doctype
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
Bootstrap
4.2.1
jQuery
1.11.2
jQuery (Fast path)
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 deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
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.
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.
Displays images with correct aspect ratio
Ensure that image display dimensions match their natural aspect ratio.

Other

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://gemtravels.com/
Includes front-end JavaScript libraries with known security vulnerabilities — 3 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
1
Medium
2
Medium
90

SEO

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

Content Best Practices

Document does not have 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.

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 gemtravels.com. 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 gemtravels.com on mobile screens.
Contains some content when JavaScript is not available
Apps should display alternative content for when JavaScript is disabled.

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://gemtravels.com/
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
Does not provide 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.

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: 172.104.171.194
Continent: Asia
Country: Singapore
Singapore Flag
Region:
City: Singapore
Longitude: 103.8547
Latitude: 1.2929
Currencies: SGD
Languages: Mandarin
English
Malay
Tamil

Web Hosting Provider

Name IP Address
Linode
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

Name IP Address
GoDaddy.com LLC 23.220.132.43
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: gemtravels.com
Issued By: Let's Encrypt Authority X3
Valid From: 15th April, 2020
Valid To: 14th July, 2020
Subject: CN = gemtravels.com
Hash: 9c3e8b68
Issuer: CN = Let's Encrypt Authority X3
O = Let's Encrypt
S = US
Version: 2
Serial Number: 0x04D0061992E8D0FAA4F88FC3EBB2B4A514E7
Serial Number (Hex): 04D0061992E8D0FAA4F88FC3EBB2B4A514E7
Valid From: 15th April, 2024
Valid To: 14th July, 2024
Signature Algorithm (Short Name): RSA-SHA256
Signature Algorithm (Long Name): sha256WithRSAEncryption
Authority Key Identifier: keyid:A8:4A:6A:63:04:7D:DD:BA:E6:D1:39:B7:A6:45:65:EF:F3:A8:EC:A1
Extended Key Usage: TLS Web Server Authentication, TLS Web Client Authentication
Certificate Policies: Policy: 2.23.140.1.2.1
Policy: 1.3.6.1.4.1.44947.1.1.1
CPS: http://cps.letsencrypt.org

Authority Information Access: OCSP - URI:http://ocsp.int-x3.letsencrypt.org
CA Issuers - URI:http://cert.int-x3.letsencrypt.org/

SCT List: Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 5E:A7:73:F9:DF:56:C0:E7:B5:36:48:7D:D0:49:E0:32:
7A:91:9A:0C:84:A1:12:12:84:18:75:96:81:71:45:58
Timestamp : Apr 15 06:55:05.793 2020 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:46:02:21:00:E6:C6:7C:9B:D2:5A:7F:C4:08:90:4C:
4F:4F:7E:B6:5D:24:42:17:66:D1:72:70:24:33:26:5C:
67:C9:C7:D9:B4:02:21:00:E8:9E:B7:D7:AC:87:89:03:
82:3B:40:2C:32:A6:21:AE:8B:94:E5:32:5B:3C:FD:9C:
DA:17:C2:9A:BA:5D:D3:ED
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : B2:1E:05:CC:8B:A2:CD:8A:20:4E:87:66:F9:2B:B9:8A:
25:20:67:6B:DA:FA:70:E7:B2:49:53:2D:EF:8B:90:5E
Timestamp : Apr 15 06:55:05.787 2020 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:20:1C:DD:AA:34:A4:5D:ED:B0:58:45:ED:01:
FF:75:31:B7:0A:D9:F3:D3:85:86:31:BA:79:F8:6F:49:
58:36:2B:2B:02:21:00:B1:A6:4F:9E:B9:B1:3A:A2:3B:
C1:CB:F4:8D:73:E7:74:0A:52:D4:74:9C:7F:DA:51:AD:
0B:08:8B:C9:C1:15:7D
Key Usage: Digital Signature, Key Encipherment
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:gemtravels.com
Technical

DNS Lookup

A Records

Host IP Address Class TTL
gemtravels.com. 172.104.171.194 IN 21599

NS Records

Host Nameserver Class TTL
gemtravels.com. ns3.linode.com. IN 21599
gemtravels.com. ns4.linode.com. IN 21599
gemtravels.com. ns2.linode.com. IN 21599
gemtravels.com. ns5.linode.com. IN 21599
gemtravels.com. ns1.linode.com. IN 21599

AAAA Records

IP Address Class TTL
2400:8901::f03c:91ff:fe98:e909 IN 21599

MX Records

Priority Host Server Class TTL
10 gemtravels.com. aspmx3.googlemail.com. IN 14399
10 gemtravels.com. aspmx2.googlemail.com. IN 14399
1 gemtravels.com. aspmx.l.google.com. IN 14399
5 gemtravels.com. alt1.aspmx.l.google.com. IN 14399
10 gemtravels.com. aspmx4.googlemail.com. IN 14399
10 gemtravels.com. aspmx5.googlemail.com. IN 14399
5 gemtravels.com. alt2.aspmx.l.google.com. IN 14399

SOA Records

Domain Name Primary NS Responsible Email TTL
gemtravels.com. ns1.linode.com. admin.gemtravels.com. 21599

TXT Records

Host Value Class TTL
gemtravels.com. google-site-verification=_Jhp3fW83LDGCCniqRnA_ZDTePJDLjFyHJfCz5M74yE IN 21599
gemtravels.com. v=spf1 IN 21599

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Server: nginx-rc
Date: 18th May, 2020
Content-Type: text/html
Content-Length: 2503
Connection: keep-alive
Vary: Accept-Encoding
Last-Modified: 15th April, 2020
ETag: "9c7-5a34ed322ec2e"
Accept-Ranges: bytes
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Strict-Transport-Security: max-age=15768000

Whois Lookup

Created: 19th March, 2002
Changed: 11th September, 2015
Expires: 19th March, 2025
Registrar: GoDaddy.com, LLC
Status: clientTransferProhibited
clientUpdateProhibited
clientRenewProhibited
clientDeleteProhibited
Nameservers: ns1.linode.com
ns2.linode.com
Owner Organization: Gem Tours and Travels Pvt. Ltd.
Owner State: Maharashtra
Owner Country: IN
Owner Email: Select Contact Domain Holder link at https://www.godaddy.com/whois/results.aspx?domain=gemtravels.com
Admin Email: Select Contact Domain Holder link at https://www.godaddy.com/whois/results.aspx?domain=gemtravels.com
Tech Email: Select Contact Domain Holder link at https://www.godaddy.com/whois/results.aspx?domain=gemtravels.com
Full Whois: Domain Name: gemtravels.com
Registry Domain ID: 84637252_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.godaddy.com
Registrar URL: http://www.godaddy.com
Updated Date: 2015-09-11T04:19:33Z
Creation Date: 2002-03-19T16:42:02Z
Registrar Registration Expiration Date: 2025-03-19T15:42:02Z
Registrar: GoDaddy.com, LLC
Registrar IANA ID: 146
Registrar Abuse Contact Email: abuse@godaddy.com
Registrar Abuse Contact Phone: +1.4806242505
Domain Status: clientTransferProhibited http://www.icann.org/epp#clientTransferProhibited
Domain Status: clientUpdateProhibited http://www.icann.org/epp#clientUpdateProhibited
Domain Status: clientRenewProhibited http://www.icann.org/epp#clientRenewProhibited
Domain Status: clientDeleteProhibited http://www.icann.org/epp#clientDeleteProhibited
Registrant Organization: Gem Tours and Travels Pvt. Ltd.
Registrant State/Province: Maharashtra
Registrant Country: IN
Registrant Email: Select Contact Domain Holder link at https://www.godaddy.com/whois/results.aspx?domain=gemtravels.com
Admin Email: Select Contact Domain Holder link at https://www.godaddy.com/whois/results.aspx?domain=gemtravels.com
Tech Email: Select Contact Domain Holder link at https://www.godaddy.com/whois/results.aspx?domain=gemtravels.com
Name Server: NS1.LINODE.COM
Name Server: NS2.LINODE.COM
DNSSEC: unsigned
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/
>>> Last update of WHOIS database: 2020-05-18T11:00:00Z <<<

For more information on Whois status codes, please visit https://www.icann.org/resources/pages/epp-status-codes-2014-06-16-en

Notes:

IMPORTANT: Port43 will provide the ICANN-required minimum data set per
ICANN Temporary Specification, adopted 17 May 2018.
Visit https://whois.godaddy.com to look up contact data for domains
not covered by GDPR policy.

The data contained in GoDaddy.com, LLC's WhoIs database,
while believed by the company 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 GoDaddy.com, LLC. By submitting an inquiry,
you agree to these terms of usage and limitations of warranty. In particular,
you agree not to use this data to allow, enable, or otherwise make possible,
dissemination or collection of this data, in part or in its entirety, for any
purpose, such as the transmission of unsolicited advertising and
and 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.

Please note: the registrant of the domain name is specified
in the "registrant" section. In most cases, GoDaddy.com, LLC
is not the registrant of domain names listed in this database.

Nameservers

Name IP Address
ns1.linode.com 92.123.94.2
ns2.linode.com 92.123.94.3
Related

Subdomains

Similar Sites

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Domain Valuation Snoop Score
0/5

Sites hosted on the same IP address