loki.com

loki.com is SSL secured

Free website and domain report on loki.com

Last Updated: 23rd October, 2021 Update Now
Overview

Snoop Summary for loki.com

This is a free and comprehensive report about loki.com. Loki.com is hosted in Frankfurt am Main, Hesse in Germany on a server with an IP address of 134.122.85.178, where the local currency is EUR and German is the local language. Our records indicate that loki.com is owned/operated by Cyberplay Management Ltd. If loki.com was to be sold it would possibly be worth $327 USD (based on the daily revenue potential of the website over a 24 month period). Loki.com receives an estimated 152 unique visitors every day - a decent amount of traffic! This report was last updated 23rd October, 2021.

About loki.com

Site Preview: loki.com loki.com
Title: This site is not available in your country
Description: A product of Skyhook Wireless, Loki is a new and unique way of interacting with the Internet. For the first time, your computer can automatically incorporate its exact physical location into your Internet experience. It can also let you quickly, efficiently and automatically share your location with others. ... By strict definition, Loki has lots of meanings...official, unofficial, silly and symbolic. Loki is best known as the Norse god of magic and trickery. ...
Keywords and Tags: gambling, hardware, software
Related Terms: automatically create resume, bang trickery, how to incorporate, loki actor, loki season 2, loki season2, norse projects, strict, symbols and meanings, unofficial
Fav Icon:
Age: Over 32 years old
Domain Created: 16th September, 1992
Domain Updated: 28th July, 2021
Domain Expires: 15th September, 2022
Review

Snoop Score

2/5

Valuation

$327 USD
Note: All valuation figures are estimates.

Popularity

Low
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 7,288,960
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: 152
Monthly Visitors: 4,636
Yearly Visitors: 55,591
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $0 USD
Monthly Revenue: $13 USD
Yearly Revenue: $158 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: loki.com 8
Domain Name: loki 4
Extension (TLD): com 3
Expiry Check:

Page Speed Analysis

Average Load Time: 2.21 seconds
Load Time Comparison: Faster than 40% of sites

PageSpeed Insights

Avg. (All Categories) 70
Performance 44
Accessibility 75
Best Practices 80
SEO 80
Progressive Web App 73
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://loki.com
Updated: 23rd October, 2021

2.25 seconds
First Contentful Paint (FCP)
65%
18%
17%

0.00 seconds
First Input Delay (FID)
97%
1%
2%

Simulate loading on desktop
44

Performance

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

Metrics

Cumulative Layout Shift — 0
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Opportunities

Eliminate render-blocking resources — Potential savings of 90 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Loki.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://loki.com/assets/5dd31320/style.css?v=1633701229
6336
70
https://loki.com/assets/242511e2/app.css?v=1631523093
59653
310
Properly size images
Images can slow down the page's load time. Loki.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Loki.com should consider lazy-loading offscreen and hidden images.
Minify CSS — Potential savings of 10 KiB
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Loki.com should consider minifying CSS files.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://loki.com/assets/242511e2/app.css?v=1631523093
59653
10744
Minify JavaScript — Potential savings of 32 KiB
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Loki.com should consider minifying JS files.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://loki.com/assets/242511e2/app.js?v=1633593277
66237
16824
https://loki.com/assets/ccbb3a4a/index.js?v=1620373570
19695
6706
https://loki.com/assets/2ffce410/yii.js?v=1611313698
6930
4343
https://loki.com/assets/e75603cb/jquery_plugins.js?v=1620373570
6191
2738
https://loki.com/assets/7e19f17f/webpush.js?v=1620373570
5737
2277
Reduce unused JavaScript — Potential savings of 39 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://loki.com/assets/242511e2/app.js?v=1633593277
66237
40049
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
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.
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Loki.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://loki.com/assets/242511e2/app.js?v=1633593277
41
https://supportmastersclub.webim.ru/js/button.js
0
https://new.go2ask.org/app/ask/js/app.js?v=1634994381236
0
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.

Diagnostics

Avoids enormous network payloads — Total size was 295 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://loki.com/assets/242511e2/app.js?v=1633593277
66237
https://loki.com/assets/242511e2/app.css?v=1631523093
59653
https://cdnjs.cloudflare.com/ajax/libs/jquery/3.3.1/jquery.min.js
28599
https://loki.com/assets/242511e2/fonts/Lato-Bold.woff2
27433
https://loki.com/assets/242511e2/fonts/Lato-Regular.woff2
27037
https://loki.com/assets/ccbb3a4a/index.js?v=1620373570
19695
https://cdnjs.cloudflare.com/ajax/libs/OwlCarousel2/2.3.4/owl.carousel.min.js
11329
https://cdnjs.cloudflare.com/ajax/libs/slick-carousel/1.6.0/slick.min.js
10197
https://loki.com/assets/2ffce410/yii.js?v=1611313698
6930
https://loki.com/assets/5dd31320/style.css?v=1633701229
6336
Avoids an excessive DOM size — 37 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
37
Maximum DOM Depth
6
Maximum Child Elements
18
Avoid chaining critical requests — 17 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Loki.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.
Keep request counts low and transfer sizes small — 25 requests • 295 KiB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.
Resource Type Requests Transfer Size (Bytes)
Total
25
302135
Script
16
177857
Stylesheet
2
65989
Font
2
54470
Document
1
2496
Other
3
1049
Image
1
274
Media
0
0
Third-party
10
69290
Minimize third-party usage — Third-party code blocked the main thread for 60 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)
69016
56.856
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.
Avoid large layout shifts
Below is a list of all DOM elements that contribute to the CLS of the page.
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks — 10 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://cdnjs.cloudflare.com/ajax/libs/jquery/3.3.1/jquery.min.js
1178
1159
https://loki.com/assets/5e35c887/device.js?v=1620373570
2436
400
https://loki.com/assets/ccbb3a4a/index.js?v=1620373570
960
218
https://loki.com/assets/e75603cb/jquery_plugins.js?v=1620373570
2337
99
https://loki.com/assets/242511e2/app.css?v=1631523093
780
88
Unattributable
265
79
Unattributable
562
78
https://loki.com/en/error/restricted
191
74
https://loki.com/en/error/restricted
490
72
https://cdnjs.cloudflare.com/ajax/libs/jquery/3.3.1/jquery.min.js
2848
72
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 loki.com on mobile screens.

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

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://loki.com/
http/1.1
0
301.77800031379
249
0
301
text/html
https://loki.com/
http/1.1
302.43699997663
1276.386000216
427
0
302
text/html
https://loki.com/en
http/1.1
1277.0500001498
2876.050000079
373
0
302
text/html
https://loki.com/en/error/restricted
http/1.1
2876.8720002845
4083.4340001456
2496
6143
200
text/html
Document
https://loki.com/assets/5dd31320/style.css?v=1633701229
http/1.1
4175.7980003022
4985.117000062
6336
31752
200
text/css
Stylesheet
https://loki.com/assets/242511e2/app.css?v=1631523093
http/1.1
4176.1910002679
5193.0019999854
59653
303204
200
text/css
Stylesheet
https://supportmastersclub.webim.ru/button.php?location=Loki_en
http/1.1
4183.7600003928
5280.6810000911
274
43
200
image/gif
Image
https://cdnjs.cloudflare.com/ajax/libs/jquery/3.3.1/jquery.min.js
h2
4179.1460001841
4277.3900004104
28599
86927
200
application/javascript
Script
https://loki.com/assets/2ffce410/yii.js?v=1611313698
http/1.1
4179.4250002131
4680.5500001647
6930
20934
200
application/x-javascript
Script
https://loki.com/assets/ccbb3a4a/index.js?v=1620373570
http/1.1
4179.7180003487
4891.3220004179
19695
58348
200
application/x-javascript
Script
https://loki.com/assets/5e35c887/device.js?v=1620373570
http/1.1
4180.0170000643
4982.0540002547
2470
2223
200
application/x-javascript
Script
https://loki.com/assets/e75603cb/jquery_plugins.js?v=1620373570
http/1.1
4180.338000413
4679.4920000248
6191
23864
200
application/x-javascript
Script
https://loki.com/assets/f9c2778/jquery.dateformat.js?v=1620373570
http/1.1
4180.6040001102
4682.9530000687
1581
1334
200
application/x-javascript
Script
https://cdnjs.cloudflare.com/ajax/libs/cleave.js/1.4.10/cleave.min.js
h2
4180.8680002578
4275.4870001227
6127
18472
200
application/javascript
Script
https://cdnjs.cloudflare.com/ajax/libs/cleave.js/1.4.10/addons/cleave-phone.ru.js
h2
4180.9500004165
4210.8610002324
5810
15250
200
application/javascript
Script
https://loki.com/assets/7e19f17f/webpush.js?v=1620373570
http/1.1
4181.0340001248
5087.7030002885
5737
5489
200
application/x-javascript
Script
https://cdnjs.cloudflare.com/ajax/libs/jquery-touch-events/2.0.0/jquery.mobile-events.min.js
h2
4181.1440000311
4276.4500002377
4621
17108
200
application/javascript
Script
https://cdnjs.cloudflare.com/ajax/libs/jquery-scrollTo/2.1.2/jquery.scrollTo.min.js
h2
4181.2230003998
4276.831000112
2333
2447
200
application/javascript
Script
https://cdnjs.cloudflare.com/ajax/libs/slick-carousel/1.6.0/slick.min.js
h2
4181.3819999807
4276.0910000652
10197
41953
200
application/javascript
Script
https://cdnjs.cloudflare.com/ajax/libs/OwlCarousel2/2.3.4/owl.carousel.min.js
h2
4181.5010001883
4274.9150004238
11329
44342
200
application/javascript
Script
https://loki.com/assets/242511e2/app.js?v=1633593277
http/1.1
4183.0710000359
5183.907000348
66237
271057
200
application/x-javascript
Script
https://loki.com/assets/242511e2/fonts/Lato-Bold.woff2
http/1.1
7578.3890001476
8186.2429999746
27433
27512
200
text/html
Font
https://loki.com/assets/242511e2/fonts/Lato-Regular.woff2
http/1.1
7578.585000243
8186.8090000935
27037
27132
200
text/html
Font
https://supportmastersclub.webim.ru/js/button.js
11781.987000257
0
0
-1
Script
https://new.go2ask.org/app/ask/js/app.js?v=1634994381236
11782.512000296
0
0
-1
Script
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)
4189.092
10.09
4201.605
71.703
5293.858
87.934
5383.278
2318.382
7703.226
197.746
7901.777
73.707
7977.836
799.824
8777.901
7.605
8787.292
6.756
8796.041
77.743
8873.8
23.524
8901.666
71.68
8973.881
218.372
9797.192
79.067
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.

Metrics

Time to Interactive — 2.9 s
The time taken for the page to become fully interactive.

Opportunities

Reduce unused CSS — Potential savings of 58 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Loki.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://loki.com/assets/242511e2/app.css?v=1631523093
59653
59328
Avoid multiple page redirects — Potential savings of 410 ms
Redirects can cause additional delays before the page can begin loading. Loki.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://loki.com/
190
https://loki.com/
150
https://loki.com/en
70
https://loki.com/en/error/restricted
0

Diagnostics

Reduce JavaScript execution time — 2.9 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://loki.com/assets/5e35c887/device.js?v=1620373570
3021.509
2302.423
0.171
https://loki.com/en/error/restricted
261.596
6.708
1.867
https://loki.com/assets/ccbb3a4a/index.js?v=1620373570
220.55
202.55
1.397
Unattributable
188.153
83.179
0.169
https://cdnjs.cloudflare.com/ajax/libs/jquery/3.3.1/jquery.min.js
181.527
170.306
1.722
https://loki.com/assets/242511e2/app.js?v=1633593277
115.941
105.895
5.058
https://loki.com/assets/242511e2/app.css?v=1631523093
87.934
0
0

Metrics

First Contentful Paint — 2.0 s
The time taken for the first image or text on the page to be rendered.
Speed Index — 5.7 s
The time taken for the page contents to be visibly populated.
Largest Contentful Paint — 2.4 s
The timing of the largest text or image that is painted.
Total Blocking Time — 660 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).

Other

Max Potential First Input Delay — 1,160 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 2.3 s
The time taken for the primary content of the page to be rendered.

Opportunities

Reduce initial server response time — Root document took 1,210 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://loki.com/en/error/restricted
1207.552

Diagnostics

Serve static assets with an efficient cache policy — 12 resources found
Loki.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) Transfer Size (Bytes)
https://loki.com/assets/242511e2/app.js?v=1633593277
0
66237
https://loki.com/assets/242511e2/app.css?v=1631523093
0
59653
https://loki.com/assets/242511e2/fonts/Lato-Bold.woff2
0
27433
https://loki.com/assets/242511e2/fonts/Lato-Regular.woff2
0
27037
https://loki.com/assets/ccbb3a4a/index.js?v=1620373570
0
19695
https://loki.com/assets/2ffce410/yii.js?v=1611313698
0
6930
https://loki.com/assets/5dd31320/style.css?v=1633701229
0
6336
https://loki.com/assets/e75603cb/jquery_plugins.js?v=1620373570
0
6191
https://loki.com/assets/7e19f17f/webpush.js?v=1620373570
0
5737
https://loki.com/assets/5e35c887/device.js?v=1620373570
0
2470
https://loki.com/assets/f9c2778/jquery.dateformat.js?v=1620373570
0
1581
https://supportmastersclub.webim.ru/button.php?location=Loki_en
0
274
Minimize main-thread work — 4.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
2878.057
Style & Layout
723.123
Parse HTML & CSS
250.289
Other
129.724
Rendering
83.271
Script Parsing & Compilation
15.123
Garbage Collection
11.945
Ensure text remains visible during webfont load
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
URL Potential Savings (Ms)
https://loki.com/assets/242511e2/fonts/Lato-Bold.woff2
607.85399982706
https://loki.com/assets/242511e2/fonts/Lato-Regular.woff2
608.22399985045
75

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of loki.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.
Heading elements appear in a sequentially-descending order
Properly order all headers and do not skip heading levels to better the navigation and readability for users of assistive technologies, like a screen reader.
No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
`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.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Form elements have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
Links have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.
`<object>` elements have `[alt]` text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Contrast

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

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Screen readers and other assistive technologies may produce poor and inaccurate output when definition lists are not properly marked up.
Definition list items are wrapped in `<dl>` elements
In order for screen readers and other assistive technologies to properly announce definition list items ('<dt>' and '<dd>'), they must be wrapped in parent a '<dl>' element.
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"]`
Loki.com may provide assistance to deaf or hearing-impaired users with captions on videos.

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

Best Practices

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

Audits

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

Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.
Avoids Application Cache
Application cache is deprecated and is no longer recommended.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
jQuery
3.3.1
Lo-Dash
4.17.11
Vue
core-js
core-js-pure@2.6.5
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
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://loki.com/
Allowed
Includes front-end JavaScript libraries with known security vulnerabilities — 9 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
3
Medium
6
High

Audits

Browser errors were logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Source Description
Chrome currently does not support the Push API in incognito mode (https://crbug.com/401439). There is deliberately no way to feature-detect this, since incognito mode needs to be undetectable by websites.
Missing source maps for large first-party JavaScript
Consider deploying source maps for added benefits such as the ability to debug while in production.
URL Map URL
https://supportmastersclub.webim.ru/js/button.js
https://loki.com/assets/242511e2/app.js?v=1633593277
https://loki.com/assets/242511e2/app.js.map
https://new.go2ask.org/app/ask/js/app.js?v=1634994381236
https://new.go2ask.org/app/ask/js/app.js.map
80

SEO

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

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.

Crawling and Indexing

robots.txt is not valid — 1 error 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
1
1
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.
73

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 loki.com. This includes details about web app manifests.

Installable

Web app manifest and service worker 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.

PWA Optimized

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

PWA Optimized

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

Manual Checks

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

2.04 seconds
First Contentful Paint (FCP)
69%
20%
11%

0.02 seconds
First Input Delay (FID)
94%
6%
0%

Simulate loading on mobile
40

Performance

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

Metrics

Cumulative Layout Shift — 0
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Opportunities

Properly size images
Images can slow down the page's load time. Loki.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Loki.com should consider lazy-loading offscreen and hidden images.
Minify JavaScript — Potential savings of 32 KiB
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Loki.com should consider minifying JS files.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://loki.com/assets/242511e2/app.js?v=1633593277
66253
16828
https://loki.com/assets/ccbb3a4a/index.js?v=1620373570
19701
6708
https://loki.com/assets/2ffce410/yii.js?v=1611313698
6930
4343
https://loki.com/assets/e75603cb/jquery_plugins.js?v=1620373570
6185
2736
https://loki.com/assets/7e19f17f/webpush.js?v=1620373570
5737
2277
Reduce unused JavaScript — Potential savings of 39 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://loki.com/assets/242511e2/app.js?v=1633593277
66253
40059
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
Enable text compression — Potential savings of 5 KiB
Text-based resources should be served with compression, such as gzip, deflate or brotli.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://loki.com/assets/7e19f17f/webpush.js?v=1620373570
5489
3945
https://loki.com/assets/5e35c887/device.js?v=1620373570
2223
1406
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 520 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://loki.com/en/error/restricted
515.003
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Loki.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://loki.com/assets/242511e2/app.js?v=1633593277
41
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.

Diagnostics

Avoids enormous network payloads — Total size was 295 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://loki.com/assets/242511e2/app.js?v=1633593277
66253
https://loki.com/assets/242511e2/app.css?v=1631523093
59645
https://cdnjs.cloudflare.com/ajax/libs/jquery/3.3.1/jquery.min.js
28653
https://loki.com/assets/242511e2/fonts/Lato-Bold.woff2
27433
https://loki.com/assets/242511e2/fonts/Lato-Regular.woff2
27037
https://loki.com/assets/ccbb3a4a/index.js?v=1620373570
19701
https://cdnjs.cloudflare.com/ajax/libs/OwlCarousel2/2.3.4/owl.carousel.min.js
11335
https://cdnjs.cloudflare.com/ajax/libs/slick-carousel/1.6.0/slick.min.js
10197
https://loki.com/assets/2ffce410/yii.js?v=1611313698
6930
https://loki.com/assets/5dd31320/style.css?v=1633701229
6336
Avoids an excessive DOM size — 37 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
37
Maximum DOM Depth
6
Maximum Child Elements
18
Avoid chaining critical requests — 17 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Loki.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.
Keep request counts low and transfer sizes small — 23 requests • 295 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
23
302132
Script
14
177899
Stylesheet
2
65981
Font
2
54470
Document
1
2493
Other
3
1015
Image
1
274
Media
0
0
Third-party
8
69316
Minimize third-party usage — Third-party code blocked the main thread for 60 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)
69042
64.316
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.
Avoid large layout shifts
Below is a list of all DOM elements that contribute to the CLS of the page.
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks — 11 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://loki.com/assets/5e35c887/device.js?v=1620373570
3630
1695
https://loki.com/assets/5e35c887/device.js?v=1620373570
5618
415
https://loki.com/assets/ccbb3a4a/index.js?v=1620373570
3269
324
https://loki.com/assets/7e19f17f/webpush.js?v=1620373570
5325
293
https://cdnjs.cloudflare.com/ajax/libs/jquery/3.3.1/jquery.min.js
3090
179
https://loki.com/assets/242511e2/app.css?v=1631523093
2580
107
Unattributable
676
93
https://loki.com/en/error/restricted
1470
83
https://loki.com/en/error/restricted
1685
74
https://loki.com/en/error/restricted
1553
70
https://loki.com/en/error/restricted
1623
62
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 loki.com on mobile screens.

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

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://loki.com/
http/1.1
0
199.36600001529
234
0
301
text/html
https://loki.com/
http/1.1
199.92400001502
709.91500001401
418
0
302
text/html
https://loki.com/en
http/1.1
710.447999998
1221.0389999673
363
0
302
text/html
https://loki.com/en/error/restricted
http/1.1
1221.596999967
1735.6049999944
2493
6142
200
text/html
Document
https://loki.com/assets/5dd31320/style.css?v=1633701229
http/1.1
1768.6680000043
2278.032000002
6336
31752
200
text/css
Stylesheet
https://loki.com/assets/242511e2/app.css?v=1631523093
http/1.1
1771.5449999669
2505.5139999604
59645
303204
200
text/css
Stylesheet
https://supportmastersclub.webim.ru/button.php?location=Loki_en
http/1.1
1799.3760000099
2500.5709999823
274
43
200
image/gif
Image
https://cdnjs.cloudflare.com/ajax/libs/jquery/3.3.1/jquery.min.js
h2
1775.3909999738
1812.3699999996
28653
86927
200
application/javascript
Script
https://loki.com/assets/2ffce410/yii.js?v=1611313698
http/1.1
1779.6690000105
2284.5129999914
6930
20934
200
application/x-javascript
Script
https://loki.com/assets/ccbb3a4a/index.js?v=1620373570
http/1.1
1783.3150000079
2392.0700000017
19701
58348
200
application/x-javascript
Script
https://loki.com/assets/5e35c887/device.js?v=1620373570
http/1.1
1783.4469999652
2582.1609999985
2470
2223
200
application/x-javascript
Script
https://loki.com/assets/e75603cb/jquery_plugins.js?v=1620373570
http/1.1
1790.0960000115
2272.8379999753
6185
23864
200
application/x-javascript
Script
https://loki.com/assets/f9c2778/jquery.dateformat.js?v=1620373570
http/1.1
1790.2340000146
2308.3259999985
1581
1334
200
application/x-javascript
Script
https://cdnjs.cloudflare.com/ajax/libs/cleave.js/1.4.10/cleave.min.js
h2
1790.3330000117
1837.6369999605
6129
18472
200
application/javascript
Script
https://cdnjs.cloudflare.com/ajax/libs/cleave.js/1.4.10/addons/cleave-phone.ru.js
h2
1793.6059999629
1835.78699996
5817
15250
200
application/javascript
Script
https://loki.com/assets/7e19f17f/webpush.js?v=1620373570
http/1.1
1797.1590000088
2607.1699999738
5737
5489
200
application/x-javascript
Script
https://cdnjs.cloudflare.com/ajax/libs/jquery-touch-events/2.0.0/jquery.mobile-events.min.js
h2
1797.9809999815
1837.8839999787
4587
17108
200
application/javascript
Script
https://cdnjs.cloudflare.com/ajax/libs/jquery-scrollTo/2.1.2/jquery.scrollTo.min.js
h2
1798.9149999921
1834.5100000151
2324
2447
200
application/javascript
Script
https://cdnjs.cloudflare.com/ajax/libs/slick-carousel/1.6.0/slick.min.js
h2
1799.0139999893
1836.2649999908
10197
41953
200
application/javascript
Script
https://cdnjs.cloudflare.com/ajax/libs/OwlCarousel2/2.3.4/owl.carousel.min.js
h2
1799.1620000103
1841.5139999706
11335
44342
200
application/javascript
Script
https://loki.com/assets/242511e2/app.js?v=1633593277
http/1.1
1799.2709999671
2487.8019999596
66253
271057
200
application/x-javascript
Script
https://loki.com/assets/242511e2/fonts/Lato-Bold.woff2
http/1.1
2612.667999987
3221.8269999721
27433
27512
200
text/html
Font
https://loki.com/assets/242511e2/fonts/Lato-Regular.woff2
http/1.1
3468.2369999937
4077.9449999682
27037
27132
200
text/html
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)
1830.197
20.705
1854.596
17.447
1956.585
11.476
1974.115
23.147
2002.959
10.205
2596.821
26.651
2623.487
30.818
2654.357
44.859
2699.255
36.925
2737.925
847.407
3585.365
11.416
3597.087
73.296
3670.409
9.653
3680.169
207.667
3890.503
8.904
3899.423
9.241
3970.967
81.105
4167.946
5.689
4745.348
5.574
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.

Metrics

First Contentful Paint — 2.1 s
The time taken for the first image or text on the page to be rendered.
Time to Interactive — 5.9 s
The time taken for the page to become fully interactive.

Other

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

Opportunities

Eliminate render-blocking resources — Potential savings of 530 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Loki.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://loki.com/assets/5dd31320/style.css?v=1633701229
6336
180
https://loki.com/assets/242511e2/app.css?v=1631523093
59645
480
Minify CSS — Potential savings of 10 KiB
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Loki.com should consider minifying CSS files.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://loki.com/assets/242511e2/app.css?v=1631523093
59645
10743
Reduce unused CSS — Potential savings of 58 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Loki.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://loki.com/assets/242511e2/app.css?v=1631523093
59645
59372

Metrics

Speed Index — 6.0 s
The time taken for the page contents to be visibly populated.
Largest Contentful Paint — 5.4 s
The timing of the largest text or image that is painted.
Total Blocking Time — 2,710 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).

Other

Max Potential First Input Delay — 1,700 ms
Users could experience a delay when interacting with the page.

Opportunities

Avoid multiple page redirects — Potential savings of 1,290 ms
Redirects can cause additional delays before the page can begin loading. Loki.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://loki.com/
630
https://loki.com/
480
https://loki.com/en
180
https://loki.com/en/error/restricted
0

Diagnostics

Serve static assets with an efficient cache policy — 12 resources found
Loki.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) Transfer Size (Bytes)
https://loki.com/assets/242511e2/app.js?v=1633593277
0
66253
https://loki.com/assets/242511e2/app.css?v=1631523093
0
59645
https://loki.com/assets/242511e2/fonts/Lato-Bold.woff2
0
27433
https://loki.com/assets/242511e2/fonts/Lato-Regular.woff2
0
27037
https://loki.com/assets/ccbb3a4a/index.js?v=1620373570
0
19701
https://loki.com/assets/2ffce410/yii.js?v=1611313698
0
6930
https://loki.com/assets/5dd31320/style.css?v=1633701229
0
6336
https://loki.com/assets/e75603cb/jquery_plugins.js?v=1620373570
0
6185
https://loki.com/assets/7e19f17f/webpush.js?v=1620373570
0
5737
https://loki.com/assets/5e35c887/device.js?v=1620373570
0
2470
https://loki.com/assets/f9c2778/jquery.dateformat.js?v=1620373570
0
1581
https://supportmastersclub.webim.ru/button.php?location=Loki_en
0
274
Reduce JavaScript execution time — 4.3 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://loki.com/assets/5e35c887/device.js?v=1620373570
4167.004
3471.86
0.772
https://loki.com/en/error/restricted
617.384
25.084
13.124
Unattributable
418.116
33.532
0.636
https://loki.com/assets/ccbb3a4a/index.js?v=1620373570
336.296
322.796
8.712
https://loki.com/assets/242511e2/app.js?v=1633593277
227.296
190.956
33.52
https://cdnjs.cloudflare.com/ajax/libs/jquery/3.3.1/jquery.min.js
214.436
176.648
17.896
https://loki.com/assets/242511e2/app.css?v=1631523093
106.604
0
0
Minimize main-thread work — 6.2 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
4264.38
Style & Layout
782.844
Other
504.884
Parse HTML & CSS
390.26
Rendering
123.808
Script Parsing & Compilation
91.056
Ensure text remains visible during webfont load
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
URL Potential Savings (Ms)
https://loki.com/assets/242511e2/fonts/Lato-Bold.woff2
609.15899998508
https://loki.com/assets/242511e2/fonts/Lato-Regular.woff2
609.70799997449
73

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of loki.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.
Heading elements appear in a sequentially-descending order
Properly order all headers and do not skip heading levels to better the navigation and readability for users of assistive technologies, like a screen reader.
No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
`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.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Form elements have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
Links have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.
`<object>` elements have `[alt]` text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Contrast

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

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Screen readers and other assistive technologies may produce poor and inaccurate output when definition lists are not properly marked up.
Definition list items are wrapped in `<dl>` elements
In order for screen readers and other assistive technologies to properly announce definition list items ('<dt>' and '<dd>'), they must be wrapped in parent a '<dl>' element.
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"]`
Loki.com may provide assistance to deaf or hearing-impaired users with captions on videos.

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

Best Practices

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

Audits

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

Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.
Avoids Application Cache
Application cache is deprecated and is no longer recommended.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
jQuery
3.3.1
Lo-Dash
4.17.11
Vue
core-js
core-js-pure@2.6.5
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
URL Map URL
https://loki.com/assets/242511e2/app.js?v=1633593277
https://loki.com/assets/242511e2/app.js.map
https://new.go2ask.org/app/ask/js/app.js?v=1634994431085
https://new.go2ask.org/app/ask/js/app.js.map
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://loki.com/
Allowed
Includes front-end JavaScript libraries with known security vulnerabilities — 9 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
3
Medium
6
High

Audits

Browser errors were logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Source Description
Chrome currently does not support the Push API in incognito mode (https://crbug.com/401439). There is deliberately no way to feature-detect this, since incognito mode needs to be undetectable by websites.
83

SEO

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

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.

Crawling and Indexing

robots.txt is not valid — 1 error 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
1
1
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.
75

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 loki.com. This includes details about web app manifests.

Installable

Web app manifest and service worker 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.

PWA Optimized

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

PWA Optimized

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

Manual Checks

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

Server Location

Server IP Address: 134.122.85.178
Continent: Europe
Country: Germany
Germany Flag
Region: Hesse
City: Frankfurt am Main
Longitude: 8.6843
Latitude: 50.1188
Currencies: EUR
Languages: German

Web Hosting Provider

Name IP Address
DigitalOcean, LLC
Registration

Domain Registrant

Private Registration: No
Name: Martin Grech
Organization: Cyberplay Management Ltd
Country: MT
City: Valletta
State:
Post Code: VLT1450
Email: martin.grech@cpm.com.mt
Phone: +356.99102806
Note: Registration information is derived from various sources and may be inaccurate.

Domain Registrar

Name IP Address
GANDI SAS 146.75.77.103
Security

Visitor Safety

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

SSL/TLS Certificate

Issued To: loki.com
Issued By: R3
Valid From: 2nd September, 2021
Valid To: 1st December, 2021
Subject: CN = loki.com
Hash: 9d0802a7
Issuer: CN = R3
O = Let's Encrypt
S = US
Version: 2
Serial Number: 0x041ED4F27EC74030E472952DB50539110743
Serial Number (Hex): 041ED4F27EC74030E472952DB50539110743
Valid From: 2nd September, 2024
Valid To: 1st December, 2024
Signature Algorithm (Short Name): RSA-SHA256
Signature Algorithm (Long Name): sha256WithRSAEncryption
Authority Key Identifier: keyid:14:2E:B3:17:B7:58:56:CB:AE:50:09:40:E6:1F:AF:9D:8B:14:C2:C6
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://r3.o.lencr.org
CA Issuers - URI:http://r3.i.lencr.org/

SCT List: Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 44:94:65:2E:B0:EE:CE:AF:C4:40:07:D8:A8:FE:28:C0:
DA:E6:82:BE:D8:CB:31:B5:3F:D3:33:96:B5:B6:81:A8
Timestamp : Sep 2 15:26:28.757 2021 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:46:02:21:00:EC:C4:A7:CB:C8:8D:92:E3:8F:22:AC:
C6:DD:4C:E8:53:5B:C5:9B:3D:A8:72:8F:38:DC:C8:B0:
4A:FA:EA:06:50:02:21:00:81:C2:E3:3B:3D:FD:41:A3:
12:D5:2A:10:C7:CC:A2:DF:84:09:7A:C6:AE:B2:1D:0D:
33:BF:5D:5B:B8:1C:F0:8D
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : F6:5C:94:2F:D1:77:30:22:14:54:18:08:30:94:56:8E:
E3:4D:13:19:33:BF:DF:0C:2F:20:0B:CC:4E:F1:64:E3
Timestamp : Sep 2 15:26:28.736 2021 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:20:10:74:D4:AC:DA:0F:1B:1C:B6:0C:F4:AD:
E8:BD:61:26:4C:C3:E6:36:F9:4F:32:D1:C1:10:55:43:
10:A8:40:C7:02:21:00:8F:7F:4D:BA:8B:4D:9F:89:CD:
C6:74:DF:AF:6D:95:46:CD:7F:95:1C:CC:F9:AE:10:18:
3D:CC:DE:75:A4:D7:0D
Key Usage: Digital Signature, Key Encipherment
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:www.loki.com
DNS:loki.com
Technical

DNS Lookup

A Records

Host IP Address Class TTL
loki.com. 134.122.85.178 IN 1800

NS Records

Host Nameserver Class TTL
loki.com. a.dns.gandi.net. IN 10800
loki.com. b.dns.gandi.net. IN 10800
loki.com. c.dns.gandi.net. IN 10800

MX Records

Priority Host Server Class TTL
0 loki.com. loki-com.mail.protection.outlook.com. IN 3600

SOA Records

Domain Name Primary NS Responsible Email TTL
loki.com. a.dns.gandi.net. hostmaster.gandi.net. 10800

TXT Records

Host Value Class TTL
loki.com. v=spf1 IN 3600

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Server: nginx
Date: 23rd October, 2021
Content-Type: text/html; charset=UTF-8
Cache-Control: no-store, no-cache, must-revalidate
Expires: 19th November, 1981
Connection: keep-alive
Pragma: no-cache
Set-Cookie: *

Whois Lookup

Created: 16th September, 1992
Changed: 28th July, 2021
Expires: 15th September, 2022
Registrar: GANDI SAS
Status: clientTransferProhibited
Nameservers: a.dns.gandi.net
b.dns.gandi.net
c.dns.gandi.net
Owner Name: Martin Grech
Owner Organization: Cyberplay Management Ltd
Owner Street: 9, Level 2, Britannia House Old Bakery Street
Owner Post Code: VLT1450
Owner City: Valletta
Owner Country: MT
Owner Phone: +356.99102806
Owner Email: martin.grech@cpm.com.mt
Admin Name: Martin Grech
Admin Organization: Cyberplay Management Ltd
Admin Street: 9, Level 2, Britannia House Old Bakery Street
Admin Post Code: VLT1450
Admin City: Valletta
Admin Country: MT
Admin Phone: +356.99102806
Admin Email: martin.grech@cpm.com.mt
Tech Name: Stefan Grech
Tech Organization: Cyber Play Management
Tech Street: Business Box 115A Floor 5 Valley Road
Tech Post Code: BKR 9024
Tech City: Imsida
Tech Country: MT
Tech Phone: +356.99203084
Tech Email: Stefan.grech@cpm.com.mt
Full Whois: Domain Name: loki.com
Registry Domain ID: 1610622_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.gandi.net
Registrar URL: http://www.gandi.net
Updated Date: 2021-07-28T15:02:27Z
Creation Date: 1992-09-16T04:00:00Z
Registrar Registration Expiration Date: 2022-09-15T04:00:00Z
Registrar: GANDI SAS
Registrar IANA ID: 81
Registrar Abuse Contact Email: abuse@support.gandi.net
Registrar Abuse Contact Phone: +33.170377661
Reseller: Cyber Play Management Ltd.
Domain Status: clientTransferProhibited http://www.icann.org/epp#clientTransferProhibited
Domain Status:
Domain Status:
Domain Status:
Domain Status:
Registry Registrant ID:
Registrant Name: Martin Grech
Registrant Organization: Cyberplay Management Ltd
Registrant Street: 9, Level 2, Britannia House Old Bakery Street
Registrant City: Valletta
Registrant State/Province:
Registrant Postal Code: VLT1450
Registrant Country: MT
Registrant Phone: +356.99102806
Registrant Phone Ext:
Registrant Fax:
Registrant Fax Ext:
Registrant Email: martin.grech@cpm.com.mt
Registry Admin ID:
Admin Name: Martin Grech
Admin Organization: Cyberplay Management Ltd
Admin Street: 9, Level 2, Britannia House Old Bakery Street
Admin City: Valletta
Admin State/Province:
Admin Postal Code: VLT1450
Admin Country: MT
Admin Phone: +356.99102806
Admin Phone Ext:
Admin Fax:
Admin Fax Ext:
Admin Email: martin.grech@cpm.com.mt
Registry Tech ID:
Tech Name: Stefan Grech
Tech Organization: Cyber Play Management
Tech Street: Business Box 115A Floor 5 Valley Road
BKR 9024
Tech City: Imsida
Tech State/Province:
Tech Postal Code: BKR 9024
Tech Country: MT
Tech Phone: +356.99203084
Tech Phone Ext:
Tech Fax:
Tech Fax Ext:
Tech Email: Stefan.grech@cpm.com.mt
Name Server: A.DNS.GANDI.NET
Name Server: B.DNS.GANDI.NET
Name Server: C.DNS.GANDI.NET
Name Server:
Name Server:
Name Server:
Name Server:
Name Server:
Name Server:
Name Server:
DNSSEC: Unsigned
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/
>>> Last update of WHOIS database: 2021-10-23T13:05:53Z <<<

For more information on Whois status codes, please visit
https://www.icann.org/epp

Reseller Email:
Reseller URL:

Personal data access and use are governed by French law, any use for the purpose of unsolicited mass commercial advertising as well as any mass or automated inquiries (for any intent other than the registration or modification of a domain name) are strictly forbidden. Copy of whole or part of our database without Gandi's endorsement is strictly forbidden.
A dispute over the ownership of a domain name may be subject to the alternate procedure established by the Registry in question or brought before the courts.
For additional information, please contact us via the following form:
https://www.gandi.net/support/contacter/mail/

Nameservers

Name IP Address
a.dns.gandi.net 173.246.98.1
b.dns.gandi.net 213.167.229.1
c.dns.gandi.net 217.70.179.1
Related

Subdomains

Similar Sites

Domain Valuation Snoop Score
0/5
0/5
0/5
$670 USD 1/5
$131,931 USD 4/5

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Domain Valuation Snoop Score
0/5
0/5
0/5
0/5

Sites hosted on the same IP address