12prayers.com

12prayers.com is SSL secured

Free website and domain report on 12prayers.com

Last Updated: 27th January, 2021 Update Now
Overview

Snoop Summary for 12prayers.com

This is a free and comprehensive report about 12prayers.com. The domain 12prayers.com is currently hosted on a server located in Switzerland with the IP address 46.28.206.115, where the local currency is CHE and French is the local language. Our records indicate that 12prayers.com is privately registered by REDACTED FOR PRIVACY. 12prayers.com has the potential to be earning an estimated $5 USD per day from advertising revenue. If 12prayers.com was to be sold it would possibly be worth $3,613 USD (based on the daily revenue potential of the website over a 24 month period). 12prayers.com receives an estimated 1,732 unique visitors every day - a large amount of traffic! This report was last updated 27th January, 2021.

About 12prayers.com

Site Preview: 12prayers.com 12prayers.com
Title: 12Prayers
Description:
Keywords and Tags: marketing, merchandising
Related Terms:
Fav Icon:
Age: Over 4 years old
Domain Created: 26th January, 2020
Domain Updated: 2nd January, 2021
Domain Expires: 26th January, 2024
Review

Snoop Score

2/5

Valuation

$3,613 USD
Note: All valuation figures are estimates.

Popularity

Modest
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 437,718
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: 1,732
Monthly Visitors: 52,717
Yearly Visitors: 632,180
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $5 USD
Monthly Revenue: $150 USD
Yearly Revenue: $1,802 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: 12prayers.com 13
Domain Name: 12prayers 9
Extension (TLD): com 3
Expiry Check:

Page Speed Analysis

Average Load Time:
Load Time Comparison:

PageSpeed Insights

Avg. (All Categories) 68
Performance 82
Accessibility 86
Best Practices 79
SEO 55
Progressive Web App 37
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
Simulate loading on desktop
82

Performance

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

Metrics

First Contentful Paint — 0.9 s
The time taken for the first image or text on the page to be rendered.
Time to Interactive — 1.5 s
The time taken for the page to become fully interactive.
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).
Cumulative Layout Shift — 0.003
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

First CPU Idle — 1.5 s
The time taken for the page's main thread to be quiet enough to handle input.
Max Potential First Input Delay — 50 ms
Users could experience a delay when interacting with the page.
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 12prayers.com as laggy when the latency is higher than 0.05 seconds.
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://12prayers.com/
0
474.74700002931
246
0
301
text/html
https://12prayers.com/
475.76199995819
1298.1000000145
9924
44773
200
text/html
Document
https://fonts.googleapis.com/css?family=Material+Icons|Material+Icons+Outlined|Material+Icons+Two+Tone|Material+Icons+Round|Material+Icons+Sharp
1321.8150000321
1329.0499999421
1712
3025
200
text/css
Stylesheet
https://stackpath.bootstrapcdn.com/bootstrap/4.4.1/css/bootstrap.min.css
1322.3219999345
1345.6299999962
24146
159515
200
text/css
Stylesheet
https://code.jquery.com/jquery-3.4.1.min.js
1322.5610000081
1336.7680000374
31144
88145
200
application/javascript
Script
https://stackpath.bootstrapcdn.com/bootstrap/4.4.1/js/bootstrap.min.js
1323.3199999668
1335.1959999418
16391
60010
200
text/javascript
Script
https://unpkg.com/aos@2.3.1/dist/aos.css
1323.6259999685
1361.4759999327
2299
26053
200
text/css
Stylesheet
https://cdnjs.cloudflare.com/ajax/libs/slick-carousel/1.9.0/slick.min.css.map
1322.1129999729
1413.3920000168
0
0
-1
Stylesheet
https://cdnjs.cloudflare.com/ajax/libs/slick-carousel/1.9.0/slick-theme.min.css
1324.3079999229
1344.0880000126
1738
2390
200
text/css
Stylesheet
https://12prayers.com/stylesheets/home.css
1324.4929999346
1721.7800000217
11798
80233
200
text/css
Stylesheet
https://12prayers.com/images/logo_regular.png
1405.9579999885
2073.5080000013
8694
8392
200
image/png
Image
https://12prayers.com/images/hero2.2.png
1406.3059999608
2547.9640000267
867584
867279
200
image/png
Image
https://12prayers.com/images/image00.png
1406.5410000039
2331.5019999864
152819
152514
200
image/png
Image
https://12prayers.com/images/icon-hiw-01.png
1406.8640000187
1511.2979999976
13146
12843
200
image/png
Image
https://12prayers.com/images/icon-hiw-02.png
1407.2930000257
2158.6469999747
16197
15894
200
image/png
Image
https://12prayers.com/images/icon-hiw-03.png
1407.5339999981
2077.071000007
15516
15213
200
image/png
Image
https://12prayers.com/images/icon-hiw-04.png
1407.744999975
1950.0439999392
12565
12262
200
image/png
Image
https://12prayers.com/images/image01.svg
1408.1030000234
1900.6149999332
36744
36437
200
image/svg+xml
Image
https://12prayers.com/images/image02.svg
1408.3109999774
1902.2800000384
37142
36835
200
image/svg+xml
Image
https://12prayers.com/images/image03.svg
1408.516000025
2048.2729999349
28471
28164
200
image/svg+xml
Image
https://12prayers.com/images/logo_icon.png
1408.7379999692
2038.4550000308
10000
9698
200
image/png
Image
https://12prayers.com/images/logo.png
1408.9280000189
2056.2459999928
8694
8392
200
image/png
Image
https://unpkg.com/aos@2.3.1/dist/aos.js
1404.3149999343
1432.5739999767
4971
14239
200
application/javascript
Script
https://cdnjs.cloudflare.com/ajax/libs/slick-carousel/1.9.0/slick.min.js
1404.8409999814
1423.5270000063
10672
43881
200
application/javascript
Script
https://cdnjs.cloudflare.com/ajax/libs/font-awesome/5.12.1/js/all.min.js
1405.3409999469
1456.768999924
347777
1147965
200
application/javascript
Script
https://12prayers.com/javascripts/home.js
1405.5879999651
1959.1539999237
2343
2014
200
application/javascript
Script
https://12prayers.com/stylesheets/fonts/CircularXXWeb-Book.woff
1797.1569999354
2493.0750000058
102678
102361
200
application/font-woff
Font
https://12prayers.com/stylesheets/fonts/CircularXXWeb-Medium.woff
1797.390999971
2480.0719999475
104331
104014
200
application/font-woff
Font
https://12prayers.com/stylesheets/fonts/tn-regular-webfont.woff2
1797.8120000334
2290.1779999956
18820
18504
200
application/font-woff2
Font
https://fonts.gstatic.com/s/materialicons/v70/flUhRq6tzZclQEJ-Vdg-IuiaDsNcIhQ8tQ.woff2
1798.1569999829
1802.4140000343
99381
98812
200
font/woff2
Font
https://12prayers.com/stylesheets/fonts/tn-bold-webfont.woff2
1799.1560000228
2292.4999999814
19200
18884
200
application/font-woff2
Font
https://12prayers.com/stylesheets/fonts/tt-medium-webfont.woff2
1799.7419999447
2299.8779999325
18796
18480
200
application/font-woff2
Font
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
1337.941
13.435
1356.016
11.631
1384.871
11.988
1396.934
53.085
1522.036
7.398
1764.176
54.26
1818.456
61.795
1882.786
11.998
1908.502
9.184
1938.245
21.003
1960.162
19.85
1980.512
14.348
1998.609
9.806
2008.51
6.368
2086.279
10.398
2330.16
7.85
2357.627
12.496
2371.271
5.438
2524.129
14.516
2543.859
17.735
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data

Opportunities

Defer offscreen images
Time to Interactive can be slowed down by resources on the page. 12prayers.com should consider lazy-loading offscreen and hidden images.
Minify CSS — Potential savings of 3 KiB
Cascading Style Sheets (CSS) files can contribute to network payload sizes. 12prayers.com should consider minifying CSS files.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://12prayers.com/stylesheets/home.css
11798
3139
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. 12prayers.com should consider minifying JS files.
Remove unused CSS — Potential savings of 23 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. 12prayers.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://stackpath.bootstrapcdn.com/bootstrap/4.4.1/css/bootstrap.min.css
24146
23844
Remove unused JavaScript — Potential savings of 21 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://code.jquery.com/jquery-3.4.1.min.js
31144
21130
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Enable text compression — Potential savings of 1 KiB
Text-based resources should be served with compression, such as gzip, deflate or brotli.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://12prayers.com/javascripts/home.js
2014
1450
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Avoid multiple page redirects — Potential savings of 190 ms
Redirects can cause additional delays before the page can begin loading. 12prayers.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://12prayers.com/
190
https://12prayers.com/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. 12prayers.com should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers — Potential savings of 0 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
URL Potential Savings (Bytes)
https://unpkg.com/aos@2.3.1/dist/aos.js
58
https://cdnjs.cloudflare.com/ajax/libs/font-awesome/5.12.1/js/all.min.js
51

Diagnostics

Avoids enormous network payloads — Total size was 1,988 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://12prayers.com/images/hero2.2.png
867584
https://cdnjs.cloudflare.com/ajax/libs/font-awesome/5.12.1/js/all.min.js
347777
https://12prayers.com/images/image00.png
152819
https://12prayers.com/stylesheets/fonts/CircularXXWeb-Medium.woff
104331
https://12prayers.com/stylesheets/fonts/CircularXXWeb-Book.woff
102678
https://fonts.gstatic.com/s/materialicons/v70/flUhRq6tzZclQEJ-Vdg-IuiaDsNcIhQ8tQ.woff2
99381
https://12prayers.com/images/image02.svg
37142
https://12prayers.com/images/image01.svg
36744
https://code.jquery.com/jquery-3.4.1.min.js
31144
https://12prayers.com/images/image03.svg
28471
Uses efficient cache policy on static assets — 0 resources found
12prayers.com can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
Avoids an excessive DOM size — 143 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
143
Maximum DOM Depth
11
Maximum Child Elements
8
Avoid chaining critical requests — 16 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. 12prayers.com should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
JavaScript execution time — 0.0 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://12prayers.com/
208.364
4.976
1.744
Unattributable
139.468
3.688
0.235
Minimizes main-thread work — 0.5 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Other
143.059
Style & Layout
119.435
Script Evaluation
76.438
Rendering
51.12
Parse HTML & CSS
50.934
Script Parsing & Compilation
30.815
Keep request counts low and transfer sizes small — 32 requests • 1,988 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
32
2035939
Image
12
1207572
Script
6
413298
Font
6
363206
Stylesheet
6
41693
Document
1
9924
Other
1
246
Media
0
0
Third-party
11
540231
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)
360187
0
101093
0
40537
0
31144
0
7270
0
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
img
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.0026838624101525
0.00018557627761725
0.00014444059516457
2.2228059422701E-5
3.470044328278E-6
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 — 2 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://unpkg.com/aos@2.3.1/dist/aos.js
1440
54
https://code.jquery.com/jquery-3.4.1.min.js
770
53
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Avoids large JavaScript libraries with smaller alternatives — 0 large libraries found
It is recommended to work with smaller JavaScript libraries to reduce your bundle size and avoid poor performance.

Budgets

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

Metrics

Speed Index — 1.8 s
The time taken for the page contents to be visibly populated.
Largest Contentful Paint — 2.3 s
The timing of the largest text or image that is painted.

Other

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

Opportunities

Eliminate render-blocking resources — Potential savings of 350 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. 12prayers.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
https://fonts.googleapis.com/css?family=Material+Icons|Material+Icons+Outlined|Material+Icons+Two+Tone|Material+Icons+Round|Material+Icons+Sharp
1712
230
https://stackpath.bootstrapcdn.com/bootstrap/4.4.1/css/bootstrap.min.css
24146
350
https://code.jquery.com/jquery-3.4.1.min.js
31144
350
https://stackpath.bootstrapcdn.com/bootstrap/4.4.1/js/bootstrap.min.js
16391
310
https://unpkg.com/aos@2.3.1/dist/aos.css
2299
230
https://cdnjs.cloudflare.com/ajax/libs/slick-carousel/1.9.0/slick-theme.min.css
1738
230
https://12prayers.com/stylesheets/home.css
11798
150
Properly size images — Potential savings of 788 KiB
Images can slow down the page's load time. 12prayers.com should consider serving more appropriate-sized images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://12prayers.com/images/hero2.2.png
867279
745020
https://12prayers.com/images/icon-hiw-02.png
15894
11921
https://12prayers.com/images/icon-hiw-03.png
15213
11410
https://12prayers.com/images/icon-hiw-01.png
12843
9632
https://12prayers.com/images/icon-hiw-04.png
12262
9197
https://12prayers.com/images/logo.png
8392
7672
https://12prayers.com/images/logo_regular.png
8392
7312
https://12prayers.com/images/logo_icon.png
9698
4686
Serve images in next-gen formats — Potential savings of 858 KiB
Image formats like PNG and JPEG have poor compression when compared to other next-gen formats, such as JPEG 200, JPEG XR and WebP.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://12prayers.com/images/hero2.2.png
867279
747127
https://12prayers.com/images/image00.png
152514
111590
https://12prayers.com/images/icon-hiw-02.png
15894
10332
https://12prayers.com/images/icon-hiw-03.png
15213
9741

Opportunities

Reduce initial server response time — Root document took 820 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://12prayers.com/
823.335

Diagnostics

Ensure text remains visible during webfont load
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
URL Potential Savings (Ms)
https://12prayers.com/stylesheets/fonts/CircularXXWeb-Book.woff
695.91800007038
https://12prayers.com/stylesheets/fonts/CircularXXWeb-Medium.woff
682.68099997658
https://12prayers.com/stylesheets/fonts/tn-regular-webfont.woff2
492.3659999622
https://fonts.gstatic.com/s/materialicons/v70/flUhRq6tzZclQEJ-Vdg-IuiaDsNcIhQ8tQ.woff2
4.2570000514388
https://12prayers.com/stylesheets/fonts/tn-bold-webfont.woff2
493.3439999586
https://12prayers.com/stylesheets/fonts/tt-medium-webfont.woff2
500.13599998783
86

Accessibility

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

Navigation

`[accesskey]` values are unique
Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.
The page contains a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.
`[id]` attributes on active, focusable elements are unique
Ensure all focusable elements have a unique id value to allow them to be visible to users of assistive technologies, like a screen reader.
No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
`[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.
`[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-*]` 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 `[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>`, `<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.
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.

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

Contrast

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

Navigation

Heading elements are not in a sequentially-descending order
Properly order all headers and do not skip heading levels to better the navigation and readability for users of assistive technologies, like a screen reader.
Failing Elements

Names and labels

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.

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

Best Practices

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

Audits

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

Audits

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

Audits

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

Audits

Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.
Avoids Application Cache
Application cache is deprecated and is no longer recommended.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
Bootstrap
4.4.1
jQuery
3.4.1
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
URL Map URL
https://stackpath.bootstrapcdn.com/bootstrap/4.4.1/js/bootstrap.min.js
https://stackpath.bootstrapcdn.com/bootstrap/4.4.1/js/bootstrap.min.js.map

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
http://12prayers.com/
Includes front-end JavaScript libraries with known security vulnerabilities — 2 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
2
Medium

Audits

Browser errors were logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
URL Description
https://12prayers.com/
Refused to apply style from 'https://cdnjs.cloudflare.com/ajax/libs/slick-carousel/1.9.0/slick.min.css.map' because its MIME type ('application/octet-stream') is not a supported stylesheet MIME type, and strict MIME checking is enabled.
https://12prayers.com/
Refused to apply style from 'https://cdnjs.cloudflare.com/ajax/libs/slick-carousel/1.9.0/slick.min.css.map' because its MIME type ('application/octet-stream') is not a supported stylesheet MIME type, and strict MIME checking is enabled.
55

SEO

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

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.

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

Content Best Practices

Document does not have a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.
Links do not have descriptive text — 1 link found
Make use of descriptive link text to assist search engines in understanding the content.

Crawling and Indexing

Links are not 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.
robots.txt is not valid — 46 errors found
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.
Line # Content Error
1
<!DOCTYPE html>
Syntax not understood
2
<html lang="en">
Syntax not understood
3
<head>
Syntax not understood
4
<meta charset="UTF-8">
Syntax not understood
5
<title>12Prayers</title>
Syntax not understood
6
<link rel="icon" type="image/png" href="/images/favicon.png">
Syntax not understood
7
<link href="https://fonts.googleapis.com/css?family=Material+Icons|Material+Icons+Outlined|Material+Icons+Two+Tone|Material+Icons+Round|Material+Icons+Sharp" rel="stylesheet">
Unknown directive
8
<link href="https://stackpath.bootstrapcdn.com/bootstrap/4.4.1/css/bootstrap.min.css"
Unknown directive
9
rel="stylesheet"
Syntax not understood
10
integrity="sha384-Vkoo8x4CGsO3+Hhxv8T/Q5PaXtkKtu6ug5TOeNV6gBiFeWPGFN9MuhOf23Q9Ifjh"
Syntax not understood
11
crossorigin="anonymous" />
Syntax not understood
12
<script
Syntax not understood
13
src="https://code.jquery.com/jquery-3.4.1.min.js"
Unknown directive
14
integrity="sha256-CSXorXvZcTkaix6Yvo6HppcZGetbYMGWSFlBw8HfCJo="
Syntax not understood
15
crossorigin="anonymous">
Syntax not understood
16
</script>
Syntax not understood
17
<script src="https://stackpath.bootstrapcdn.com/bootstrap/4.4.1/js/bootstrap.min.js"
Unknown directive
18
integrity="sha384-wfSDF2E50Y2D1uUdj0O3uMBJnjuUD4Ih7YwaYd1iqfktj0Uod8GCExl3Og8ifwB6"
Syntax not understood
19
crossorigin="anonymous">
Syntax not understood
20
</script>
Syntax not understood
21
<link href="https://unpkg.com/aos@2.3.1/dist/aos.css" rel="stylesheet">
Unknown directive
22
<link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/slick-carousel/1.9.0/slick.min.css.map"
Unknown directive
23
integrity="undefined"
Syntax not understood
24
crossorigin="anonymous"/>
Syntax not understood
25
<link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/slick-carousel/1.9.0/slick-theme.min.css"
Unknown directive
26
integrity="sha256-4hqlsNP9KM6+2eA8VUT0kk4RsMRTeS7QGHIM+MZ5sLY="
Syntax not understood
27
crossorigin="anonymous" />
Syntax not understood
28
<link rel='stylesheet' href='/stylesheets/home.css' />
Syntax not understood
30
</head>
Syntax not understood
31
<body>
Syntax not understood
32
<main>
Syntax not understood
33
<div class="pagenotfound-container">
Syntax not understood
34
<div class="pagenotfound-wrapper">
Syntax not understood
35
<div class="pagenotfound-content">
Syntax not understood
36
<figure>
Syntax not understood
37
<img src="/images/logo_icon.png" alt="">
Syntax not understood
38
</figure>
Syntax not understood
39
<h1><span>Oops!</span>We couldn't find what you were looking for!</h1>
Syntax not understood
40
<p>The page you are looking for might have been removed, had its name changed or temporarily unavailable.</p>
Syntax not understood
41
<a href="/" class="button-cta">go to home</a>
Syntax not understood
42
</div>
Syntax not understood
43
</div>
Syntax not understood
44
</div>
Syntax not understood
45
</main>
Syntax not understood
46
</body>
Syntax not understood
47
</html>
Syntax not understood

Manual Checks

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

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

Fast and reliable

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

PWA Optimized

Redirects HTTP traffic to HTTPS
It is advised to redirect all HTTP traffic to HTTPS, in order to enable secure web features for all users.
Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Contains some content when JavaScript is not available
Apps should display alternative content for when JavaScript is disabled.

Fast and reliable

Current page does not respond with a 200 when offline
In order for Progressive Web Apps to be made available offline, ensure that the app is using a service worker.
`start_url` does not respond with a 200 when offline
Consider using a service worker for Progressive Web Apps to ensure greater reliability for the user, in the case of poor network conditions.

Installable

Does not use HTTPS — 1 insecure request found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL
http://12prayers.com/
Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Web app manifest does not meet the installability requirements
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
View Data

PWA Optimized

Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Does not set a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Does not 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 12prayers.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.
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) 60
Performance 62
Accessibility 86
Best Practices 71
SEO 46
Progressive Web App 36
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
Simulate loading on mobile
62

Performance

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

Metrics

Total Blocking Time — 110 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).
Cumulative Layout Shift — 0.018
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

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 12prayers.com as laggy when the latency is higher than 0.05 seconds.
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://12prayers.com/
0
234.98199996538
234
0
301
text/html
https://12prayers.com/
235.590999946
786.97699983604
9924
44773
200
text/html
Document
https://fonts.googleapis.com/css?family=Material+Icons|Material+Icons+Outlined|Material+Icons+Two+Tone|Material+Icons+Round|Material+Icons+Sharp
824.58699983545
846.15599992685
1612
3025
200
text/css
Stylesheet
https://stackpath.bootstrapcdn.com/bootstrap/4.4.1/css/bootstrap.min.css
824.87799995579
847.75999980047
24146
159515
200
text/css
Stylesheet
https://code.jquery.com/jquery-3.4.1.min.js
825.17299987376
869.10699983127
31144
88145
200
application/javascript
Script
https://stackpath.bootstrapcdn.com/bootstrap/4.4.1/js/bootstrap.min.js
825.40899980813
838.48399994895
16391
60010
200
text/javascript
Script
https://unpkg.com/aos@2.3.1/dist/aos.css
825.56499983184
849.9629998114
2299
26053
200
text/css
Stylesheet
https://cdnjs.cloudflare.com/ajax/libs/slick-carousel/1.9.0/slick.min.css.map
824.86099982634
923.7359999679
0
0
-1
Stylesheet
https://cdnjs.cloudflare.com/ajax/libs/slick-carousel/1.9.0/slick-theme.min.css
826.00299990736
846.91099985503
1736
2390
200
text/css
Stylesheet
https://12prayers.com/stylesheets/home.css
826.10999979079
932.10399989039
11798
80233
200
text/css
Stylesheet
https://12prayers.com/images/logo_regular.png
910.90899985284
1018.6459999532
8694
8392
200
image/png
Image
https://12prayers.com/images/hero2.2.png
911.07799997553
1508.3119999617
867584
867279
200
image/png
Image
https://12prayers.com/images/image00.png
911.52299987152
1309.6109998878
152819
152514
200
image/png
Image
https://12prayers.com/images/icon-hiw-01.png
911.75400000066
1020.8359998651
13146
12843
200
image/png
Image
https://12prayers.com/images/icon-hiw-02.png
911.96800000034
1115.422999952
16197
15894
200
image/png
Image
https://12prayers.com/images/icon-hiw-03.png
912.12299978361
1114.5709999837
15516
15213
200
image/png
Image
https://12prayers.com/images/icon-hiw-04.png
912.32599993236
1021.1879999842
12565
12262
200
image/png
Image
https://12prayers.com/images/image01.svg
912.54399996251
1119.367999956
36744
36437
200
image/svg+xml
Image
https://12prayers.com/images/image02.svg
912.69499994814
1116.0699999891
37142
36835
200
image/svg+xml
Image
https://12prayers.com/images/image03.svg
912.89599984884
1118.8889998011
28471
28164
200
image/svg+xml
Image
https://12prayers.com/images/logo_icon.png
913.069000002
1020.3239999246
10000
9698
200
image/png
Image
https://12prayers.com/images/logo.png
913.35399984382
1021.5319998097
8694
8392
200
image/png
Image
https://unpkg.com/aos@2.3.1/dist/aos.js
909.61299999617
935.14999980107
4971
14239
200
application/javascript
Script
https://cdnjs.cloudflare.com/ajax/libs/slick-carousel/1.9.0/slick.min.js
910.03899998032
929.16499986313
10668
43881
200
application/javascript
Script
https://cdnjs.cloudflare.com/ajax/libs/font-awesome/5.12.1/js/all.min.js
910.43499996886
963.81699992344
347775
1147965
200
application/javascript
Script
https://12prayers.com/javascripts/home.js
910.61799996532
1307.1299998555
2343
2014
200
application/javascript
Script
https://12prayers.com/stylesheets/fonts/CircularXXWeb-Book.woff
944.66499984264
1242.4339998979
102678
102361
200
application/font-woff
Font
https://12prayers.com/stylesheets/fonts/CircularXXWeb-Medium.woff
945.08899981156
1635.6089999899
104331
104014
200
application/font-woff
Font
https://12prayers.com/stylesheets/fonts/tn-regular-webfont.woff2
945.39000000805
1143.9859999809
18820
18504
200
application/font-woff2
Font
https://fonts.gstatic.com/s/materialicons/v70/flUhRq6tzZclQEJ-Vdg-IuiaDsNcIhQ8tQ.woff2
945.5879998859
949.88500000909
99381
98812
200
font/woff2
Font
https://12prayers.com/stylesheets/fonts/tn-bold-webfont.woff2
945.7659998443
1144.4049999118
19200
18884
200
application/font-woff2
Font
https://12prayers.com/stylesheets/fonts/tt-medium-webfont.woff2
946.02699996904
1439.294999931
18796
18480
200
application/font-woff2
Font
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
828.451
20.234
853.264
11.132
883.286
9.467
907.791
41.395
968.115
44.258
1016.745
6.139
1022.901
12.923
1036.234
6.391
1042.653
5.747
1048.432
37.061
1149.68
13.465
1163.219
5.682
1169.1
5.092
1174.228
5.731
1185.402
8.189
1281.308
9.022
1341.671
10.941
1475.044
7.432
1548.928
17.566
1669.76
10.016
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data

Opportunities

Properly size images — Potential savings of 24 KiB
Images can slow down the page's load time. 12prayers.com should consider serving more appropriate-sized images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://12prayers.com/images/hero2.2.png
867279
24839
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. 12prayers.com should consider lazy-loading offscreen and hidden images.
Minify CSS — Potential savings of 3 KiB
Cascading Style Sheets (CSS) files can contribute to network payload sizes. 12prayers.com should consider minifying CSS files.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://12prayers.com/stylesheets/home.css
11798
3139
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. 12prayers.com should consider minifying JS files.
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Enable text compression — Potential savings of 1 KiB
Text-based resources should be served with compression, such as gzip, deflate or brotli.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://12prayers.com/javascripts/home.js
2014
1450
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 550 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://12prayers.com/
552.383
Avoid multiple page redirects — Potential savings of 630 ms
Redirects can cause additional delays before the page can begin loading. 12prayers.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://12prayers.com/
630
https://12prayers.com/
0
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers — Potential savings of 0 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
URL Potential Savings (Bytes)
https://unpkg.com/aos@2.3.1/dist/aos.js
58
https://cdnjs.cloudflare.com/ajax/libs/font-awesome/5.12.1/js/all.min.js
51

Diagnostics

Avoids enormous network payloads — Total size was 1,988 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://12prayers.com/images/hero2.2.png
867584
https://cdnjs.cloudflare.com/ajax/libs/font-awesome/5.12.1/js/all.min.js
347775
https://12prayers.com/images/image00.png
152819
https://12prayers.com/stylesheets/fonts/CircularXXWeb-Medium.woff
104331
https://12prayers.com/stylesheets/fonts/CircularXXWeb-Book.woff
102678
https://fonts.gstatic.com/s/materialicons/v70/flUhRq6tzZclQEJ-Vdg-IuiaDsNcIhQ8tQ.woff2
99381
https://12prayers.com/images/image02.svg
37142
https://12prayers.com/images/image01.svg
36744
https://code.jquery.com/jquery-3.4.1.min.js
31144
https://12prayers.com/images/image03.svg
28471
Uses efficient cache policy on static assets — 0 resources found
12prayers.com can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
Avoids an excessive DOM size — 143 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
143
Maximum DOM Depth
11
Maximum Child Elements
8
Avoid chaining critical requests — 16 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. 12prayers.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.3 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://12prayers.com/
643.284
10.468
8
Unattributable
381.244
12.948
3.904
https://cdnjs.cloudflare.com/ajax/libs/font-awesome/5.12.1/js/all.min.js
163.268
50.108
87.564
https://code.jquery.com/jquery-3.4.1.min.js
152.336
124.12
6.484
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)
Other
484.664
Style & Layout
297.856
Script Evaluation
230.192
Rendering
175.34
Parse HTML & CSS
136.504
Script Parsing & Compilation
120.696
Keep request counts low and transfer sizes small — 32 requests • 1,988 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
32
2035819
Image
12
1207572
Script
6
413292
Font
6
363206
Stylesheet
6
41591
Document
1
9924
Other
1
234
Media
0
0
Third-party
11
540123
Minimize third-party usage — Third-party code blocked the main thread for 70 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)
360179
37.028
31144
35.876
100993
0
40537
0
7270
0
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
img
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.012302397449304
0.0051884905222766
8.2641932904247E-5
12
9.8028719210743E-6
9.8028719210743E-6
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 — 7 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://code.jquery.com/jquery-3.4.1.min.js
3090
166
https://cdnjs.cloudflare.com/ajax/libs/font-awesome/5.12.1/js/all.min.js
6870
148
https://12prayers.com/
1236
89
https://12prayers.com/
1110
81
https://12prayers.com/
736
70
Unattributable
682
54
Unattributable
630
52
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Avoids large JavaScript libraries with smaller alternatives — 0 large libraries found
It is recommended to work with smaller JavaScript libraries to reduce your bundle size and avoid poor performance.

Budgets

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

Metrics

First Contentful Paint — 3.3 s
The time taken for the first image or text on the page to be rendered.
Speed Index — 3.8 s
The time taken for the page contents to be visibly populated.
Time to Interactive — 7.0 s
The time taken for the page to become fully interactive.

Other

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

Opportunities

Remove unused CSS — Potential savings of 23 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. 12prayers.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://stackpath.bootstrapcdn.com/bootstrap/4.4.1/css/bootstrap.min.css
24146
23844
Remove unused JavaScript — Potential savings of 21 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://code.jquery.com/jquery-3.4.1.min.js
31144
21130

Metrics

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

Other

First CPU Idle — 7.0 s
The time taken for the page's main thread to be quiet enough to handle input.
First Meaningful Paint — 4.8 s
The time taken for the primary content of the page to be rendered.
First Contentful Paint (3G) — 6720 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 1,380 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. 12prayers.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
https://fonts.googleapis.com/css?family=Material+Icons|Material+Icons+Outlined|Material+Icons+Two+Tone|Material+Icons+Round|Material+Icons+Sharp
1612
780
https://stackpath.bootstrapcdn.com/bootstrap/4.4.1/css/bootstrap.min.css
24146
1380
https://code.jquery.com/jquery-3.4.1.min.js
31144
1530
https://stackpath.bootstrapcdn.com/bootstrap/4.4.1/js/bootstrap.min.js
16391
1230
https://unpkg.com/aos@2.3.1/dist/aos.css
2299
780
https://cdnjs.cloudflare.com/ajax/libs/slick-carousel/1.9.0/slick-theme.min.css
1736
780
https://12prayers.com/stylesheets/home.css
11798
780
Serve images in next-gen formats — Potential savings of 858 KiB
Image formats like PNG and JPEG have poor compression when compared to other next-gen formats, such as JPEG 200, JPEG XR and WebP.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://12prayers.com/images/hero2.2.png
867279
747127
https://12prayers.com/images/image00.png
152514
111590
https://12prayers.com/images/icon-hiw-02.png
15894
10332
https://12prayers.com/images/icon-hiw-03.png
15213
9741
Preload key requests — Potential savings of 930 ms
Key requests can be preloaded by using '<link rel=preload>'. 12prayers.com should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
URL Potential Savings (Ms)
https://12prayers.com/stylesheets/fonts/CircularXXWeb-Book.woff
930
https://12prayers.com/stylesheets/fonts/tt-medium-webfont.woff2
930
https://12prayers.com/stylesheets/fonts/CircularXXWeb-Medium.woff
780
https://12prayers.com/stylesheets/fonts/tn-regular-webfont.woff2
630
https://12prayers.com/stylesheets/fonts/tn-bold-webfont.woff2
480

Diagnostics

Ensure text remains visible during webfont load
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
URL Potential Savings (Ms)
https://12prayers.com/stylesheets/fonts/CircularXXWeb-Book.woff
297.76900005527
https://12prayers.com/stylesheets/fonts/CircularXXWeb-Medium.woff
690.52000017837
https://12prayers.com/stylesheets/fonts/tn-regular-webfont.woff2
198.59599997289
https://fonts.gstatic.com/s/materialicons/v70/flUhRq6tzZclQEJ-Vdg-IuiaDsNcIhQ8tQ.woff2
4.2970001231879
https://12prayers.com/stylesheets/fonts/tn-bold-webfont.woff2
198.63900006749
https://12prayers.com/stylesheets/fonts/tt-medium-webfont.woff2
493.26799996197
86

Accessibility

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

Navigation

`[accesskey]` values are unique
Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.
The page contains a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.
`[id]` attributes on active, focusable elements are unique
Ensure all focusable elements have a unique id value to allow them to be visible to users of assistive technologies, like a screen reader.
No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
`[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.
`[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-*]` 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 `[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>`, `<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.
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.

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

Contrast

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

Navigation

Heading elements are not in a sequentially-descending order
Properly order all headers and do not skip heading levels to better the navigation and readability for users of assistive technologies, like a screen reader.
Failing Elements

Names and labels

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.

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

Best Practices

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

Audits

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

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.
Fonts with `font-display: optional` are preloaded
It is recommended that optional fonts are preloaded.

Audits

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

Audits

Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.
Avoids Application Cache
Application cache is deprecated and is no longer recommended.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
Bootstrap
4.4.1
jQuery
3.4.1
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
URL Map URL
https://stackpath.bootstrapcdn.com/bootstrap/4.4.1/js/bootstrap.min.js
https://stackpath.bootstrapcdn.com/bootstrap/4.4.1/js/bootstrap.min.js.map

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
http://12prayers.com/
Includes front-end JavaScript libraries with known security vulnerabilities — 2 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
2
Medium

Audits

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://12prayers.com/images/image00.png
940 x 732
940 x 732
2468 x 1922

Audits

Browser errors were logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
URL Description
https://12prayers.com/
Refused to apply style from 'https://cdnjs.cloudflare.com/ajax/libs/slick-carousel/1.9.0/slick.min.css.map' because its MIME type ('application/octet-stream') is not a supported stylesheet MIME type, and strict MIME checking is enabled.
https://12prayers.com/
Refused to apply style from 'https://cdnjs.cloudflare.com/ajax/libs/slick-carousel/1.9.0/slick.min.css.map' because its MIME type ('application/octet-stream') is not a supported stylesheet MIME type, and strict MIME checking is enabled.
46

SEO

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

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.

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 12prayers.com on mobile screens.
Document doesn't use 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 not 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 does not have a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.
Links do not have descriptive text — 1 link found
Make use of descriptive link text to assist search engines in understanding the content.

Crawling and Indexing

Links are not 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.
robots.txt is not valid — 46 errors found
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.
Line # Content Error
1
<!DOCTYPE html>
Syntax not understood
2
<html lang="en">
Syntax not understood
3
<head>
Syntax not understood
4
<meta charset="UTF-8">
Syntax not understood
5
<title>12Prayers</title>
Syntax not understood
6
<link rel="icon" type="image/png" href="/images/favicon.png">
Syntax not understood
7
<link href="https://fonts.googleapis.com/css?family=Material+Icons|Material+Icons+Outlined|Material+Icons+Two+Tone|Material+Icons+Round|Material+Icons+Sharp" rel="stylesheet">
Unknown directive
8
<link href="https://stackpath.bootstrapcdn.com/bootstrap/4.4.1/css/bootstrap.min.css"
Unknown directive
9
rel="stylesheet"
Syntax not understood
10
integrity="sha384-Vkoo8x4CGsO3+Hhxv8T/Q5PaXtkKtu6ug5TOeNV6gBiFeWPGFN9MuhOf23Q9Ifjh"
Syntax not understood
11
crossorigin="anonymous" />
Syntax not understood
12
<script
Syntax not understood
13
src="https://code.jquery.com/jquery-3.4.1.min.js"
Unknown directive
14
integrity="sha256-CSXorXvZcTkaix6Yvo6HppcZGetbYMGWSFlBw8HfCJo="
Syntax not understood
15
crossorigin="anonymous">
Syntax not understood
16
</script>
Syntax not understood
17
<script src="https://stackpath.bootstrapcdn.com/bootstrap/4.4.1/js/bootstrap.min.js"
Unknown directive
18
integrity="sha384-wfSDF2E50Y2D1uUdj0O3uMBJnjuUD4Ih7YwaYd1iqfktj0Uod8GCExl3Og8ifwB6"
Syntax not understood
19
crossorigin="anonymous">
Syntax not understood
20
</script>
Syntax not understood
21
<link href="https://unpkg.com/aos@2.3.1/dist/aos.css" rel="stylesheet">
Unknown directive
22
<link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/slick-carousel/1.9.0/slick.min.css.map"
Unknown directive
23
integrity="undefined"
Syntax not understood
24
crossorigin="anonymous"/>
Syntax not understood
25
<link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/slick-carousel/1.9.0/slick-theme.min.css"
Unknown directive
26
integrity="sha256-4hqlsNP9KM6+2eA8VUT0kk4RsMRTeS7QGHIM+MZ5sLY="
Syntax not understood
27
crossorigin="anonymous" />
Syntax not understood
28
<link rel='stylesheet' href='/stylesheets/home.css' />
Syntax not understood
30
</head>
Syntax not understood
31
<body>
Syntax not understood
32
<main>
Syntax not understood
33
<div class="pagenotfound-container">
Syntax not understood
34
<div class="pagenotfound-wrapper">
Syntax not understood
35
<div class="pagenotfound-content">
Syntax not understood
36
<figure>
Syntax not understood
37
<img src="/images/logo_icon.png" alt="">
Syntax not understood
38
</figure>
Syntax not understood
39
<h1><span>Oops!</span>We couldn't find what you were looking for!</h1>
Syntax not understood
40
<p>The page you are looking for might have been removed, had its name changed or temporarily unavailable.</p>
Syntax not understood
41
<a href="/" class="button-cta">go to home</a>
Syntax not understood
42
</div>
Syntax not understood
43
</div>
Syntax not understood
44
</div>
Syntax not understood
45
</main>
Syntax not understood
46
</body>
Syntax not understood
47
</html>
Syntax not understood

Manual Checks

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

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

Fast and reliable

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

PWA Optimized

Redirects HTTP traffic to HTTPS
It is advised to redirect all HTTP traffic to HTTPS, in order to enable secure web features for all users.
Contains some content when JavaScript is not available
Apps should display alternative content for when JavaScript is disabled.

Fast and reliable

Current page does not respond with a 200 when offline
In order for Progressive Web Apps to be made available offline, ensure that the app is using a service worker.
`start_url` does not respond with a 200 when offline
Consider using a service worker for Progressive Web Apps to ensure greater reliability for the user, in the case of poor network conditions.

Installable

Does not use HTTPS — 1 insecure request found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL
http://12prayers.com/
Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Web app manifest does not meet the installability requirements
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
View Data

PWA Optimized

Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Does not set a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Content is not 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.
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 12prayers.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.
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: 46.28.206.115
Continent: Europe
Country: Switzerland
Switzerland Flag
Region:
City:
Longitude: 8.1551
Latitude: 47.1449
Currencies: CHE
CHF
CHW
Languages: French
Swiss German
Italian
Romansh

Web Hosting Provider

Registration

Domain Registrant

Private Registration: Yes
Name: REDACTED FOR PRIVACY
Organization: REDACTED FOR PRIVACY
Country: BG
City: REDACTED FOR PRIVACY
State: england
Post Code: REDACTED FOR PRIVACY
Email:
Phone: REDACTED FOR PRIVACY
Note: Registration information is derived from various sources and may be inaccurate.

Domain Registrar

Name IP Address
REALTIME REGISTER B.V. 109.235.74.210
Security

Visitor Safety

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

SSL/TLS Certificate

Issued To: 12prayers.com
Issued By: R3
Valid From: 22nd December, 2020
Valid To: 22nd March, 2021
Subject: CN = 12prayers.com
Hash: 59fffe6e
Issuer: CN = R3
O = Let's Encrypt
S = US
Version: 2
Serial Number: 0x03A3BFDC4D48FC130FE1EA9EA8BD0324024E
Serial Number (Hex): 03A3BFDC4D48FC130FE1EA9EA8BD0324024E
Valid From: 22nd December, 2024
Valid To: 22nd March, 2024
Signature Algorithm (Short Name): RSA-SHA256
Signature Algorithm (Long Name): sha256WithRSAEncryption
Authority Key Identifier: keyid:14:2E:B3:17:B7:58:56:CB:AE:50:09:40:E6:1F:AF:9D:8B:14:C2:C6
Extended Key Usage: TLS Web Server Authentication, TLS Web Client Authentication
Certificate Policies: Policy: 2.23.140.1.2.1
Policy: 1.3.6.1.4.1.44947.1.1.1
CPS: http://cps.letsencrypt.org

Authority Information Access: OCSP - URI:http://r3.o.lencr.org
CA Issuers - URI:http://r3.i.lencr.org/

SCT List: Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 7D:3E:F2:F8:8F:FF:88:55:68:24:C2:C0:CA:9E:52:89:
79:2B:C5:0E:78:09:7F:2E:6A:97:68:99:7E:22:F0:D7
Timestamp : Dec 22 15:02:26.273 2020 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:21:00:CF:54:0A:EE:46:09:74:DF:8C:A8:2D:
3D:FD:15:7B:EB:1B:C3:49:AA:10:9E:19:C8:C0:54:F1:
7D:2C:94:10:46:02:20:0C:CC:04:28:69:CF:90:D0:E7:
68:77:DB:A4:F6:B2:F3:B6:8F:63:43:A3:F5:02:9E:E4:
9E:CF:6B:5F:43:DC:9B
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 6F:53:76:AC:31:F0:31:19:D8:99:00:A4:51:15:FF:77:
15:1C:11:D9:02:C1:00:29:06:8D:B2:08:9A:37:D9:13
Timestamp : Dec 22 15:02:26.386 2020 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:20:66:FF:F4:F9:60:46:4A:43:2C:0C:0B:68:
2F:A0:83:D4:F1:7B:D9:32:B7:60:BF:CE:DB:B9:BD:1D:
4E:90:41:0C:02:21:00:D3:24:85:46:4A:A1:7A:4F:37:
03:E2:52:4B:A9:8C:0C:54:52:49:57:22:72:72:EF:19:
A4:9D:3D:BA:E7:16:A4
Key Usage: Digital Signature, Key Encipherment
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:api.12prayers.com
DNS:app.12prayers.com
DNS:h3av3n.12prayers.com
DNS:support.12prayers.com
DNS:www.12prayers.com
DNS:12prayers.com
Technical

DNS Lookup

A Records

Host IP Address Class TTL
12prayers.com. 46.28.206.115 IN 10799

NS Records

Host Nameserver Class TTL
12prayers.com. ns.prq.se. IN 10799
12prayers.com. ns2.prq.se. IN 10799

MX Records

Priority Host Server Class TTL
10 12prayers.com. smtp.prq.se. IN 10799

SOA Records

Domain Name Primary NS Responsible Email TTL
12prayers.com. ns.prq.se. registry.prq.se. 10799

TXT Records

Host Value Class TTL
12prayers.com. v=spf1 IN 10799

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Server: nginx/1.17.3
Date: 27th January, 2021
Content-Type: text/html; charset=utf-8
Content-Length: 44773
Connection: keep-alive
Vary: Accept-Encoding
X-Powered-By: Express
ETag: W/"aee5-IWOqPu2LYq01zPS/jrazujpu5CM"

Whois Lookup

Created: 26th January, 2020
Changed: 2nd January, 2021
Expires: 26th January, 2024
Registrar: REALTIME REGISTER B.V.
Status: ok
Nameservers: ns.prq.se
ns2.prq.se
Owner Name: REDACTED FOR PRIVACY
Owner Organization: REDACTED FOR PRIVACY
Owner Street: REDACTED FOR PRIVACY
Owner Post Code: REDACTED FOR PRIVACY
Owner City: REDACTED FOR PRIVACY
Owner Country: SE
Owner Phone: REDACTED FOR PRIVACY
Owner Email: https://mydomainprovider.com/contact_domain/
Admin Name: REDACTED FOR PRIVACY
Admin Organization: REDACTED FOR PRIVACY
Admin Street: REDACTED FOR PRIVACY
Admin Post Code: REDACTED FOR PRIVACY
Admin City: REDACTED FOR PRIVACY
Admin State: REDACTED FOR PRIVACY
Admin Country: REDACTED FOR PRIVACY
Admin Phone: REDACTED FOR PRIVACY
Admin Email: https://mydomainprovider.com/contact_domain/
Tech Name: REDACTED FOR PRIVACY
Tech Organization: REDACTED FOR PRIVACY
Tech Street: REDACTED FOR PRIVACY
Tech Post Code: REDACTED FOR PRIVACY
Tech City: REDACTED FOR PRIVACY
Tech State: REDACTED FOR PRIVACY
Tech Country: REDACTED FOR PRIVACY
Tech Phone: REDACTED FOR PRIVACY
Tech Email: https://mydomainprovider.com/contact_domain/
Full Whois: Domain Name: 12prayers.com
Registry Domain ID: 2484811413_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.yoursrs.com
Registrar URL: http://www.realtimeregister.com
Updated Date: 2021-01-02T05:00:42Z
Creation Date: 2020-01-26T12:46:38Z
Registrar Registration Expiration Date: 2024-01-26T12:46:38Z
Registrar: REALTIME REGISTER B.V.
Registrar IANA ID: 839
Reseller: EgenSajt Hosting AB
Domain Status: ok http://www.icann.org/epp#ok
Registry Registrant ID: REDACTED FOR PRIVACY
Registrant Name: REDACTED FOR PRIVACY
Registrant Organization: REDACTED FOR PRIVACY
Registrant Street: REDACTED FOR PRIVACY
Registrant City: REDACTED FOR PRIVACY
Registrant State/Province:
Registrant Postal Code: REDACTED FOR PRIVACY
Registrant Country: SE
Registrant Phone: REDACTED FOR PRIVACY
Registrant Phone Ext: REDACTED FOR PRIVACY
Registrant Fax: REDACTED FOR PRIVACY
Registrant Fax Ext: REDACTED FOR PRIVACY
Registrant Email: https://mydomainprovider.com/contact_domain/
Registry Admin ID: REDACTED FOR PRIVACY
Admin Name: REDACTED FOR PRIVACY
Admin Organization: REDACTED FOR PRIVACY
Admin Street: REDACTED FOR PRIVACY
Admin City: REDACTED FOR PRIVACY
Admin State/Province: REDACTED FOR PRIVACY
Admin Postal Code: REDACTED FOR PRIVACY
Admin Country: REDACTED FOR PRIVACY
Admin Phone: REDACTED FOR PRIVACY
Admin Phone Ext: REDACTED FOR PRIVACY
Admin Fax: REDACTED FOR PRIVACY
Admin Fax Ext: REDACTED FOR PRIVACY
Admin Email: https://mydomainprovider.com/contact_domain/
Registry Tech ID: REDACTED FOR PRIVACY
Tech Name: REDACTED FOR PRIVACY
Tech Organization: REDACTED FOR PRIVACY
Tech Street: REDACTED FOR PRIVACY
Tech City: REDACTED FOR PRIVACY
Tech State/Province: REDACTED FOR PRIVACY
Tech Postal Code: REDACTED FOR PRIVACY
Tech Country: REDACTED FOR PRIVACY
Tech Phone: REDACTED FOR PRIVACY
Tech Phone Ext: REDACTED FOR PRIVACY
Tech Fax: REDACTED FOR PRIVACY
Tech Fax Ext: REDACTED FOR PRIVACY
Tech Email: https://mydomainprovider.com/contact_domain/
Name Server: ns.prq.se
Name Server: ns2.prq.se
DNSSEC: not signed
Registrar Abuse Contact Email: abuse[at]realtimeregister.com
Registrar Abuse Contact Phone: +31.384530759
URL of the ICANN WHOIS Data Problem Reporting System:
http://wdprs.internic.net/
>>> Last update of WHOIS database: 2021-01-27T16:04:39Z <<<

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

Please email the listed admin email address if you wish to raise a legal issue.

The data in this whois database is provided to you for information purposes only, that is,
to assist you in obtaining information about or related to a domain name registration record.
We make this information available "as is," and do not guarantee its accuracy.
By submitting a whois query, you agree that you will use this data only for lawful purposes and that, under no circumstances will you use this data to:
(1) enable high volume, automated, electronic processes that stress or load this whois database system providing you this information; or
(2) allow, enable, or otherwise support the transmission of mass unsolicited, commercial advertising or solicitations via direct mail,
electronic mail, or by telephone. The compilation, repackaging, dissemination or other use of this data is expressly prohibited without
prior written consent from REALTIME REGISTER B.V.


Nameservers

Name IP Address
ns.prq.se 193.104.214.194
ns2.prq.se 88.80.30.194
Related

Subdomains

Similar Sites

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Sites hosted on the same IP address