Sinhala - Sinhala.com

Overview

Snoop Summary for sinhala.com

This is a free and comprehensive report about sinhala.com. The domain sinhala.com is currently hosted on a server located in Lansing, Michigan in United States with the IP address 72.52.179.174, where USD is the local currency and the local language is English. If sinhala.com was to be sold it would possibly be worth $52 USD (based on the daily revenue potential of the website over a 24 month period). Sinhala.com is slightly popular with an estimated 20 daily unique visitors. This report was last updated 13th May, 2020.

About sinhala.com

Site Preview:
Title:
Description:
Keywords and Tags:	parked domain
Related Terms:	adaderana lk sinhala, divaina lk sinhala, sinhala, sinhala teledrama, www lankaenews com sinhala, www sinhala niws com
Fav Icon:
Age:	Over 23 years old
Domain Created:	3rd May, 2001
Domain Updated:	5th April, 2019
Domain Expires:	3rd May, 2021

Review

Snoop Score

1/5

Valuation

$52 USD

Note: All valuation figures are estimates.

Popularity

Low

Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank:	9,637,241
Alexa Reach:	<0.0001%
SEMrush Rank (US):
SEMrush Authority Score:
Moz Domain Authority:	0
Moz Page Authority:	0

Organic vs Paid (Google Ads)

Traffic

Visitors

Daily Visitors:	20
Monthly Visitors:	609
Yearly Visitors:	7,300

Note: All visitors figures are estimates.

Visitors By Country

Revenue

Daily Revenue:	$0 USD
Monthly Revenue:	$2 USD
Yearly Revenue:	$21 USD

Note: All revenue figures are estimates.

Revenue By Country

SEO

Backlinks Analysis (SEMrush)

Top Ranking Keywords (US)

Domain Analysis

	Value	Length
Domain:	sinhala.com	11
Domain Name:	sinhala	7
Extension (TLD):	com	3

Expiry Check:

Page Speed Analysis

Average Load Time:
Load Time Comparison:

Avg. (All Categories)

Performance

Accessibility

Best Practices

SEO

Progressive Web App

0–49 (Fail) 50–89 (Average) 90–100 (Pass)

Simulate loading on desktop

Performance

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

Passing (41)

Metrics

First Contentful Paint — 0.7 s
The time taken for the first image or text on the page to be rendered.

First Meaningful Paint — 0.7 s
The time taken for the primary content of the page to be rendered.

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

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

First CPU Idle — 0.9 s
The time taken for the page's main thread to be quiet enough to handle input.

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

Other

Estimated Input Latency — 10 ms
The time taken for the page to respond to user input (during the busiest 5 second window of page load). Users are likely to perceive sinhala.com as laggy when the latency is higher than 0.05 seconds.

Total Blocking Time — 50 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).

Network Requests
Below is a list of network requests that were made during page load.

URL	Start Time (Ms)	End Time (Ms)	Transfer Size (Bytes)	Resource Size (Bytes)	Status Code	MIME Type	Resource Type
http://sinhala.com/	0	153.38299999712	356	0	302	text/html
http://ww1.sinhala.com/	153.87999999803	463.63800001564	8151	18168	200	text/html	Document
http://img.sedoparking.com/js/jquery-1.4.2.min.js	475.25499999756	495.93400000595	27306	52770	200	application/x-javascript	Script
https://www.google.com/adsense/domains/caf.js	475.62600002857	497.31900001643	60308	165541	200	text/javascript	Script
http://parking.parklogic.com/page/enhance.js?pcId=2&domain=sinhala.com	475.9840000188	550.68799998844	2757	2488	200	text/javascript	Script
http://img.sedoparking.com/templates/brick_gfx/common/logo_white.png	476.28699999768	494.40800002776	2749	2237	200	image/png	Image
https://www.google.com/afs/ads/i/iframe.html	592.21899998374	598.43200002797	1577	1243	200	text/html	Document
https://www.google.com/dp/ads?r=m&client=dp-sedo80_3ph&channel=exp-0051%2Cauxa-control-1%2C2785943&hl=en&adtest=off&adsafe=low&type=3&swp=as-drid-2523287999779246&uiopt=true&oe=UTF-8&ie=UTF-8&fexp=21404%2C17300162%2C17300165%2C17300167&format=r10%7Cs&num=0&output=afd_ads&domain_name=ww1.sinhala.com&v=3&adext=as1%2Csr1&bsl=8&u_his=2&u_tz=-420&dt=1589335211064&u_w=800&u_h=600&biw=1350&bih=940&psw=1350&psh=331&frm=0&uio=sl1sr1-st24sa18lt45-&cont=rlblock_center&csize=w1190h74&inames=master-1&jsv=27311&rurl=http%3A%2F%2Fww1.sinhala.com%2F	598.32599997753	694.07299999148	7675	10151	200	text/html	Document
http://ww1.sinhala.com/search/tsc.php?200=MzEzMjY1OTY3&21=NjcuMjA1LjEzNy4xMjc=&681=MTU4OTMzNTIxMDJiOTI4MmM3ZmRjNWIzZTE1MjQ5MTZhM2NiNzE4ZmI4&crc=c0ea18e6321ad8de5464bb450279796246f536f6&cv=1	601.88999999082	713.26899999985	175	0	200	text/html	XHR
https://www.google.com/adsense/domains/caf.js	703.33400001982	722.95399999712	59797	165591	200	text/javascript	Script
https://afs.googleusercontent.com/dp-sedo/bullet_lime.gif	772.68100000219	825.53600001847	1958	1399	200	image/gif	Image
https://www.google.com/js/bg/IBsoycHqu6ZdqZ5gHS35_f-v1rrNoj4t1cu0jBGkozc.js	783.77600002568	788.72700000647	6120	12468	200	text/javascript	Script
https://www.google.com/js/bg/IBsoycHqu6ZdqZ5gHS35_f-v1rrNoj4t1cu0jBGkozc.js	895.59700002428	895.68499999586	6120	12468	200	text/javascript	Script

Show Details

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)
485.59	7.355
518.337	22.038
540.699	8.468
571.323	52.11
625.195	5.75
752.622	42.01
796.277	6.066
809.619	82.431
895.747	11.906
916.067	84.661

Show Details

Diagnostics
Below is a collection of useful page vitals.
View Data

Metrics
Below is a collection of metrics.
View Data

Opportunities

Eliminate render-blocking resources — Potential savings of 0 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Sinhala.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.

URL	Size (Bytes)	Potential Savings (Ms)
http://img.sedoparking.com/js/jquery-1.4.2.min.js	27306	230

Show Details

Properly size images
Images can slow down the page's load time. Sinhala.com should consider serving more appropriate-sized images.

Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Sinhala.com should consider lazy-loading offscreen and hidden images.

Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Sinhala.com should consider minifying CSS files.

Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Sinhala.com should consider minifying JS files.

Remove unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Sinhala.com 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
Image formats like PNG and JPEG have poor compression when compared to other next-gen formats, such as JPEG 200, JPEG XR and WebP.

Enable text compression — Potential savings of 1 KB
Text-based resources should be served with compression, such as gzip, deflate or brotli.

URL	Size (Bytes)	Potential Savings (Bytes)
http://parking.parklogic.com/page/enhance.js?pcId=2&domain=sinhala.com	2488	1453

Show Details

Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.

Server response times are low (TTFB) — Root document took 310 ms
Time to First Byte (TTFB) identifies the time at which the server sends a response.

Avoid multiple page redirects — Potential savings of 190 ms
Redirects can cause additional delays before the page can begin loading. Sinhala.com should avoid multiple or unnecessary page redirects.

URL	Time Spent (Ms)
(Start) http://sinhala.com/	0
http://ww1.sinhala.com/	190

Show Details

Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Sinhala.com should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.

Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.

Diagnostics

Avoids enormous network payloads — Total size was 181 KB
Large network payloads can cost users money and are linked to long load times.

URL	Size (Bytes)
https://www.google.com/adsense/domains/caf.js	60308
https://www.google.com/adsense/domains/caf.js	59797
http://img.sedoparking.com/js/jquery-1.4.2.min.js	27306
http://ww1.sinhala.com/	8151
https://www.google.com/dp/ads?r=m&client=dp-sedo80_3ph&channel=exp-0051%2Cauxa-control-1%2C2785943&hl=en&adtest=off&adsafe=low&type=3&swp=as-drid-2523287999779246&uiopt=true&oe=UTF-8&ie=UTF-8&fexp=21404%2C17300162%2C17300165%2C17300167&format=r10%7Cs&num=0&output=afd_ads&domain_name=ww1.sinhala.com&v=3&adext=as1%2Csr1&bsl=8&u_his=2&u_tz=-420&dt=1589335211064&u_w=800&u_h=600&biw=1350&bih=940&psw=1350&psh=331&frm=0&uio=sl1sr1-st24sa18lt45-&cont=rlblock_center&csize=w1190h74&inames=master-1&jsv=27311&rurl=http%3A%2F%2Fww1.sinhala.com%2F	7675
https://www.google.com/js/bg/IBsoycHqu6ZdqZ5gHS35_f-v1rrNoj4t1cu0jBGkozc.js	6120
https://www.google.com/js/bg/IBsoycHqu6ZdqZ5gHS35_f-v1rrNoj4t1cu0jBGkozc.js	6120
http://parking.parklogic.com/page/enhance.js?pcId=2&domain=sinhala.com	2757
http://img.sedoparking.com/templates/brick_gfx/common/logo_white.png	2749
https://afs.googleusercontent.com/dp-sedo/bullet_lime.gif	1958

Show Details

Uses efficient cache policy on static assets — 4 resources found
Sinhala.com can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.

URL	Cache TTL (Ms)	Size (Bytes)
http://parking.parklogic.com/page/enhance.js?pcId=2&domain=sinhala.com	0	2757
https://afs.googleusercontent.com/dp-sedo/bullet_lime.gif	82800000	1958
http://img.sedoparking.com/js/jquery-1.4.2.min.js	86400000	27306
http://img.sedoparking.com/templates/brick_gfx/common/logo_white.png	604800000	2749

Show Details

Avoids an excessive DOM size — 28 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		28
Maximum DOM Depth	SHOW DETAILS	6
Maximum Child Elements	SHOW DETAILS	9

Show Details

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. Sinhala.com should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.

JavaScript execution time — 0.2 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.

URL	Total CPU Time (Ms)	Script Evaluation (Ms)	Script Parse (Ms)
https://www.google.com/adsense/domains/caf.js	240.056	210.784	23.716
Other	77.795	11.92	2.026

Show Details

Minimizes main-thread work — 0.4 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.

Category	Time Spent (Ms)
Script Evaluation	272.238
Other	40.941
Script Parsing & Compilation	30.527
Style & Layout	18.246
Parse HTML & CSS	8.954
Rendering	8.153
Garbage Collection	0.548

Show Details

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 — 13 requests • 181 KB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.

Resource Type	Requests	Transfer Size (Bytes)
Total	13	185049
Script	6	162408
Document	3	17403
Image	2	4707
Other	2	531
Stylesheet	0	0
Media	0	0
Font	0	0
Third-party	10	176367

Show Details

Minimize third-party usage — Third-party code blocked the main thread for 50 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	Size (Bytes)	Main-Thread Blocking Time (Ms)
SHOW DETAILS	141597	50.486

Show Details

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.

Accessibility

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

Navigation

`[accesskey]` values are unique
Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.

The page contains a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.

No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.

`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.

Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.

`[role]`s are contained by their required parent element
Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.

`[role]` values are valid
All ARIA roles require valid values to perform their intended functions.

`[aria-*]` attributes have valid values
ARIA attributes cannot be interpreted with invalid values when used by screen readers and other assistive technologies.

`[aria-*]` attributes are valid and not misspelled
ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.

Audio and video

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

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

`<video>` elements contain a `<track>` element with `[kind="description"]`
Sinhala.com may provide relevant information that dialogue cannot, by using audio descriptions.

Names and labels

Buttons have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.

Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.

`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.

Form elements have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.

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

`<object>` elements have `[alt]` text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>` or `<template>` elements.
Screen readers and other assistive technologies may produce poor and inaccurate output when definition lists are not properly marked up.

Definition list items are wrapped in `<dl>` elements
In order for screen readers and other assistive technologies to properly announce definition list items ('<dt>' and '<dd>'), they must be wrapped in parent a '<dl>' element.

Presentational `<table>` elements avoid using `<th>`, `<caption>` or the `[summary]` attribute.
It is advised to not include data elements in tables which are used for layout purposes, as it may create confusion for screen reader and other assistive technology users.

Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Use proper list structure to aid screen readers and other assistive technologies.

List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
In order for screen readers to announce list items, ensure that list items ('<li>') are contained within parent '<ul>' or '<ol>' tags.

Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that '<td>' cells using the headers attribute only refer to other cells in the same table, to improve screen reader user experience.

`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that table headers refer to some set of cells, to improve screen reader user experience.

Best practices

`[id]` attributes on the page are unique
It is advised to keep all id attributes unique in order to prevent instances from being overlooked by screen readers and other assistive technologies.

The document does not use `<meta http-equiv="refresh">`
Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.

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

Internationalization and localization

`<html>` element has a valid value for its `[lang]` attribute
Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.

`[lang]` attributes have a valid value
Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.

Contrast

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

Failing Elements
sinhala.com

Show Details

Names and labels

`<frame>` or `<iframe>` elements do not have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.

Failing Elements
iframe
iframe

Show Details

Internationalization and localization

`<html>` element does not have a `[lang]` attribute
It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.

Failing Elements
html

Show Details

Manual Checks

The page has a logical tab order
The visual layout should be logical in its tab order and users cannot focus elements that are offscreen.

Interactive controls are keyboard focusable
Ensure that custom interactive controls are keyboard focusable and that a focus indicator is displayed.

Interactive elements indicate their purpose and state
Ensure that interactive elements (such as links and buttons) are distinguishable from non-interactive elements and that they indicate their state.

The user's focus is directed to new content added to the page
When new content (such as a dialogue) is added to the page, the user's focus should be directed to it.

User focus is not accidentally trapped in a region
Avoid focus being accidentally trapped when a user tabs in and out of controls or regions on page.

Custom controls have associated labels
Ensure that custom interactive controls have associated labels, which are provided by aria-label and aria-labelledby attributes.

Custom controls have ARIA roles
Ensure that all custom interactive controls have appropriate ARIA roles.

Visual order on the page follows DOM order
Ensure that the DOM order matches with the page's visual order, in order to improve navigation for screen readers and other assistive technologies.

Offscreen content is hidden from assistive technology
Ensure that offscreen content is hidden through the use of "display:none" styling or the aria-hidden attribute.

Headings don't skip levels
Ensure that headings create an outline for the page and that heading levels are not skipped.

HTML5 landmark elements are used to improve navigation
Elements such as <main> and <nav> are recommended as they are used by screen readers and other assistive technologies to improve keyboard navigation.

Best Practices

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

Passing (10)
Failing (4)

Other

Avoids Application Cache
Application cache is deprecated and is no longer recommended.

Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.

Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.

Page has the HTML doctype
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.

Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.

Name	Version
jQuery	1.4.2
jQuery (Fast path)

Show Details

Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.

Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.

Allows users to paste into password fields
Ensure that password inputs may be pasted into to aid in the user's ability to use password managers and improve security.

No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.

Displays images with correct aspect ratio
Ensure that image display dimensions match their natural aspect ratio.

Other

Does not use HTTPS — 6 insecure requests found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.

Insecure URL
http://sinhala.com/
http://ww1.sinhala.com/
http://img.sedoparking.com/js/jquery-1.4.2.min.js
http://parking.parklogic.com/page/enhance.js?pcId=2&domain=sinhala.com
http://img.sedoparking.com/templates/brick_gfx/common/logo_white.png
http://ww1.sinhala.com/search/tsc.php?200=MzEzMjY1OTY3&21=NjcuMjA1LjEzNy4xMjc=&681=MTU4OTMzNTIxMDJiOTI4MmM3ZmRjNWIzZTE1MjQ5MTZhM2NiNzE4ZmI4&crc=c0ea18e6321ad8de5464bb450279796246f536f6&cv=1

Show Details

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

URL	Location
http://parking.parklogic.com/page/enhance.js?pcId=2&domain=sinhala.com	line: 39
https://www.google.com/adsense/domains/caf.js	line: 193

Show Details

Links to cross-origin destinations are unsafe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.

URL	Target	Rel
https://uniregistry.com/market/domain/sinhala.com	_blank
http://sedoparking.com/	_blank

Show Details

Includes front-end JavaScript libraries with known security vulnerabilities — 4 vulnerabilities detected
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.

Library Version	Vulnerability Count	Highest Severity
SHOW DETAILS	4	Medium

Show Details

SEO

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

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.

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.

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.

Mobile Friendly

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.

Mobile Friendly

Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of sinhala.com on mobile screens.

Content Best Practices

Links do not have descriptive text — 1 link found
Make use of descriptive link text to assist search engines in understanding the content.

Link destination	Link Text
https://uniregistry.com/market/domain/sinhala.com	Click here

Show Details

Crawling and Indexing

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

Blocking Directive Source
SHOW DETAILS

Show Details

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

Fast and reliable

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

PWA Optimized

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.

Contains some content when JavaScript is not available
Apps should display alternative content for when JavaScript is disabled.

Fast and reliable

Current page does not respond with a 200 when offline
In order for Progressive Web Apps to be made available offline, ensure that the app is using a service worker.

`start_url` does not respond with a 200 when offline
Consider using a service worker for Progressive Web Apps to ensure greater reliability for the user, in the case of poor network conditions.

Installable

Does not use HTTPS — 6 insecure requests found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.

Insecure URL
http://sinhala.com/
http://ww1.sinhala.com/
http://img.sedoparking.com/js/jquery-1.4.2.min.js
http://parking.parklogic.com/page/enhance.js?pcId=2&domain=sinhala.com
http://img.sedoparking.com/templates/brick_gfx/common/logo_white.png
http://ww1.sinhala.com/search/tsc.php?200=MzEzMjY1OTY3&21=NjcuMjA1LjEzNy4xMjc=&681=MTU4OTMzNTIxMDJiOTI4MmM3ZmRjNWIzZTE1MjQ5MTZhM2NiNzE4ZmI4&crc=c0ea18e6321ad8de5464bb450279796246f536f6&cv=1

Show Details

Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.

Web app manifest does not meet the installability requirements
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
View Data

PWA Optimized

Does not redirect HTTP traffic to HTTPS
It is advised to redirect all HTTP traffic to HTTPS, in order to enable secure web features for all users.

Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data

Does not set a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data

Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of sinhala.com on mobile screens.

Does not provide a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.

Manual Checks

Site works cross-browser
Ensure that the Progressive Web App works correctly across every major browser.

Page transitions don't feel like they block on the network
Users perceive apps with responsive, snappy transitions as higher peforming and ensures a great user experience, even on a slow network.

Each page has a URL
Ensure that all pages are deep linkable via URL. They should also be unique for the purpose of shareability on social media.

Avg. (All Categories)

Performance

Accessibility

Best Practices

SEO

Progressive Web App

0–49 (Fail) 50–89 (Average) 90–100 (Pass)

Simulate loading on mobile

Performance

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

Metrics

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

Opportunities

Properly size images
Images can slow down the page's load time. Sinhala.com should consider serving more appropriate-sized images.

Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Sinhala.com should consider lazy-loading offscreen and hidden images.

Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Sinhala.com should consider minifying CSS files.

Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Sinhala.com should consider minifying JS files.

Remove unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Sinhala.com 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
Image formats like PNG and JPEG have poor compression when compared to other next-gen formats, such as JPEG 200, JPEG XR and WebP.

Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.

Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.

Server response times are low (TTFB) — Root document took 170 ms
Time to First Byte (TTFB) identifies the time at which the server sends a response.

Avoid multiple page redirects — Potential savings of 630 ms
Redirects can cause additional delays before the page can begin loading. Sinhala.com should avoid multiple or unnecessary page redirects.

URL	Time Spent (Ms)
(Start) http://sinhala.com/	0
http://ww1.sinhala.com/	630

Show Details

Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Sinhala.com should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.

Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.

Diagnostics

Avoids enormous network payloads — Total size was 175 KB
Large network payloads can cost users money and are linked to long load times.

URL	Size (Bytes)
https://www.google.com/adsense/domains/caf.js	60093
http://www.google.com/adsense/domains/caf.js	58566
http://img.sedoparking.com/js/jquery-1.11.3.custom.min.js	25745
http://ww1.sinhala.com/	10302
https://www.google.com/dp/ads?r=m&cpp=0&client=dp-sedo80_3ph&channel=exp-0050%2Cauxa-control-1%2C2785943&hl=en&adtest=off&adsafe=low&type=3&swp=as-drid-2523287999779246&uiopt=true&oe=UTF-8&ie=UTF-8&fexp=21404%2C17300162%2C17300169%2C17300171%2C17300191%2C17300193&format=r10%7Cs&num=0&output=afd_ads&domain_name=ww1.sinhala.com&v=3&adext=as1%2Csr1&bsl=8&u_his=2&u_tz=-420&dt=1589335219470&u_w=412&u_h=660&biw=412&bih=660&psw=412&psh=561&frm=0&uio=sl1sr1-st22sa10lt40-&cont=rb-default&csize=w0h0&inames=master-1&jsv=27311&rurl=http%3A%2F%2Fww1.sinhala.com%2F	7795
https://www.google.com/js/bg/IBsoycHqu6ZdqZ5gHS35_f-v1rrNoj4t1cu0jBGkozc.js	6122
https://www.google.com/js/bg/IBsoycHqu6ZdqZ5gHS35_f-v1rrNoj4t1cu0jBGkozc.js	6122
https://afs.googleusercontent.com/dp-sedo/bullet_lime.gif	1958
https://www.google.com/afs/ads/i/iframe.html	1625
http://sinhala.com/	371

Show Details

Uses efficient cache policy on static assets — 2 resources found
Sinhala.com can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.

URL	Cache TTL (Ms)	Size (Bytes)
https://afs.googleusercontent.com/dp-sedo/bullet_lime.gif	82800000	1958
http://img.sedoparking.com/js/jquery-1.11.3.custom.min.js	86400000	25745

Show Details

Avoids an excessive DOM size — 28 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		28
Maximum DOM Depth	SHOW DETAILS	7
Maximum Child Elements	SHOW DETAILS	9

Show Details

Avoid chaining critical requests — 2 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Sinhala.com should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.

JavaScript execution time — 1.0 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.

URL	Total CPU Time (Ms)	Script Evaluation (Ms)	Script Parse (Ms)
https://www.google.com/adsense/domains/caf.js	847.572	766.276	25.928
Other	294.04	39.072	10.36
http://ww1.sinhala.com/	133.248	102.04	4.516
http://img.sedoparking.com/js/jquery-1.11.3.custom.min.js	59.476	51.052	5.916

Show Details

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	1002.628
Other	167.12
Style & Layout	72.432
Script Parsing & Compilation	70.68
Parse HTML & CSS	35.588
Garbage Collection	32.852
Rendering	24.544

Show Details

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 • 175 KB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.

Resource Type	Requests	Transfer Size (Bytes)
Total	11	178874
Script	5	156648
Document	3	19722
Image	1	1958
Other	2	546
Stylesheet	0	0
Media	0	0
Font	0	0
Third-party	8	168026

Show Details

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.

Other

Network Requests
Below is a list of network requests that were made during page load.

URL	Start Time (Ms)	End Time (Ms)	Transfer Size (Bytes)	Resource Size (Bytes)	Status Code	MIME Type	Resource Type
http://sinhala.com/	0	93.989999964833	371	0	302	text/html
http://ww1.sinhala.com/	94.35599995777	266.65999996476	10302	30289	200	text/html	Document
http://img.sedoparking.com/js/jquery-1.11.3.custom.min.js	279.76099983789	301.05699994601	25745	63696	200	application/x-javascript	Script
http://www.google.com/adsense/domains/caf.js	280.06300004199	298.9139999263	58566	165584	200	text/javascript	Script
http://ww1.sinhala.com/search/tsc.php?200=MzEzMjY1OTY3&21=NjcuMjA1LjEzNy4xMjc=&681=MTU4OTMzNTIxOTA2NzU2NGNjMzk4MGUxYWIxYzU1Y2UzNmU4YmJhZWI4&crc=6416bfc16547cb4bf3dd23143e6e26059f7b51a2&cv=1	335.63799993135	447.85299990326	175	0	200	text/html	XHR
https://www.google.com/afs/ads/i/iframe.html	356.44300002605	361.63900000975	1625	1243	200	text/html	Document
https://www.google.com/dp/ads?r=m&cpp=0&client=dp-sedo80_3ph&channel=exp-0050%2Cauxa-control-1%2C2785943&hl=en&adtest=off&adsafe=low&type=3&swp=as-drid-2523287999779246&uiopt=true&oe=UTF-8&ie=UTF-8&fexp=21404%2C17300162%2C17300169%2C17300171%2C17300191%2C17300193&format=r10%7Cs&num=0&output=afd_ads&domain_name=ww1.sinhala.com&v=3&adext=as1%2Csr1&bsl=8&u_his=2&u_tz=-420&dt=1589335219470&u_w=412&u_h=660&biw=412&bih=660&psw=412&psh=561&frm=0&uio=sl1sr1-st22sa10lt40-&cont=rb-default&csize=w0h0&inames=master-1&jsv=27311&rurl=http%3A%2F%2Fww1.sinhala.com%2F	362.09199996665	454.29400005378	7795	10308	200	text/html	Document
https://www.google.com/adsense/domains/caf.js	465.09999991395	485.33999989741	60093	165584	200	text/javascript	Script
https://afs.googleusercontent.com/dp-sedo/bullet_lime.gif	536.76999988966	582.15599996038	1958	1399	200	image/gif	Image
https://www.google.com/js/bg/IBsoycHqu6ZdqZ5gHS35_f-v1rrNoj4t1cu0jBGkozc.js	547.06300003454	553.22199990042	6122	12468	200	text/javascript	Script
https://www.google.com/js/bg/IBsoycHqu6ZdqZ5gHS35_f-v1rrNoj4t1cu0jBGkozc.js	653.94299989566	654.0349998977	6122	12468	200	text/javascript	Script

Show Details

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)
288.814	7.915
325.733	16.943
342.878	41.111
385.907	6.277
476.601	6.239
515.24	42.061
558.861	6.584
574.516	83.141
660.046	10.663
674.495	84.39

Show Details

Diagnostics
Below is a collection of useful page vitals.
View Data

Metrics
Below is a collection of metrics.
View Data

Metrics

First Contentful Paint — 2.6 s
The time taken for the first image or text on the page to be rendered.

First Meaningful Paint — 2.6 s
The time taken for the primary content of the page to be rendered.

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

First CPU Idle — 4.3 s
The time taken for the page's main thread to be quiet enough to handle input.

Other

Total Blocking Time — 550 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).

First Contentful Paint (3G) — 5096 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 230 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Sinhala.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.

URL	Size (Bytes)	Potential Savings (Ms)
http://img.sedoparking.com/js/jquery-1.11.3.custom.min.js	25745	780

Show Details

Metrics

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

Other

Estimated Input Latency — 100 ms
The time taken for the page to respond to user input (during the busiest 5 second window of page load). Users are likely to perceive sinhala.com as laggy when the latency is higher than 0.05 seconds.

Diagnostics

Reduce the impact of third-party code — Third-party code blocked the main thread for 540 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	Size (Bytes)	Main-Thread Blocking Time (Ms)
SHOW DETAILS	140323	535.264

Show Details

Accessibility

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

Navigation

`[accesskey]` values are unique
Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.

The page contains a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.

No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.

`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.

Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.

`[role]`s are contained by their required parent element
Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.

`[role]` values are valid
All ARIA roles require valid values to perform their intended functions.

`[aria-*]` attributes have valid values
ARIA attributes cannot be interpreted with invalid values when used by screen readers and other assistive technologies.

`[aria-*]` attributes are valid and not misspelled
ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.

Audio and video

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

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

`<video>` elements contain a `<track>` element with `[kind="description"]`
Sinhala.com may provide relevant information that dialogue cannot, by using audio descriptions.

Names and labels

Buttons have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.

Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.

`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.

Form elements have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.

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

`<object>` elements have `[alt]` text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>` or `<template>` elements.
Screen readers and other assistive technologies may produce poor and inaccurate output when definition lists are not properly marked up.

Definition list items are wrapped in `<dl>` elements
In order for screen readers and other assistive technologies to properly announce definition list items ('<dt>' and '<dd>'), they must be wrapped in parent a '<dl>' element.

Presentational `<table>` elements avoid using `<th>`, `<caption>` or the `[summary]` attribute.
It is advised to not include data elements in tables which are used for layout purposes, as it may create confusion for screen reader and other assistive technology users.

Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Use proper list structure to aid screen readers and other assistive technologies.

List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
In order for screen readers to announce list items, ensure that list items ('<li>') are contained within parent '<ul>' or '<ol>' tags.

Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that '<td>' cells using the headers attribute only refer to other cells in the same table, to improve screen reader user experience.

`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that table headers refer to some set of cells, to improve screen reader user experience.

Best practices

`[id]` attributes on the page are unique
It is advised to keep all id attributes unique in order to prevent instances from being overlooked by screen readers and other assistive technologies.

The document does not use `<meta http-equiv="refresh">`
Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.

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.

Contrast

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

Failing Elements
sinhala.com
This webpage was generated by the domain owner using Sedo Domain Parking. Discl…
Sedo Domain Parking
Privacy Policy

Show Details

Names and labels

`<frame>` or `<iframe>` elements do not have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.

Failing Elements
iframe
iframe

Show Details

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
meta