frendz4m.in

frendz4m.in is SSL secured

Free website and domain report on frendz4m.in

Last Updated: 13th June, 2023 Update Now
Overview

Snoop Summary for frendz4m.in

This is a free and comprehensive report about frendz4m.in. The domain frendz4m.in is currently hosted on a server located in Dallas, Texas in United States with the IP address 45.56.79.23, where the local currency is USD and English is the local language. If frendz4m.in was to be sold it would possibly be worth $626 USD (based on the daily revenue potential of the website over a 24 month period). Frendz4m.in receives an estimated 296 unique visitors every day - a decent amount of traffic! This report was last updated 13th June, 2023.

What is frendz4m.in?

Frendz4m.in enables you to watch or download movies and tv series online, including full feature films. We advise against visiting websites like frendz4m.in due to their potentially illegal/unsafe content.

About frendz4m.in

Site Preview: frendz4m.in frendz4m.in
Title:
Description:
Keywords and Tags: bollywood movies, bollywood tv shows, download movies, download tv shows, full feature films, hollywood movies, hollywood tv shows, potential illegal software, watch movies, watch tv shows
Related Terms:
Fav Icon:
Age:
Domain Created:
Domain Updated:
Domain Expires:
Review

Snoop Score

1/5

Valuation

$626 USD
Note: All valuation figures are estimates.

Popularity

Low
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 4,721,062
Alexa Reach:
SEMrush Rank (US):
SEMrush Authority Score:
Moz Domain Authority: 17
Moz Page Authority: 28

Organic vs Paid (Google Ads)

Traffic

Visitors

Daily Visitors: 296
Monthly Visitors: 9,009
Yearly Visitors: 108,040
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $1 USD
Monthly Revenue: $26 USD
Yearly Revenue: $308 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: frendz4m.in 11
Domain Name: frendz4m 8
Extension (TLD): in 2

Page Speed Analysis

Average Load Time: 1.07 seconds
Load Time Comparison: Faster than 76% of sites

PageSpeed Insights

Avg. (All Categories) 63
Performance 88
Accessibility 56
Best Practices 64
SEO 73
Progressive Web App 33
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
Simulate loading on desktop
88

Performance

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

Metrics

First Contentful Paint — 0.5 s
The time taken for the first image or text on the page to be rendered.
Speed Index — 1.2 s
The time taken for the page contents to be visibly populated.
Largest Contentful Paint — 1.0 s
The timing of the largest text or image that is painted.
Time to Interactive — 1.7 s
The time taken for the page to become fully interactive.
Cumulative Layout Shift — 0.038
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

First CPU Idle — 1.6 s
The time taken for the page's main thread to be quiet enough to handle input.
First Meaningful Paint — 0.9 s
The time taken for the primary content of the page to be rendered.
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 frendz4m.in 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://frendz4m.in/
0
56.656999979168
684
725
200
text/html
Document
http://i.cdnpark.com/themes/registrar/852261.css
72.960000019521
99.030000041239
1294
2472
200
text/css
Stylesheet
http://i.cdnpark.com/registrar/v3/loader.js
73.236000025645
98.288999986835
2583
2195
200
text/javascript
Script
http://frendz4m.in/hp_script.js
73.496000026353
116.12899997272
684
725
200
text/html
Script
http://d1lxhc4jvstzrp.cloudfront.net/registrar/v3/content/852261
112.91300004814
132.29600002524
3084
2696
200
text/javascript
Script
http://js.parkingcrew.net/jsparkcaf.php?_v=3&regcn=852261&_h=frendz4m.in&_t=1601487248967&_qs=
113.99400001392
255.67300000694
5675
5425
200
text/javascript
Script
http://d1lxhc4jvstzrp.cloudfront.net/themes/registrar/images/logo_dynadot2.png
136.58399996348
178.98900003638
20089
19647
200
image/png
Image
http://www.google.com/adsense/domains/caf.js
260.32800006215
279.97499995399
62362
176587
200
text/javascript
Script
http://js.parkingcrew.net/assets/scripts/jsparkcaf.js
260.61999995727
574.95699997526
5884
5638
200
application/javascript
Script
http://js.parkingcrew.net/ls.php
261.81000005454
400.21800005343
345
0
201
text/javascript
XHR
http://js.parkingcrew.net/track.php?domain=frendz4m.in&toggle=browserjs&uid=MTYwMTQ4NzI0OS4wNTc4OjFhYTg1YTRlZGFkOTgwNGNjNDE1NjE3ZjNkMmYwMzkxMzExYWY5YmU3Mzk0NjQ1MTc3OWU1NTc3MmVkODI4ZTQ6NWY3NGMxOTEwZTFkYw%3D%3D
580.97200002521
694.81899996754
300
0
200
text/html
XHR
http://js.parkingcrew.net/assets/scripts/registrar-caf/852261.js
697.14199996088
804.47500001173
3327
3082
200
application/javascript
Script
https://www.google.com/afs/ads/i/iframe.html
835.34700004384
840.38199996576
1687
1243
200
text/html
Document
https://www.google.com/dp/ads?max_radlink_len=40&r=m&client=dp-teaminternet09_3ph&channel=000001&hl=en&adtest=off&type=3&pcsa=false&swp=as-drid-2997149969328928&uiopt=false&oe=UTF-8&ie=UTF-8&fexp=21404&format=r10%7Cs&num=0&output=afd_ads&domain_name=frendz4m.in&v=3&adext=as1%2Csr1&bsl=8&u_his=2&u_tz=-420&dt=1601487249684&u_w=800&u_h=600&biw=1350&bih=940&psw=1350&psh=208&frm=0&uio=ff2sa16fa2sl1sr1-st22sa14lt33-&cont=tc&csize=w400h0&inames=master-1&jsv=71661&rurl=http%3A%2F%2Ffrendz4m.in%2F
845.92100000009
945.10500004981
8354
11065
200
text/html
Document
https://www.google.com/adsense/domains/caf.js
960.60200000647
980.02600006294
64008
176629
200
text/javascript
Script
https://afs.googleusercontent.com/dp-teaminternet/arr_1e88e5.png
1050.0010000542
1052.9160000151
1695
1136
200
image/png
Image
http://js.parkingcrew.net/track.php?domain=frendz4m.in&caf=1&toggle=answercheck&answer=yes&uid=MTYwMTQ4NzI0OS4wNTc4OjFhYTg1YTRlZGFkOTgwNGNjNDE1NjE3ZjNkMmYwMzkxMzExYWY5YmU3Mzk0NjQ1MTc3OWU1NTc3MmVkODI4ZTQ6NWY3NGMxOTEwZTFkYw%3D%3D
1054.6570000006
1163.3800000418
302
0
200
text/html
XHR
https://www.google.com/js/bg/LfFQ5hcFG3hXPsOLdOnrUHUTGTSsMRvOgIlCDTigNb8.js
1174.9680000357
1179.1910000611
6585
13716
200
text/javascript
Script
https://www.google.com/afs/gen_204?client=dp-teaminternet09_3ph&output=uds_ads_only&zx=2bstntw7bdtc&aqid=kcF0X57uLoqemgSGtZuIBg&pbt=bo&adbn=master-1&uio=|12|13|8|||http%3A%2F%2Fafs.googleusercontent.com%2Fdp-teaminternet%2Farr_1e88e5.png|17||||||||||%231e88e5||%23aaaaaa|transparent||||||%231e88e5|1|||||arial|arial||14||||22||||||33|||||true||||||%233bb000|||true|true|true|3||tc||relatedsearch|||400|true|
1207.3810000438
1228.031000006
545
0
204
text/html
Image
https://www.google.com/afs/gen_204?client=dp-teaminternet09_3ph&output=uds_ads_only&zx=8je8zeyhgzt3&pbt=bo&adbn=slave-1-1&uio=|||||||||||||||||||%23b7b7b7|transparent||||||||||||arial|arial||16||||||||||||||||||||||||true|true||||form||searchbox|||300|true|
1207.7050000662
1228.5629999824
545
0
204
text/html
Image
https://www.google.com/js/bg/LfFQ5hcFG3hXPsOLdOnrUHUTGTSsMRvOgIlCDTigNb8.js
1209.5490000211
1213.4460000088
6585
13716
200
text/javascript
Script
https://www.google.com/afs/gen_204?client=dp-teaminternet09_3ph&output=uds_ads_only&zx=h5e8oxlgvbf0&aqid=kcF0X57uLoqemgSGtZuIBg&pbt=bs&adbx=275&adby=180&adbh=406&adbw=400&adbn=master-1&eawp=partner-dp-teaminternet09_3ph&errv=7166121592703734751&csadii=26&csadr=362&pblt=1&lle=0&llm=0&ifv=1
2705.1780000329
2723.2300000032
545
0
204
text/html
Image
https://www.google.com/afs/gen_204?client=dp-teaminternet09_3ph&output=uds_ads_only&zx=x1afjky4piby&pbt=bs&adbx=775&adby=180&adbh=36&adbw=300&adbn=slave-1-1&eawp=partner-dp-teaminternet09_3ph&errv=7166121592703734751&csadii=17&csadr=375&pblt=1&lle=0&llm=0&ifv=1
2707.0639999583
2729.6370000113
545
0
204
text/html
Image
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)
114.276
10.837
347.223
11.628
630.938
120.88
860.75
42.417
905.358
9.719
1003.358
9.093
1045.822
60.628
1107.109
111.855
1218.98
7.68
1235.404
15.496
1253.096
9.457
1264.412
8.207
1273.036
131.586
1408.238
6.452
1416.427
116.749
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data

Opportunities

Eliminate render-blocking resources — Potential savings of 0 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Frendz4m.in should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
http://i.cdnpark.com/themes/registrar/852261.css
1294
190
Properly size images
Images can slow down the page's load time. Frendz4m.in should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Frendz4m.in should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Frendz4m.in should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Frendz4m.in should consider minifying JS files.
Remove unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Frendz4m.in should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Remove unused JavaScript — Potential savings of 74 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
http://www.google.com/adsense/domains/caf.js
62362
40024
https://www.google.com/adsense/domains/caf.js
64008
35936
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats — Potential savings of 16 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)
http://d1lxhc4jvstzrp.cloudfront.net/themes/registrar/images/logo_dynadot2.png
19647
15925
Enable text compression — Potential savings of 10 KiB
Text-based resources should be served with compression, such as gzip, deflate or brotli.
URL Transfer Size (Bytes) Potential Savings (Bytes)
http://js.parkingcrew.net/assets/scripts/jsparkcaf.js
5638
3905
http://js.parkingcrew.net/jsparkcaf.php?_v=3&regcn=852261&_h=frendz4m.in&_t=1601487248967&_qs=
5425
2535
http://js.parkingcrew.net/assets/scripts/registrar-caf/852261.js
3082
2149
http://d1lxhc4jvstzrp.cloudfront.net/registrar/v3/content/852261
2696
1911
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 60 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)
http://frendz4m.in/
57.642
Avoid multiple page redirects
Redirects can cause additional delays before the page can begin loading. Frendz4m.in should avoid multiple or unnecessary page redirects.
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Frendz4m.in should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.

Diagnostics

Avoids enormous network payloads — Total size was 193 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://www.google.com/adsense/domains/caf.js
64008
http://www.google.com/adsense/domains/caf.js
62362
http://d1lxhc4jvstzrp.cloudfront.net/themes/registrar/images/logo_dynadot2.png
20089
https://www.google.com/dp/ads?max_radlink_len=40&r=m&client=dp-teaminternet09_3ph&channel=000001&hl=en&adtest=off&type=3&pcsa=false&swp=as-drid-2997149969328928&uiopt=false&oe=UTF-8&ie=UTF-8&fexp=21404&format=r10%7Cs&num=0&output=afd_ads&domain_name=frendz4m.in&v=3&adext=as1%2Csr1&bsl=8&u_his=2&u_tz=-420&dt=1601487249684&u_w=800&u_h=600&biw=1350&bih=940&psw=1350&psh=208&frm=0&uio=ff2sa16fa2sl1sr1-st22sa14lt33-&cont=tc&csize=w400h0&inames=master-1&jsv=71661&rurl=http%3A%2F%2Ffrendz4m.in%2F
8354
https://www.google.com/js/bg/LfFQ5hcFG3hXPsOLdOnrUHUTGTSsMRvOgIlCDTigNb8.js
6585
https://www.google.com/js/bg/LfFQ5hcFG3hXPsOLdOnrUHUTGTSsMRvOgIlCDTigNb8.js
6585
http://js.parkingcrew.net/assets/scripts/jsparkcaf.js
5884
http://js.parkingcrew.net/jsparkcaf.php?_v=3&regcn=852261&_h=frendz4m.in&_t=1601487248967&_qs=
5675
http://js.parkingcrew.net/assets/scripts/registrar-caf/852261.js
3327
http://d1lxhc4jvstzrp.cloudfront.net/registrar/v3/content/852261
3084
Avoids an excessive DOM size — 36 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
36
Maximum DOM Depth
10
Maximum Child Elements
12
Avoid chaining critical requests — 6 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Frendz4m.in 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.6 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://www.google.com/adsense/domains/caf.js
319.903
296.521
9.347
http://js.parkingcrew.net/assets/scripts/jsparkcaf.js
158.196
152.535
0.703
http://www.google.com/adsense/domains/caf.js
135.789
125.735
4.675
Minimizes main-thread work — 0.7 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Script Evaluation
603.602
Other
63.312
Script Parsing & Compilation
25.105
Style & Layout
23.235
Parse HTML & CSS
15.161
Rendering
11.861
Garbage Collection
6.393
All text remains visible during webfont loads
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
Keep request counts low and transfer sizes small — 23 requests • 193 KiB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.
Resource Type Requests Transfer Size (Bytes)
Total
23
197707
Script
10
160777
Image
6
23964
Document
3
10725
Stylesheet
1
1294
Other
3
947
Media
0
0
Font
0
0
Third-party
21
196339
Minimize third-party usage — Third-party code blocked the main thread for 240 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)
151761
177.413
39006
65.101
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
img
Avoid large layout shifts — 2 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.029503546099291
0.0081903861308117
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoid long main-thread tasks — 5 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://www.google.com/js/bg/LfFQ5hcFG3hXPsOLdOnrUHUTGTSsMRvOgIlCDTigNb8.js
1530
132
http://js.parkingcrew.net/assets/scripts/jsparkcaf.js
640
121
https://www.google.com/js/bg/LfFQ5hcFG3hXPsOLdOnrUHUTGTSsMRvOgIlCDTigNb8.js
1662
117
http://www.google.com/adsense/domains/caf.js
913
112
https://www.google.com/adsense/domains/caf.js
1250
61
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

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

Other

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

Diagnostics

Serve static assets with an efficient cache policy — 8 resources found
Frendz4m.in can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Transfer Size (Bytes)
http://d1lxhc4jvstzrp.cloudfront.net/themes/registrar/images/logo_dynadot2.png
0
20089
http://js.parkingcrew.net/assets/scripts/jsparkcaf.js
0
5884
http://js.parkingcrew.net/jsparkcaf.php?_v=3&regcn=852261&_h=frendz4m.in&_t=1601487248967&_qs=
0
5675
http://js.parkingcrew.net/assets/scripts/registrar-caf/852261.js
0
3327
http://d1lxhc4jvstzrp.cloudfront.net/registrar/v3/content/852261
0
3084
http://i.cdnpark.com/registrar/v3/loader.js
0
2583
http://i.cdnpark.com/themes/registrar/852261.css
0
1294
https://afs.googleusercontent.com/dp-teaminternet/arr_1e88e5.png
82800000
1695

Diagnostics

Avoid `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
URL Location
http://i.cdnpark.com/registrar/v3/loader.js
line: 13
http://js.parkingcrew.net/jsparkcaf.php?_v=3&regcn=852261&_h=frendz4m.in&_t=1601487248967&_qs=
line: 0
https://www.google.com/adsense/domains/caf.js
line: 199
56

Accessibility

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

Navigation

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

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
`[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.
`<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 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"]`
Frendz4m.in may provide assistance to deaf or hearing-impaired users with captions on videos.
`<video>` elements contain a `<track>` element with `[kind="description"]`
Frendz4m.in 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

Names and labels

`<frame>` or `<iframe>` elements do not have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
Failing Elements
Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements
img
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.

Internationalization and localization

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

Manual Checks

The page has a logical tab order
The visual layout should be logical in its tab order and users cannot focus elements that are offscreen.
Interactive controls are keyboard focusable
Ensure that custom interactive controls are keyboard focusable and that a focus indicator is displayed.
Interactive elements indicate their purpose and state
Ensure that interactive elements (such as links and buttons) are distinguishable from non-interactive elements and that they indicate their state.
The user's focus is directed to new content added to the page
When new content (such as a dialogue) is added to the page, the user's focus should be directed to it.
User focus is not accidentally trapped in a region
Avoid focus being accidentally trapped when a user tabs in and out of controls or regions on page.
Custom controls have associated labels
Ensure that custom interactive controls have associated labels, which are provided by aria-label and aria-labelledby attributes.
Custom controls have ARIA roles
Ensure that all custom interactive controls have appropriate ARIA roles.
Visual order on the page follows DOM order
Ensure that the DOM order matches with the page's visual order, in order to improve navigation for screen readers and other assistive technologies.
Offscreen content is hidden from assistive technology
Ensure that offscreen content is hidden through the use of "display:none" styling or the aria-hidden attribute.
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.
64

Best Practices

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

Audits

Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids front-end JavaScript libraries with known security vulnerabilities
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.

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

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.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.

Audits

Does not use HTTPS — 13 insecure requests found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL
http://frendz4m.in/
http://i.cdnpark.com/themes/registrar/852261.css
http://i.cdnpark.com/registrar/v3/loader.js
http://frendz4m.in/hp_script.js
http://d1lxhc4jvstzrp.cloudfront.net/registrar/v3/content/852261
http://js.parkingcrew.net/jsparkcaf.php?_v=3&regcn=852261&_h=frendz4m.in&_t=1601487248967&_qs=
http://d1lxhc4jvstzrp.cloudfront.net/themes/registrar/images/logo_dynadot2.png
http://www.google.com/adsense/domains/caf.js
http://js.parkingcrew.net/assets/scripts/jsparkcaf.js
http://js.parkingcrew.net/ls.php
http://js.parkingcrew.net/track.php?domain=frendz4m.in&toggle=browserjs&uid=MTYwMTQ4NzI0OS4wNTc4OjFhYTg1YTRlZGFkOTgwNGNjNDE1NjE3ZjNkMmYwMzkxMzExYWY5YmU3Mzk0NjQ1MTc3OWU1NTc3MmVkODI4ZTQ6NWY3NGMxOTEwZTFkYw%3D%3D
http://js.parkingcrew.net/assets/scripts/registrar-caf/852261.js
http://js.parkingcrew.net/track.php?domain=frendz4m.in&caf=1&toggle=answercheck&answer=yes&uid=MTYwMTQ4NzI0OS4wNTc4OjFhYTg1YTRlZGFkOTgwNGNjNDE1NjE3ZjNkMmYwMzkxMzExYWY5YmU3Mzk0NjQ1MTc3OWU1NTc3MmVkODI4ZTQ6NWY3NGMxOTEwZTFkYw%3D%3D
Links to cross-origin destinations are unsafe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.

Audits

Page lacks the HTML doctype, thus triggering quirks-mode
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.

Audits

Uses deprecated APIs — 1 warning found
Avoid deprecated APIs which will eventually be removed the browser.
Deprecation / Warning URL
Synchronous XMLHttpRequest on the main thread is deprecated because of its detrimental effects to the end user's experience. For more help, check https://xhr.spec.whatwg.org/.
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
http://frendz4m.in/hp_script.js
SyntaxError: Unexpected token '<'
73

SEO

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

Mobile Friendly

Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of frendz4m.in on mobile screens.
Document uses legible font sizes
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.
Tap targets are sized appropriately
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.

Content Best Practices

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
Links have descriptive text
Make use of descriptive link text to assist search engines in understanding the content.
Document has a valid `hreflang`
Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.
Document has a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.
Document avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
Links are crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.
Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.

Content Best Practices

Document does not have a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.
Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements
img

Crawling and Indexing

robots.txt is not valid — 7 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 PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
Unknown directive
2
<html xmlns:fb="http://www.facebook.com/2008/fbml" xmlns:og="http://ogp.me/ns#">
Unknown directive
3
<head>
Syntax not understood
4
<meta http-equiv="Content-Type" content="text/html; charset=utf-8"><meta name="viewport" content="width=device-width, initial-scale=1, user-scalable=no shrink-to-fit=no"><title>&nbsp;</title><link href="http://i.cdnpark.com/themes/registrar/852261.css" rel="stylesheet"></head>
Unknown directive
5
<body><script type="text/javascript"><!--
Syntax not understood
6
var cname = "852261";var identifier = "";
Syntax not understood
7
--></script><script type="text/javascript" src="//i.cdnpark.com/registrar/v3/loader.js"></script><script type="text/javascript" src="/hp_script.js"></script></body></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.
33

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

Fast and reliable

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

PWA Optimized

Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of frendz4m.in on mobile screens.

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 — 13 insecure requests found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL
http://frendz4m.in/
http://i.cdnpark.com/themes/registrar/852261.css
http://i.cdnpark.com/registrar/v3/loader.js
http://frendz4m.in/hp_script.js
http://d1lxhc4jvstzrp.cloudfront.net/registrar/v3/content/852261
http://js.parkingcrew.net/jsparkcaf.php?_v=3&regcn=852261&_h=frendz4m.in&_t=1601487248967&_qs=
http://d1lxhc4jvstzrp.cloudfront.net/themes/registrar/images/logo_dynadot2.png
http://www.google.com/adsense/domains/caf.js
http://js.parkingcrew.net/assets/scripts/jsparkcaf.js
http://js.parkingcrew.net/ls.php
http://js.parkingcrew.net/track.php?domain=frendz4m.in&toggle=browserjs&uid=MTYwMTQ4NzI0OS4wNTc4OjFhYTg1YTRlZGFkOTgwNGNjNDE1NjE3ZjNkMmYwMzkxMzExYWY5YmU3Mzk0NjQ1MTc3OWU1NTc3MmVkODI4ZTQ6NWY3NGMxOTEwZTFkYw%3D%3D
http://js.parkingcrew.net/assets/scripts/registrar-caf/852261.js
http://js.parkingcrew.net/track.php?domain=frendz4m.in&caf=1&toggle=answercheck&answer=yes&uid=MTYwMTQ4NzI0OS4wNTc4OjFhYTg1YTRlZGFkOTgwNGNjNDE1NjE3ZjNkMmYwMzkxMzExYWY5YmU3Mzk0NjQ1MTc3OWU1NTc3MmVkODI4ZTQ6NWY3NGMxOTEwZTFkYw%3D%3D
Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Web app manifest does not meet the installability requirements
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
View Data

PWA Optimized

Does not redirect HTTP traffic to HTTPS
It is advised to redirect all HTTP traffic to HTTPS, in order to enable secure web features for all users.
Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Does not set a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Does not provide fallback content when JavaScript is not available
Apps should display alternative content for when JavaScript is disabled.
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) 62
Performance 59
Accessibility 70
Best Practices 64
SEO 83
Progressive Web App 36
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
Simulate loading on mobile
59

Performance

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

Metrics

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

Opportunities

Eliminate render-blocking resources — Potential savings of 0 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Frendz4m.in should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
http://i.cdnpark.com/themes/registrar/852261.css
1294
630
Properly size images
Images can slow down the page's load time. Frendz4m.in should consider serving more appropriate-sized images.
Defer offscreen images — Potential savings of 19 KiB
Time to Interactive can be slowed down by resources on the page. Frendz4m.in should consider lazy-loading offscreen and hidden images.
URL Resource Size (Bytes) Potential Savings (Bytes)
http://d1lxhc4jvstzrp.cloudfront.net/themes/registrar/images/logo_dynadot2.png
19647
19647
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Frendz4m.in should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Frendz4m.in should consider minifying JS files.
Remove unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Frendz4m.in should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats — Potential savings of 16 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)
http://d1lxhc4jvstzrp.cloudfront.net/themes/registrar/images/logo_dynadot2.png
19647
15925
Enable text compression — Potential savings of 10 KiB
Text-based resources should be served with compression, such as gzip, deflate or brotli.
URL Transfer Size (Bytes) Potential Savings (Bytes)
http://js.parkingcrew.net/assets/scripts/jsparkcaf.js
5638
3905
http://js.parkingcrew.net/jsparkcaf.php?_v=3&regcn=852261&_h=frendz4m.in&_t=1601487261217&_qs=
5468
2608
http://js.parkingcrew.net/assets/scripts/registrar-caf/852261.js
3082
2149
http://d1lxhc4jvstzrp.cloudfront.net/registrar/v3/content/852261
2696
1911
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 20 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)
http://frendz4m.in/
16.869
Avoid multiple page redirects
Redirects can cause additional delays before the page can begin loading. Frendz4m.in should avoid multiple or unnecessary page redirects.
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Frendz4m.in should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.

Diagnostics

Avoids enormous network payloads — Total size was 192 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://www.google.com/adsense/domains/caf.js
64039
http://www.google.com/adsense/domains/caf.js
62382
http://d1lxhc4jvstzrp.cloudfront.net/themes/registrar/images/logo_dynadot2.png
20089
https://www.google.com/dp/ads?max_radlink_len=40&r=m&client=dp-mobile-teaminternet02_3ph&channel=000001&hl=en&adtest=off&type=3&pcsa=false&swp=as-drid-2997149969328928&uiopt=false&oe=UTF-8&ie=UTF-8&fexp=21404%2C17300002&format=r10%7Cs&num=0&output=afd_ads&domain_name=frendz4m.in&v=3&adext=as1%2Csr1&bsl=8&u_his=2&u_tz=-420&dt=1601487261893&u_w=360&u_h=640&biw=360&bih=640&psw=360&psh=205&frm=0&uio=ff2sa16fa2sl1sr1-st22sa14lt33-&cont=tc&csize=w360h0&inames=master-1&jsv=71661&rurl=http%3A%2F%2Ffrendz4m.in%2F
8216
https://www.google.com/js/bg/LfFQ5hcFG3hXPsOLdOnrUHUTGTSsMRvOgIlCDTigNb8.js
6586
https://www.google.com/js/bg/LfFQ5hcFG3hXPsOLdOnrUHUTGTSsMRvOgIlCDTigNb8.js
6585
http://js.parkingcrew.net/assets/scripts/jsparkcaf.js
5884
http://js.parkingcrew.net/jsparkcaf.php?_v=3&regcn=852261&_h=frendz4m.in&_t=1601487261217&_qs=
5714
http://js.parkingcrew.net/assets/scripts/registrar-caf/852261.js
3327
http://d1lxhc4jvstzrp.cloudfront.net/registrar/v3/content/852261
3084
Avoids an excessive DOM size — 36 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
36
Maximum DOM Depth
10
Maximum Child Elements
12
Avoid chaining critical requests — 6 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Frendz4m.in 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.
All text remains visible during webfont loads
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
Keep request counts low and transfer sizes small — 21 requests • 192 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
21
196540
Script
10
160868
Image
4
22824
Document
3
10607
Stylesheet
1
1294
Other
3
947
Media
0
0
Font
0
0
Third-party
19
195172
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Avoid large layout shifts — 2 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.16329345703125
0.01296875
Avoid long main-thread tasks — 6 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://www.google.com/js/bg/LfFQ5hcFG3hXPsOLdOnrUHUTGTSsMRvOgIlCDTigNb8.js
4470
571
http://js.parkingcrew.net/assets/scripts/jsparkcaf.js
2070
458
http://www.google.com/adsense/domains/caf.js
3085
444
https://www.google.com/js/bg/LfFQ5hcFG3hXPsOLdOnrUHUTGTSsMRvOgIlCDTigNb8.js
5041
378
https://www.google.com/adsense/domains/caf.js
4110
228
http://js.parkingcrew.net/assets/scripts/registrar-caf/852261.js
3016
69
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.

Other

Network Requests
Below is a list of network requests that were made during page load.
URL Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://frendz4m.in/
0
15.885000117123
684
725
200
text/html
Document
http://i.cdnpark.com/themes/registrar/852261.css
32.461000140756
48.243999946862
1294
2472
200
text/css
Stylesheet
http://i.cdnpark.com/registrar/v3/loader.js
33.247000072151
103.19099994376
2583
2195
200
text/javascript
Script
http://frendz4m.in/hp_script.js
33.873999956995
49.953000154346
684
725
200
text/html
Script
http://d1lxhc4jvstzrp.cloudfront.net/registrar/v3/content/852261
106.80600022897
135.98800031468
3084
2696
200
text/javascript
Script
http://js.parkingcrew.net/jsparkcaf.php?_v=3&regcn=852261&_h=frendz4m.in&_t=1601487261217&_qs=
107.75800002739
228.09100011364
5714
5468
200
text/javascript
Script
http://d1lxhc4jvstzrp.cloudfront.net/themes/registrar/images/logo_dynadot2.png
139.71700007096
155.62000032514
20089
19647
200
image/png
Image
http://www.google.com/adsense/domains/caf.js
231.66300030425
251.61299994215
62382
176620
200
text/javascript
Script
http://js.parkingcrew.net/assets/scripts/jsparkcaf.js
232.43300011382
546.79400008172
5884
5638
200
application/javascript
Script
http://js.parkingcrew.net/ls.php
233.38200012222
342.46399998665
345
0
201
text/javascript
XHR
http://js.parkingcrew.net/track.php?domain=frendz4m.in&toggle=browserjs&uid=MTYwMTQ4NzI2MS4yODA0Ojg0MjQ1YmQ5Y2EyYWZlMTVmZTllNGYwMjVjMmFjMmZjZjU3MDBkNDI4ZGMyZWU1YjdiYjJjOGY5NWVkOTllMGM6NWY3NGMxOWQ0NDc0Mg%3D%3D
550.95300031826
660.4500003159
300
0
200
text/html
XHR
http://js.parkingcrew.net/assets/scripts/registrar-caf/852261.js
662.31800010428
769.57100024447
3327
3082
200
application/javascript
Script
https://www.google.com/afs/ads/i/iframe.html
794.60600018501
799.58700016141
1707
1243
200
text/html
Document
https://www.google.com/dp/ads?max_radlink_len=40&r=m&client=dp-mobile-teaminternet02_3ph&channel=000001&hl=en&adtest=off&type=3&pcsa=false&swp=as-drid-2997149969328928&uiopt=false&oe=UTF-8&ie=UTF-8&fexp=21404%2C17300002&format=r10%7Cs&num=0&output=afd_ads&domain_name=frendz4m.in&v=3&adext=as1%2Csr1&bsl=8&u_his=2&u_tz=-420&dt=1601487261893&u_w=360&u_h=640&biw=360&bih=640&psw=360&psh=205&frm=0&uio=ff2sa16fa2sl1sr1-st22sa14lt33-&cont=tc&csize=w360h0&inames=master-1&jsv=71661&rurl=http%3A%2F%2Ffrendz4m.in%2F
801.78000032902
889.02600016445
8216
10908
200
text/html
Document
https://www.google.com/adsense/domains/caf.js
904.04100017622
922.51800000668
64039
176647
200
text/javascript
Script
https://afs.googleusercontent.com/dp-teaminternet/arr_1e88e5.png
989.19899994507
995.64100010321
1670
1136
200
image/png
Image
http://js.parkingcrew.net/track.php?domain=frendz4m.in&caf=1&toggle=answercheck&answer=yes&uid=MTYwMTQ4NzI2MS4yODA0Ojg0MjQ1YmQ5Y2EyYWZlMTVmZTllNGYwMjVjMmFjMmZjZjU3MDBkNDI4ZGMyZWU1YjdiYjJjOGY5NWVkOTllMGM6NWY3NGMxOWQ0NDc0Mg%3D%3D
993.88500023633
1102.3110002279
302
0
200
text/html
XHR
https://www.google.com/js/bg/LfFQ5hcFG3hXPsOLdOnrUHUTGTSsMRvOgIlCDTigNb8.js
1111.5170000121
1115.3800003231
6586
13716
200
text/javascript
Script
https://www.google.com/js/bg/LfFQ5hcFG3hXPsOLdOnrUHUTGTSsMRvOgIlCDTigNb8.js
1142.9500002414
1146.2799999863
6585
13716
200
text/javascript
Script
https://www.google.com/afs/gen_204?client=dp-mobile-teaminternet02_3ph&output=uds_ads_only&zx=ihg9gbsg6jhv&aqid=ncF0X7HLOouX6toPjN-3qAI&pbt=bs&adbx=0&adby=129.4375&adbh=379&adbw=360&adbn=master-1&eawp=partner-dp-mobile-teaminternet02_3ph&errv=7166121592703734751&csadii=21&csadr=340&pblt=1&lle=0&llm=0&ifv=1
2643.161999993
2665.929000359
545
0
204
text/html
Image
https://www.google.com/afs/gen_204?client=dp-mobile-teaminternet02_3ph&output=uds_ads_only&zx=c1y8m9c1coqj&pbt=bs&adbx=36&adby=556.4375&adbh=36&adbw=288&adbn=slave-1-1&eawp=partner-dp-mobile-teaminternet02_3ph&errv=7166121592703734751&csadii=14&csadr=350&pblt=1&lle=0&llm=0&ifv=1
2645.9970003925
2674.5200003497
520
0
204
text/html
Image
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)
55.615
9.924
304.172
11.585
584.73
114.506
807.516
34.401
843.125
8.944
929.399
7.985
971.041
56.903
1028.709
110.998
1139.76
6.23
1152.263
14.068
1172.462
5.353
1180.092
142.659
1322.788
6.233
1331.042
94.48
1426.499
6.656
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
First Contentful Paint (3G) — 3075 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.

Metrics

Speed Index — 3.7 s
The time taken for the page contents to be visibly populated.
Largest Contentful Paint — 3.5 s
The timing of the largest text or image that is painted.
Time to Interactive — 5.4 s
The time taken for the page to become fully interactive.
Cumulative Layout Shift — 0.176
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

First CPU Idle — 5.4 s
The time taken for the page's main thread to be quiet enough to handle input.
First Meaningful Paint — 3.2 s
The time taken for the primary content of the page to be rendered.

Opportunities

Remove unused JavaScript — Potential savings of 75 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
http://www.google.com/adsense/domains/caf.js
62382
40756
https://www.google.com/adsense/domains/caf.js
64039
35941

Diagnostics

Serve static assets with an efficient cache policy — 8 resources found
Frendz4m.in can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Transfer Size (Bytes)
http://d1lxhc4jvstzrp.cloudfront.net/themes/registrar/images/logo_dynadot2.png
0
20089
http://js.parkingcrew.net/assets/scripts/jsparkcaf.js
0
5884
http://js.parkingcrew.net/jsparkcaf.php?_v=3&regcn=852261&_h=frendz4m.in&_t=1601487261217&_qs=
0
5714
http://js.parkingcrew.net/assets/scripts/registrar-caf/852261.js
0
3327
http://d1lxhc4jvstzrp.cloudfront.net/registrar/v3/content/852261
0
3084
http://i.cdnpark.com/registrar/v3/loader.js
0
2583
http://i.cdnpark.com/themes/registrar/852261.css
0
1294
https://afs.googleusercontent.com/dp-teaminternet/arr_1e88e5.png
82800000
1670
Reduce JavaScript execution time — 2.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://www.google.com/adsense/domains/caf.js
1212.448
1127.172
34.336
http://js.parkingcrew.net/assets/scripts/jsparkcaf.js
583.996
557.632
2.58
http://www.google.com/adsense/domains/caf.js
523.66
486.872
17.768
Unattributable
158.3
10.756
0.596
http://frendz4m.in/
127.168
17.088
6.532
https://www.google.com/afs/ads/i/iframe.html
51.332
14.352
5.08
https://www.google.com/dp/ads?max_radlink_len=40&r=m&client=dp-mobile-teaminternet02_3ph&channel=000001&hl=en&adtest=off&type=3&pcsa=false&swp=as-drid-2997149969328928&uiopt=false&oe=UTF-8&ie=UTF-8&fexp=21404%2C17300002&format=r10%7Cs&num=0&output=afd_ads&domain_name=frendz4m.in&v=3&adext=as1%2Csr1&bsl=8&u_his=2&u_tz=-420&dt=1601487261893&u_w=360&u_h=640&biw=360&bih=640&psw=360&psh=205&frm=0&uio=ff2sa16fa2sl1sr1-st22sa14lt33-&cont=tc&csize=w360h0&inames=master-1&jsv=71661&rurl=http%3A%2F%2Ffrendz4m.in%2F
50.472
7.132
4.74
Minimize main-thread work — 2.8 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Script Evaluation
2268.768
Other
243.14
Style & Layout
91.608
Script Parsing & Compilation
90.764
Parse HTML & CSS
52.808
Garbage Collection
42.216
Rendering
37.656

Metrics

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

Other

Max Potential First Input Delay — 570 ms
Users could experience a delay when interacting with the page.
Estimated Input Latency — 250 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 frendz4m.in as laggy when the latency is higher than 0.05 seconds.

Diagnostics

Reduce the impact of third-party code — Third-party code blocked the main thread for 1,660 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)
150580
1225.504
39045
432.128
Does not use passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
URL Location
https://www.google.com/adsense/domains/caf.js
line: 135
Avoid `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
URL Location
http://i.cdnpark.com/registrar/v3/loader.js
line: 13
http://js.parkingcrew.net/jsparkcaf.php?_v=3&regcn=852261&_h=frendz4m.in&_t=1601487261217&_qs=
line: 0
https://www.google.com/adsense/domains/caf.js
line: 199
70

Accessibility

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

Navigation

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

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
`[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.
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 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"]`
Frendz4m.in may provide assistance to deaf or hearing-impaired users with captions on videos.
`<video>` elements contain a `<track>` element with `[kind="description"]`
Frendz4m.in 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

Names and labels

`<frame>` or `<iframe>` elements do not have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
Failing Elements
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.

Internationalization and localization

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

Manual Checks

The page has a logical tab order
The visual layout should be logical in its tab order and users cannot focus elements that are offscreen.
Interactive controls are keyboard focusable
Ensure that custom interactive controls are keyboard focusable and that a focus indicator is displayed.
Interactive elements indicate their purpose and state
Ensure that interactive elements (such as links and buttons) are distinguishable from non-interactive elements and that they indicate their state.
The user's focus is directed to new content added to the page
When new content (such as a dialogue) is added to the page, the user's focus should be directed to it.
User focus is not accidentally trapped in a region
Avoid focus being accidentally trapped when a user tabs in and out of controls or regions on page.
Custom controls have associated labels
Ensure that custom interactive controls have associated labels, which are provided by aria-label and aria-labelledby attributes.
Custom controls have ARIA roles
Ensure that all custom interactive controls have appropriate ARIA roles.
Visual order on the page follows DOM order
Ensure that the DOM order matches with the page's visual order, in order to improve navigation for screen readers and other assistive technologies.
Offscreen content is hidden from assistive technology
Ensure that offscreen content is hidden through the use of "display:none" styling or the aria-hidden attribute.
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.
64

Best Practices

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

Audits

Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids front-end JavaScript libraries with known security vulnerabilities
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.

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

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.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.

Audits

Does not use HTTPS — 13 insecure requests found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL
http://frendz4m.in/
http://i.cdnpark.com/themes/registrar/852261.css
http://i.cdnpark.com/registrar/v3/loader.js
http://frendz4m.in/hp_script.js
http://d1lxhc4jvstzrp.cloudfront.net/registrar/v3/content/852261
http://js.parkingcrew.net/jsparkcaf.php?_v=3&regcn=852261&_h=frendz4m.in&_t=1601487261217&_qs=
http://d1lxhc4jvstzrp.cloudfront.net/themes/registrar/images/logo_dynadot2.png
http://www.google.com/adsense/domains/caf.js
http://js.parkingcrew.net/assets/scripts/jsparkcaf.js
http://js.parkingcrew.net/ls.php
http://js.parkingcrew.net/track.php?domain=frendz4m.in&toggle=browserjs&uid=MTYwMTQ4NzI2MS4yODA0Ojg0MjQ1YmQ5Y2EyYWZlMTVmZTllNGYwMjVjMmFjMmZjZjU3MDBkNDI4ZGMyZWU1YjdiYjJjOGY5NWVkOTllMGM6NWY3NGMxOWQ0NDc0Mg%3D%3D
http://js.parkingcrew.net/assets/scripts/registrar-caf/852261.js
http://js.parkingcrew.net/track.php?domain=frendz4m.in&caf=1&toggle=answercheck&answer=yes&uid=MTYwMTQ4NzI2MS4yODA0Ojg0MjQ1YmQ5Y2EyYWZlMTVmZTllNGYwMjVjMmFjMmZjZjU3MDBkNDI4ZGMyZWU1YjdiYjJjOGY5NWVkOTllMGM6NWY3NGMxOWQ0NDc0Mg%3D%3D
Links to cross-origin destinations are unsafe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.

Audits

Page lacks the HTML doctype, thus triggering quirks-mode
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.

Audits

Uses deprecated APIs — 1 warning found
Avoid deprecated APIs which will eventually be removed the browser.
Deprecation / Warning URL
Synchronous XMLHttpRequest on the main thread is deprecated because of its detrimental effects to the end user's experience. For more help, check https://xhr.spec.whatwg.org/.
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
http://frendz4m.in/hp_script.js
SyntaxError: Unexpected token '<'
83

SEO

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

Mobile Friendly

Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of frendz4m.in on mobile screens.
Document uses legible font sizes — 100% legible text
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.
Source Selector % of Page Text Font Size
100.00%
≥ 12px
Tap targets are sized appropriately — 100% appropriately sized tap targets
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.

Content Best Practices

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

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
Links are crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.
Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.

Content Best Practices

Document does not have a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.

Crawling and Indexing

robots.txt is not valid — 7 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 PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
Unknown directive
2
<html xmlns:fb="http://www.facebook.com/2008/fbml" xmlns:og="http://ogp.me/ns#">
Unknown directive
3
<head>
Syntax not understood
4
<meta http-equiv="Content-Type" content="text/html; charset=utf-8"><meta name="viewport" content="width=device-width, initial-scale=1, user-scalable=no shrink-to-fit=no"><title>&nbsp;</title><link href="http://i.cdnpark.com/themes/registrar/852261.css" rel="stylesheet"></head>
Unknown directive
5
<body><script type="text/javascript"><!--
Syntax not understood
6
var cname = "852261";var identifier = "";
Syntax not understood
7
--></script><script type="text/javascript" src="//i.cdnpark.com/registrar/v3/loader.js"></script><script type="text/javascript" src="/hp_script.js"></script></body></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 frendz4m.in. This includes details about web app manifests.

Fast and reliable

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

PWA Optimized

Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of frendz4m.in on mobile screens.

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 — 13 insecure requests found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL
http://frendz4m.in/
http://i.cdnpark.com/themes/registrar/852261.css
http://i.cdnpark.com/registrar/v3/loader.js
http://frendz4m.in/hp_script.js
http://d1lxhc4jvstzrp.cloudfront.net/registrar/v3/content/852261
http://js.parkingcrew.net/jsparkcaf.php?_v=3&regcn=852261&_h=frendz4m.in&_t=1601487261217&_qs=
http://d1lxhc4jvstzrp.cloudfront.net/themes/registrar/images/logo_dynadot2.png
http://www.google.com/adsense/domains/caf.js
http://js.parkingcrew.net/assets/scripts/jsparkcaf.js
http://js.parkingcrew.net/ls.php
http://js.parkingcrew.net/track.php?domain=frendz4m.in&toggle=browserjs&uid=MTYwMTQ4NzI2MS4yODA0Ojg0MjQ1YmQ5Y2EyYWZlMTVmZTllNGYwMjVjMmFjMmZjZjU3MDBkNDI4ZGMyZWU1YjdiYjJjOGY5NWVkOTllMGM6NWY3NGMxOWQ0NDc0Mg%3D%3D
http://js.parkingcrew.net/assets/scripts/registrar-caf/852261.js
http://js.parkingcrew.net/track.php?domain=frendz4m.in&caf=1&toggle=answercheck&answer=yes&uid=MTYwMTQ4NzI2MS4yODA0Ojg0MjQ1YmQ5Y2EyYWZlMTVmZTllNGYwMjVjMmFjMmZjZjU3MDBkNDI4ZGMyZWU1YjdiYjJjOGY5NWVkOTllMGM6NWY3NGMxOWQ0NDc0Mg%3D%3D
Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Web app manifest does not meet the installability requirements
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
View Data

PWA Optimized

Does not redirect HTTP traffic to HTTPS
It is advised to redirect all HTTP traffic to HTTPS, in order to enable secure web features for all users.
Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Does not set a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Does not provide fallback content when JavaScript is not available
Apps should display alternative content for when JavaScript is disabled.
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: 45.56.79.23
Continent: North America
Country: United States
United States Flag
Region: Texas
City: Dallas
Longitude: -96.8217
Latitude: 32.7787
Currencies: USD
USN
USS
Languages: English

Web Hosting Provider

Name IP Address
Linode
Registration

Domain Registrant

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

Domain Registrar

Security

Visitor Safety

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

SSL/TLS Certificate

Issued To: frendz4m.in
Issued By: R3
Valid From: 14th May, 2021
Valid To: 12th August, 2021
Subject: CN = frendz4m.in
Hash: 9ded6c6a
Issuer: CN = R3
O = Let's Encrypt
S = US
Version: 2
Serial Number: 0x03F67E53CDD3D0DDECE23E08BB2616D5C285
Serial Number (Hex): 03F67E53CDD3D0DDECE23E08BB2616D5C285
Valid From: 14th May, 2024
Valid To: 12th August, 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 : 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 : May 14 03:11:57.426 2021 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:44:02:20:6F:73:E2:19:28:A2:C4:96:80:93:7F:68:
C1:0B:F3:39:2F:D3:07:32:5C:64:63:C8:E2:8E:B0:C7:
AA:1B:22:D0:02:20:1B:AC:C5:8D:64:E7:69:0B:A0:7B:
75:19:66:7F:51:17:A0:BD:AA:E7:30:B4:6B:1B:B0:98:
AC:EC:2F:59:D3:C5
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 : May 14 03:11:57.461 2021 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:20:7B:E5:E5:0E:7B:CE:EA:98:B9:88:15:78:
40:CE:F5:06:E4:97:F3:52:8B:AB:D0:5D:31:D3:D3:86:
32:5D:AD:A7:02:21:00:DE:62:4D:C5:AE:1C:8E:5D:68:
84:F1:1F:81:6F:32:ED:5E:73:51:A8:2E:1E:DE:EE:DA:
C7:0F:C3:EF:C5:E7:DE
Key Usage: Digital Signature, Key Encipherment
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:frendz4m.in
DNS:*.frendz4m.in
Technical

DNS Lookup

A Records

Host IP Address Class TTL
frendz4m.in. 45.79.19.196 IN 299
frendz4m.in. 198.58.118.167 IN 299
frendz4m.in. 45.56.79.23 IN 299
frendz4m.in. 45.33.2.79 IN 299
frendz4m.in. 45.33.23.183 IN 299
frendz4m.in. 96.126.123.244 IN 299

NS Records

Host Nameserver Class TTL
frendz4m.in. ns2.mytrafficmanagement.com. IN 299
frendz4m.in. ns1.mytrafficmanagement.com. IN 299

MX Records

Priority Host Server Class TTL
1 frendz4m.in. mail.mailerhost.net. IN 3599

SOA Records

Domain Name Primary NS Responsible Email TTL
frendz4m.in. ns1.mytrafficmanagement.com. admin.frendz4m.in. 299

TXT Records

Host Value Class TTL
frendz4m.in. v=spf1 IN 3599

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Server: openresty/1.13.6.1
Date: 2nd July, 2021
Content-Type: application/octet-stream
Content-Length: 0
Connection: close

Whois Lookup

Created:
Changed:
Expires:
Status:
Nameservers: ns1.mytrafficmanagement.com
ns2.mytrafficmanagement.com
Full Whois:

Nameservers

Name IP Address
ns1.mytrafficmanagement.com 52.223.41.32
ns2.mytrafficmanagement.com 35.71.129.26
Related

Subdomains

Similar Sites

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Domain Valuation Snoop Score
0/5
$840 USD 1/5
0/5
0/5
$809 USD 1/5

Sites hosted on the same IP address

Domain Valuation Snoop Score
$10 USD 1/5
0/5
0/5
$913 USD 2/5