koora-lives.tv

koora-lives.tv is SSL secured

Free website and domain report on koora-lives.tv

Last Updated: 14th December, 2022 Update Now
Overview

Snoop Summary for koora-lives.tv

This is a free and comprehensive report about koora-lives.tv. The domain koora-lives.tv is currently hosted on a server located in United States with the IP address 104.21.73.204, where USD is the local currency and the local language is English. Koora-lives.tv is expected to earn an estimated $91 USD per day from advertising revenue. The sale of koora-lives.tv would possibly be worth $66,799 USD. This figure is based on the daily revenue potential of the website over a 24 month period. Koora-lives.tv is wildly popular with an estimated 21,635 daily unique visitors. This report was last updated 14th December, 2022.

About koora-lives.tv

Site Preview: koora-lives.tv koora-lives.tv
Title: koora live English
Description: koora live | live tv , kooora live today s matches , watch live matches on koora life or koora4live
Keywords and Tags:
Related Terms: hd matches, hi koora, koora live 96, koora live online 96, koora live tv, koora live.pp.ua, koora online 96, m koora live tv, matches on plane, tsa matches
Fav Icon:
Age:
Domain Created:
Domain Updated:
Domain Expires:
Review

Snoop Score

2/5

Valuation

$66,799 USD
Note: All valuation figures are estimates.

Popularity

High
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 34,503
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: 21,635
Monthly Visitors: 658,501
Yearly Visitors: 7,896,775
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $91 USD
Monthly Revenue: $2,785 USD
Yearly Revenue: $33,395 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: koora-lives.tv 14
Domain Name: koora-lives 11
Extension (TLD): tv 2

Page Speed Analysis

Average Load Time:
Load Time Comparison:

PageSpeed Insights

Avg. (All Categories) 81
Performance 100
Accessibility 91
Best Practices 83
SEO 100
PWA 33
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://koora-lives.tv/
Updated: 14th December, 2022

1.82 seconds
First Contentful Paint (FCP)
74%
18%
8%

0.01 seconds
First Input Delay (FID)
98%
2%
0%

Simulate loading on desktop
100

Performance

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

Metrics

First Contentful Paint — 0.4 s
The time taken for the first image or text on the page to be rendered.
Time to Interactive — 0.4 s
The time taken for the page to become fully interactive.
Speed Index — 0.6 s
The time taken for the page contents to be visibly populated.
Total Blocking Time — 0 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).
Largest Contentful Paint — 0.5 s
The timing of the largest text or image that is painted.
Cumulative Layout Shift — 0.024
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Audits

Max Potential First Input Delay — 20 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 0.4 s
The time taken for the primary content of the page to be rendered.
Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://koora-lives.tv/
http/1.1
0
40.96200002823
731
0
301
text/plain
https://koora-lives.tv/
h2
41.300000040792
259.35800001025
13650
51934
200
text/html
Document
https://koora-lives.tv/assets/js/jquery.min.js?t=1671047306
h2
265.72999998461
337.87300006952
33738
89402
200
application/javascript
Script
https://koora-lives.tv/uploads/logo/yalla-shoot.png
h2
265.92600008007
316.57200003974
3837
2772
200
image/png
Image
https://koora-lives.tv/assets/themes/yalla-shoot/js/lazyload.js
h2
317.93700007256
364.19700004626
3702
7249
200
application/javascript
Script
https://www.googletagmanager.com/gtag/js?id=UA-238395345-1
h2
344.05900002457
352.96200006269
44324
111592
200
application/javascript
Script
data
358.31000003964
358.39499998838
0
451
200
image/svg+xml
Image
data
359.53300003894
359.61600008886
0
944
200
image/svg+xml
Image
data
360.71300006006
360.76800001319
0
248
200
image/svg+xml
Image
data
361.67500005104
361.73600004986
0
460
200
image/svg+xml
Image
https://koora-lives.tv/assets/fonts/Montserrat-SemiBold.ttf
h2
363.30199998338
430.28199998662
193352
192268
200
application/octet-stream
Font
https://web-api.yalla-kora.tv/uploads/team/1612059317.png
h2
373.20200004615
474.3980000494
2484
1620
200
image/png
Image
https://web-api.yalla-kora.tv/uploads/team/1670707143.png
h2
373.37899999693
535.43699998409
6352
5489
200
image/png
Image
data
377.32299999334
377.42100004107
0
500
200
image/svg+xml
Image
https://www.google-analytics.com/analytics.js
h2
423.39700006414
429.78900007438
20664
50230
200
text/javascript
Script
https://www.google-analytics.com/j/collect?v=1&_v=j98&a=1713660536&t=pageview&_s=1&dl=https%3A%2F%2Fkoora-lives.tv%2F&ul=en-us&de=UTF-8&dt=koora%20live%20English&sd=24-bit&sr=800x600&vp=1350x940&je=0&_u=YEBAAUABAAAAACAAI~&jid=621354146&gjid=1588629050&cid=1187601927.1671047358&tid=UA-238395345-1&_gid=477348846.1671047358&_r=1&gtm=2oubu0&z=2117297499
h2
457.37200009171
460.77200002037
612
1
200
text/plain
XHR
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)
263.217
8.402
344.974
10.015
356.827
17.727
376.374
7.441
387.486
20.043
407.779
5.629
417.297
7.052
434.842
23.647
1405.138
21.105
2424.146
20.506
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Other

Eliminate render-blocking resources — Potential savings of 80 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Koora-lives.tv 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://koora-lives.tv/assets/js/jquery.min.js?t=1671047306
33738
80
Properly size images — Potential savings of 4 KiB
Images can slow down the page's load time. Koora-lives.tv should consider serving more appropriate-sized images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://web-api.yalla-kora.tv/uploads/team/1670707143.png
5489
4489
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Koora-lives.tv should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Koora-lives.tv should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Koora-lives.tv should consider minifying JS files.
Reduce unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Koora-lives.tv should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Reduce unused JavaScript — Potential savings of 45 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://koora-lives.tv/assets/js/jquery.min.js?t=1671047306
33738
23893
https://www.googletagmanager.com/gtag/js?id=UA-238395345-1
44324
21930
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.
Initial server response time was short — Root document took 220 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://koora-lives.tv/
219.052
Avoid multiple page redirects — Potential savings of 190 ms
Redirects can cause additional delays before the page can begin loading. Koora-lives.tv should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://koora-lives.tv/
190
https://koora-lives.tv/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Koora-lives.tv 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
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.
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
Avoids enormous network payloads — Total size was 316 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://koora-lives.tv/assets/fonts/Montserrat-SemiBold.ttf
193352
https://www.googletagmanager.com/gtag/js?id=UA-238395345-1
44324
https://koora-lives.tv/assets/js/jquery.min.js?t=1671047306
33738
https://www.google-analytics.com/analytics.js
20664
https://koora-lives.tv/
13650
https://web-api.yalla-kora.tv/uploads/team/1670707143.png
6352
https://koora-lives.tv/uploads/logo/yalla-shoot.png
3837
https://koora-lives.tv/assets/themes/yalla-shoot/js/lazyload.js
3702
https://web-api.yalla-kora.tv/uploads/team/1612059317.png
2484
http://koora-lives.tv/
731
Avoids an excessive DOM size — 173 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
173
Maximum DOM Depth
11
Maximum Child Elements
12
Avoid chaining critical requests — 3 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Koora-lives.tv should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
JavaScript execution time — 0.1 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://koora-lives.tv/
108.374
57.688
1.943
Minimizes main-thread work — 0.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
95.657
Other
33.163
Style & Layout
30.153
Rendering
8.257
Script Parsing & Compilation
5.849
Parse HTML & CSS
5.4
Garbage Collection
2.612
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 — 11 requests • 316 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
11
323446
Font
1
193352
Script
4
102428
Document
1
13650
Image
3
12673
Other
2
1343
Stylesheet
0
0
Media
0
0
Third-party
5
74436
Minimize third-party usage — Third-party code blocked the main thread for 0 ms
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Third-Party Transfer Size (Bytes) Main-Thread Blocking Time (Ms)
44324
0
21276
0
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.
Avoid large layout shifts — 5 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.0080778998414701
0.0067385577502744
0.0035458658182785
0.0034127777019944
0.0019723110016328
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
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 koora-lives.tv on mobile screens.
Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.

Budgets

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

Other

Serve static assets with an efficient cache policy — 7 resources found
Koora-lives.tv 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://www.google-analytics.com/analytics.js
7200000
20664
https://koora-lives.tv/assets/fonts/Montserrat-SemiBold.ttf
2592000000
193352
https://koora-lives.tv/assets/js/jquery.min.js?t=1671047306
2592000000
33738
https://web-api.yalla-kora.tv/uploads/team/1670707143.png
2592000000
6352
https://koora-lives.tv/uploads/logo/yalla-shoot.png
2592000000
3837
https://koora-lives.tv/assets/themes/yalla-shoot/js/lazyload.js
2592000000
3702
https://web-api.yalla-kora.tv/uploads/team/1612059317.png
2592000000
2484

Other

Image elements do not have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
URL
https://koora-lives.tv/uploads/logo/yalla-shoot.png
91

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of koora-lives.tv. 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.
`<object>` elements have alternate text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Contrast

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

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Screen readers and other assistive technologies may produce poor and inaccurate output when definition lists are not properly marked up.
Definition list items are wrapped in `<dl>` elements
In order for screen readers and other assistive technologies to properly announce definition list items ('<dt>' and '<dd>'), they must be wrapped in parent a '<dl>' element.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that '<td>' cells using the headers attribute only refer to other cells in the same table, to improve screen reader user experience.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that table headers refer to some set of cells, to improve screen reader user experience.

Internationalization and localization

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

Best practices

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

Audio and video

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

Names and labels

Links do not have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.

Tables and lists

Lists do not contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Use proper list structure to aid screen readers and other assistive technologies.
Failing Elements
List items (`<li>`) are not 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.
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.
83

Best Practices

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

Audits

Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
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
script-src directive is missing. This can allow the execution of unsafe scripts.
script-src
High
Missing object-src allows the injection of plugins that execute unsafe scripts. Consider setting object-src to 'none' if you can.
object-src
High

Audits

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

Audits

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

Audits

Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
jQuery
3.1.0
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

Does not use HTTPS — 1 insecure request found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL Request Resolution
http://koora-lives.tv/
Allowed
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
3
Medium
100

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for koora-lives.tv. 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 koora-lives.tv on mobile screens.
Document uses legible font sizes
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.
Tap targets are sized appropriately
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.

Content Best Practices

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

Crawling and Indexing

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

Manual Checks

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

PWA

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

PWA Optimized

Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of koora-lives.tv on mobile screens.
Provides a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.

Installable

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

PWA Optimized

Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Does not set a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Manifest doesn't have a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

Manual Checks

Site works cross-browser
Ensure that the Progressive Web App works correctly across every major browser.
Page transitions don't feel like they block on the network
Users perceive apps with responsive, snappy transitions as higher peforming and ensures a great user experience, even on a slow network.
Each page has a URL
Ensure that all pages are deep linkable via URL. They should also be unique for the purpose of shareability on social media.
Avg. (All Categories) 78
Performance 94
Accessibility 91
Best Practices 67
SEO 100
PWA 40
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://koora-lives.tv/
Updated: 14th December, 2022

1.94 seconds
First Contentful Paint (FCP)
73%
16%
11%

0.02 seconds
First Input Delay (FID)
94%
4%
2%

Simulate loading on mobile
94

Performance

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

Metrics

First Contentful Paint — 1.5 s
The time taken for the first image or text on the page to be rendered.
Speed Index — 2.4 s
The time taken for the page contents to be visibly populated.
Largest Contentful Paint — 1.7 s
The timing of the largest text or image that is painted.
Cumulative Layout Shift — 0.032
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Audits

First Meaningful Paint — 1.5 s
The time taken for the primary content of the page to be rendered.
Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://koora-lives.tv/
http/1.1
0
70.905000087805
740
0
301
text/plain
https://koora-lives.tv/
h2
71.525000035763
686.57600006554
13658
51934
200
text/html
Document
https://koora-lives.tv/assets/js/jquery.min.js?t=1671047366
h2
699.65399999637
787.85500000231
33735
89402
200
application/javascript
Script
https://koora-lives.tv/uploads/logo/yalla-shoot.png
h2
701.12400001381
791.63300001528
3847
2772
200
image/png
Image
https://koora-lives.tv/assets/themes/yalla-shoot/js/lazyload.js
h2
794.15900004096
892.65600009821
3696
7249
200
application/javascript
Script
https://www.googletagmanager.com/gtag/js?id=UA-238395345-1
h2
799.01900002733
813.71100002434
44369
111590
200
application/javascript
Script
data
821.83600007556
821.97000004817
0
451
200
image/svg+xml
Image
data
824.12400003523
824.2109999992
0
944
200
image/svg+xml
Image
data
825.33400005195
825.40600001812
0
248
200
image/svg+xml
Image
data
826.58100000117
826.65500009898
0
460
200
image/svg+xml
Image
https://koora-lives.tv/assets/fonts/Montserrat-SemiBold.ttf
h2
832.36200001556
914.46700005326
193356
192268
200
application/octet-stream
Font
https://web-api.yalla-kora.tv/uploads/team/1612059317.png
h2
847.62100002263
956.75500005018
2470
1620
200
image/png
Image
https://web-api.yalla-kora.tv/uploads/team/1670707143.png
h2
847.78200008441
931.11600005068
6346
5489
200
image/png
Image
data
853.66600006819
853.75700006261
0
500
200
image/svg+xml
Image
https://www.google-analytics.com/analytics.js
h2
996.50400003884
1008.4200000856
20663
50230
200
text/javascript
Script
https://www.google-analytics.com/j/collect?v=1&_v=j98&a=1690244439&t=pageview&_s=1&dl=https%3A%2F%2Fkoora-lives.tv%2F&ul=en-us&de=UTF-8&dt=koora%20live%20English&sd=24-bit&sr=360x640&vp=360x640&je=0&_u=YEBAAUABAAAAACAAI~&jid=779084047&gjid=174019201&cid=18772653.1671047377&tid=UA-238395345-1&_gid=1236013872.1671047377&_r=1&gtm=2oubu0&z=510326619
h2
1047.8989999974
1055.269000004
612
1
200
text/plain
XHR
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)
691.657
15.053
798.401
18.046
819.587
29.921
853.376
22.75
878.372
12.88
899.689
34.934
934.642
20.336
955.023
7.728
962.762
5.006
967.793
14.673
983.755
9.358
994.448
6.869
1023.177
25.721
1932.445
47.109
2980.182
33.728
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Other

Properly size images
Images can slow down the page's load time. Koora-lives.tv should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Koora-lives.tv should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Koora-lives.tv should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Koora-lives.tv should consider minifying JS files.
Reduce unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Koora-lives.tv should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
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.
Avoid multiple page redirects — Potential savings of 630 ms
Redirects can cause additional delays before the page can begin loading. Koora-lives.tv should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://koora-lives.tv/
630
https://koora-lives.tv/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Koora-lives.tv 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
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.
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
Avoids enormous network payloads — Total size was 316 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://koora-lives.tv/assets/fonts/Montserrat-SemiBold.ttf
193356
https://www.googletagmanager.com/gtag/js?id=UA-238395345-1
44369
https://koora-lives.tv/assets/js/jquery.min.js?t=1671047366
33735
https://www.google-analytics.com/analytics.js
20663
https://koora-lives.tv/
13658
https://web-api.yalla-kora.tv/uploads/team/1670707143.png
6346
https://koora-lives.tv/uploads/logo/yalla-shoot.png
3847
https://koora-lives.tv/assets/themes/yalla-shoot/js/lazyload.js
3696
https://web-api.yalla-kora.tv/uploads/team/1612059317.png
2470
http://koora-lives.tv/
740
Avoids an excessive DOM size — 173 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
173
Maximum DOM Depth
11
Maximum Child Elements
12
Avoid chaining critical requests — 3 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Koora-lives.tv 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.7 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://koora-lives.tv/
941.1
432.152
11.344
https://www.googletagmanager.com/gtag/js?id=UA-238395345-1
127.828
106.412
17.688
Unattributable
118.864
6.644
0
https://www.google-analytics.com/analytics.js
108.032
98.212
4.232
https://koora-lives.tv/assets/js/jquery.min.js?t=1671047366
73.18
60.136
9.468
Minimizes main-thread work — 1.4 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Script Evaluation
711.64399999999
Style & Layout
255.532
Other
234.664
Rendering
80.636
Script Parsing & Compilation
44.472
Parse HTML & CSS
31.656
Garbage Collection
21.368
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 — 11 requests • 316 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
11
323492
Font
1
193356
Script
4
102463
Document
1
13658
Image
3
12663
Other
2
1352
Stylesheet
0
0
Media
0
0
Third-party
5
74460
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)
21275
45.164
44369
12.916
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 — 5 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.010693530394142
0.010555603837334
0.0048133553498244
0.0032652001203487
0.0031244587358509
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 — 8 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://koora-lives.tv/
1461
188
https://koora-lives.tv/
1321
140
https://koora-lives.tv/
1649
135
https://www.google-analytics.com/analytics.js
3598
103
https://www.googletagmanager.com/gtag/js?id=UA-238395345-1
2550
81
https://koora-lives.tv/assets/js/jquery.min.js?t=1671047366
3960
72
https://koora-lives.tv/
1110
60
https://koora-lives.tv/
1189
60
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 koora-lives.tv on mobile screens.
Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.

Budgets

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

Metrics

Time to Interactive — 3.8 s
The time taken for the page to become fully interactive.
Total Blocking Time — 210 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).

Audits

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

Other

Eliminate render-blocking resources — Potential savings of 290 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Koora-lives.tv 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://koora-lives.tv/assets/js/jquery.min.js?t=1671047366
33735
300
Reduce unused JavaScript — Potential savings of 45 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://koora-lives.tv/assets/js/jquery.min.js?t=1671047366
33735
23891
https://www.googletagmanager.com/gtag/js?id=UA-238395345-1
44369
21953
Serve static assets with an efficient cache policy — 7 resources found
Koora-lives.tv 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://www.google-analytics.com/analytics.js
7200000
20663
https://koora-lives.tv/assets/fonts/Montserrat-SemiBold.ttf
2592000000
193356
https://koora-lives.tv/assets/js/jquery.min.js?t=1671047366
2592000000
33735
https://web-api.yalla-kora.tv/uploads/team/1670707143.png
2592000000
6346
https://koora-lives.tv/uploads/logo/yalla-shoot.png
2592000000
3847
https://koora-lives.tv/assets/themes/yalla-shoot/js/lazyload.js
2592000000
3696
https://web-api.yalla-kora.tv/uploads/team/1612059317.png
2592000000
2470
First Contentful Paint (3G) — 2892 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.

Other

Reduce initial server response time — Root document took 620 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://koora-lives.tv/
616.043
91

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of koora-lives.tv. 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.
`<object>` elements have alternate text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Contrast

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

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Screen readers and other assistive technologies may produce poor and inaccurate output when definition lists are not properly marked up.
Definition list items are wrapped in `<dl>` elements
In order for screen readers and other assistive technologies to properly announce definition list items ('<dt>' and '<dd>'), they must be wrapped in parent a '<dl>' element.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that '<td>' cells using the headers attribute only refer to other cells in the same table, to improve screen reader user experience.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that table headers refer to some set of cells, to improve screen reader user experience.

Internationalization and localization

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

Best practices

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

Audio and video

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

Names and labels

Links do not have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.

Tables and lists

Lists do not contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Use proper list structure to aid screen readers and other assistive technologies.
Failing Elements
List items (`<li>`) are not 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.
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.
67

Best Practices

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

Audits

Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
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
script-src directive is missing. This can allow the execution of unsafe scripts.
script-src
High
Missing object-src allows the injection of plugins that execute unsafe scripts. Consider setting object-src to 'none' if you can.
object-src
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.
Fonts with `font-display: optional` are preloaded
It is recommended that optional fonts are preloaded.

Audits

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

Audits

Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
jQuery
3.1.0
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

Does not use HTTPS — 1 insecure request found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL Request Resolution
http://koora-lives.tv/
Allowed
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
3
Medium

Audits

Displays images with incorrect aspect ratio
Ensure that image display dimensions match their natural aspect ratio.
URL Aspect Ratio (Displayed) Aspect Ratio (Actual)
https://koora-lives.tv/uploads/logo/yalla-shoot.png
160 x 55 (2.91)
200 x 75 (2.67)
Serves images with low resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.
URL Displayed size Actual size Expected size
https://koora-lives.tv/uploads/logo/yalla-shoot.png
160 x 55
200 x 75
320 x 110
100

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for koora-lives.tv. 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 koora-lives.tv 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.
Document has a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.
Links have descriptive text
Make use of descriptive link text to assist search engines in understanding the content.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Document has a valid `hreflang`
Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.
Document has a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.
Document avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Crawling and Indexing

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

Manual Checks

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

PWA

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

PWA Optimized

Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of koora-lives.tv on mobile screens.
Provides a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.

Installable

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

PWA Optimized

Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Does not set a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Manifest doesn't have a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

Manual Checks

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

Server Location

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

Web Hosting Provider

Name IP Address
Cloudflare, Inc.
Registration

Domain Registrant

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

Domain Registrar

Security

Visitor Safety

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

SSL/TLS Certificate

Issued To: *.koora-lives.tv
Issued By: E1
Valid From: 13th December, 2022
Valid To: 13th March, 2023
Subject: CN = *.koora-lives.tv
Hash: e20020e1
Issuer: CN = E1
O = Let's Encrypt
S = US
Version: 2
Serial Number: 0x03B3131C5DC62549E3BA3CDA273B137690F7
Serial Number (Hex): 03B3131C5DC62549E3BA3CDA273B137690F7
Valid From: 13th December, 2024
Valid To: 13th March, 2024
Signature Algorithm (Short Name): ecdsa-with-SHA384
Signature Algorithm (Long Name): ecdsa-with-SHA384
Authority Key Identifier: keyid:5A:F3:ED:2B:FC:36:C2:37:79:B9:52:30:EA:54:6F:CF:55:CB:2E:AC
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://e1.o.lencr.org
CA Issuers - URI:http://e1.i.lencr.org/

SCT List: Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : B7:3E:FB:24:DF:9C:4D:BA:75:F2:39:C5:BA:58:F4:6C:
5D:FC:42:CF:7A:9F:35:C4:9E:1D:09:81:25:ED:B4:99
Timestamp : Dec 13 03:13:00.277 2022 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:21:00:B7:CB:37:37:84:FD:C3:42:E1:42:1E:
61:5F:B6:E7:B9:5C:E3:A0:0F:02:C1:6A:8F:FB:B1:40:
4C:1D:9A:31:4A:02:20:17:31:20:4D:1E:DA:6D:64:49:
5F:92:4F:85:F3:FA:DC:F1:81:D7:80:96:6C:D8:C8:96:
FC:19:48:9B:C5:1F:0B
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : E8:3E:D0:DA:3E:F5:06:35:32:E7:57:28:BC:89:6B:C9:
03:D3:CB:D1:11:6B:EC:EB:69:E1:77:7D:6D:06:BD:6E
Timestamp : Dec 13 03:13:00.242 2022 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:46:02:21:00:E9:54:EC:6A:41:54:13:D0:AD:38:97:
78:4E:D3:23:8D:B0:2C:22:21:EE:76:12:0A:A3:7A:C9:
06:50:A5:D9:15:02:21:00:AC:A0:C5:4F:3E:2C:CE:23:
8F:BD:4C:DA:C4:5F:3C:85:DB:D3:93:8E:FC:2F:E2:2C:
BF:A9:0A:A9:2F:FA:41:48
Key Usage: Digital Signature
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:koora-lives.tv
DNS:*.koora-lives.tv
Technical

DNS Lookup

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Date: 14th December, 2022
Content-Type: text/html; charset=UTF-8
Cache-Control: max-age=60
expires: 14th December, 2022
Server: cloudflare
Connection: keep-alive
vary: Accept-Encoding
pragma: public
last-modified: 14th December, 2022
x-frame-options: ALLOW-FROM https://koora-lives.tv
x-xss-protection: 1; mode=block
x-content-type-options: nosniff
content-security-policy: frame-ancestors https://koora-lives.tv
referrer-policy: strict-origin
strict-transport-security: max-age=31536000; includeSubDomains; preload
CF-Cache-Status: DYNAMIC
Report-To: {"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report\/v3?s=sM3gSW4GDyblTAx%2Fqap1uH8LAIn6%2BEywqy%2Bpn3YTOIyVcCusU9hTJ0kDor8b4GzJ3fOIOYe4RmyRouRVa5mfKGwgcV%2Fq3xt2cBojZtkxVuE8Cvdey6gi0ErY2pKl5FSyLA%3D%3D"}],"group":"cf-nel","max_age":604800}
NEL: {"success_fraction":0,"report_to":"cf-nel","max_age":604800}
CF-RAY: 7799761c3ba6c32b-EWR
alt-svc: h3=":443"; ma=86400, h3-29=":443"; ma=86400

Whois Lookup

Created:
Changed:
Expires:
Status:
Nameservers: edward.ns.cloudflare.com
joan.ns.cloudflare.com
Full Whois: No match for "KOORA-LIVES.TV".
>>> Last update of WHOIS database: 2022-12-14T19:48:54Z <<<

NOTICE: The expiration date displayed in this record is the date the
registrar's sponsorship of the domain name registration in the registry is
currently set to expire. This date does not necessarily reflect the
expiration date of the domain name registrant's agreement with the
sponsoring registrar. Users may consult the sponsoring registrar's
Whois database to view the registrar's reported date of expiration
for this registration.

TERMS OF USE: You are not authorized to access or query our Whois
database through the use of electronic processes that are high-volume and
automated except as reasonably necessary to register domain names or
modify existing registrations; the Data in VeriSign's ("VeriSign") Whois
database is provided by VeriSign for information purposes only, and to
assist persons in obtaining information about or related to a domain name
registration record. VeriSign does not guarantee its accuracy.
By submitting a Whois query, you agree to abide by the following terms of
use: You agree that you may use this Data only for lawful purposes and that
under no circumstances will you use this Data to: (1) allow, enable, or
otherwise support the transmission of mass unsolicited, commercial
advertising or solicitations via e-mail, telephone, or facsimile; or
(2) enable high volume, automated, electronic processes that apply to
VeriSign (or its computer systems). The compilation, repackaging,
dissemination or other use of this Data is expressly prohibited without
the prior written consent of VeriSign. You agree not to use electronic
processes that are automated and high-volume to access or query the
Whois database except as reasonably necessary to register domain names
or modify existing registrations. VeriSign reserves the right to restrict
your access to the Whois database in its sole discretion to ensure
operational stability. VeriSign may restrict or terminate your access to the
Whois database for failure to abide by these terms of use. VeriSign
reserves the right to modify these terms at any time.

Nameservers

Name IP Address
edward.ns.cloudflare.com 162.159.44.210
joan.ns.cloudflare.com 173.245.58.173
Related

Subdomains

Similar Sites

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Sites hosted on the same IP address