pirateiro.com

pirateiro.com is SSL secured

Free website and domain report on pirateiro.com

Last Updated: 28th January, 2021 Update Now
Overview

Snoop Summary for pirateiro.com

This is a free and comprehensive report about pirateiro.com. The domain pirateiro.com is currently hosted on a server located in United States with the IP address 172.67.158.94, where USD is the local currency and the local language is English. Pirateiro.com has the potential to be earning an estimated $8 USD per day from advertising revenue. If pirateiro.com was to be sold it would possibly be worth $5,527 USD (based on the daily revenue potential of the website over a 24 month period). Pirateiro.com receives an estimated 2,652 unique visitors every day - a large amount of traffic! This report was last updated 28th January, 2021.

About pirateiro.com

Site Preview: pirateiro.com pirateiro.com
Title: Download movies, music, tv series, games, software! Pirateiro
Description: Search and download, new episodes from your favorites tv series, movies, musics, games of PC/PS2/PSP/Wii/Xbox all fast and free.
Keywords and Tags: potential illegal software
Related Terms: ps2
Fav Icon:
Age: Over 8 years old
Domain Created: 18th June, 2015
Domain Updated: 1st June, 2020
Domain Expires: 18th June, 2021
Review

Snoop Score

3/5 (Great!)

Valuation

$5,527 USD
Note: All valuation figures are estimates.

Popularity

Modest
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 210,617
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: 2,652
Monthly Visitors: 80,719
Yearly Visitors: 967,980
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $8 USD
Monthly Revenue: $230 USD
Yearly Revenue: $2,759 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: pirateiro.com 13
Domain Name: pirateiro 9
Extension (TLD): com 3
Expiry Check:

Page Speed Analysis

Average Load Time: 1.13 seconds
Load Time Comparison: Faster than 75% of sites

PageSpeed Insights

Avg. (All Categories) 70
Performance 99
Accessibility 54
Best Practices 71
SEO 91
Progressive Web App 37
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: http://pirateiro.com
Updated: 28th January, 2021

1.32 seconds
First Contentful Paint (FCP)
57%
36%
7%

0.00 seconds
First Input Delay (FID)
98%
1%
1%

Simulate loading on desktop
99

Performance

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

Metrics

First Contentful Paint — 0.7 s
The time taken for the first image or text on the page to be rendered.
Speed Index — 1.0 s
The time taken for the page contents to be visibly populated.
Largest Contentful Paint — 0.8 s
The timing of the largest text or image that is painted.
Time to Interactive — 0.8 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
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

First CPU Idle — 0.8 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.
First Meaningful Paint — 0.7 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 pirateiro.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://pirateiro.com/
0
103.50800000015
124206
299641
200
text/html
Document
http://pirateiro.com/styles/default.css
126.16800000251
214.36500000709
20085
139959
200
text/css
Stylesheet
http://pirateiro.com/js/jquery.2.2.4.min.js
126.52800000797
220.60900001088
30922
85577
200
application/javascript
Script
http://pirateiro.com/js/all.js
126.95299999905
767.71200000076
7510
23753
200
application/javascript
Script
http://pirateiro.com/js/jquery.fancybox.min.js
127.53300000622
751.27000000793
22987
67881
200
application/javascript
Script
http://pirateiro.com/js/validationTopLogin.js
128.21799999801
776.27300001041
1355
1163
200
application/javascript
Script
http://pirateiro.com/js/slideout.min.js
140.65700001083
221.38000000268
3109
6865
200
application/javascript
Script
http://www.google-analytics.com/analytics.js
786.79199999897
790.90200000792
19274
47051
200
text/javascript
Script
https://www.visariomedia.com/sequence-diagram-min.js
806.53899999743
891.15900000616
9759
31307
200
application/x-javascript
Script
http://pirateiro.com/pic/spriteContent.png
811.01900000067
847.41800000484
63188
62365
200
image/png
Image
851.19000000122
851.33200000564
0
4688
200
image/png
Image
851.76400000637
851.96100000758
0
4502
200
image/png
Image
852.34800000035
852.45900000155
0
4959
200
image/png
Image
852.84600000887
852.97100000025
0
5058
200
image/png
Image
853.29900000943
853.40000000724
0
4534
200
image/png
Image
853.74800000864
853.8750000007
0
4771
200
image/png
Image
854.26300000108
854.41900001024
0
4553
200
image/png
Image
854.7350000008
854.84300000826
0
4427
200
image/png
Image
855.20000000542
855.31500000798
0
4825
200
image/png
Image
855.66700001073
855.80000000482
0
5000
200
image/png
Image
856.17700000876
856.33000000962
0
5145
200
image/png
Image
856.72200001136
856.85399999784
0
6062
200
image/png
Image
857.18700000143
857.30600000534
0
5538
200
image/png
Image
857.66500000318
857.78400000709
0
5273
200
image/png
Image
858.1930000073
858.33899999852
0
6105
200
image/png
Image
858.7300000072
858.8410000084
0
4849
200
image/png
Image
859.22300000675
859.32499999763
0
4301
200
image/png
Image
859.67299999902
859.80000000563
0
5229
200
image/png
Image
860.15300000145
860.25700000755
0
4421
200
image/png
Image
860.60800000269
860.74600000575
0
3979
200
image/png
Image
861.1579999997
861.25700001139
0
4796
200
image/png
Image
861.65000000619
861.78700000164
0
5297
200
image/png
Image
862.19700000947
862.32600000221
0
4983
200
image/png
Image
862.65400001139
862.77600000903
0
4487
200
image/png
Image
https://www.google-analytics.com/j/collect?v=1&_v=j87&a=1887230274&t=pageview&_s=1&dl=http%3A%2F%2Fpirateiro.com%2F&ul=en-us&de=UTF-8&dt=Download%20movies%2C%20music%2C%20tv%20series%2C%20games%2C%20software!%20Pirateiro&sd=24-bit&sr=800x600&vp=1350x940&je=0&_u=IEBAAEABAAAAAC~&jid=1627585780&gjid=499440153&cid=985655046.1611865674&tid=UA-34472775-2&_gid=1804695095.1611865674&_r=1&_slc=1&z=113566242
1131.4050000074
1135.0440000097
621
2
200
text/plain
XHR
http://c.adsco.re/
1284.9700000079
1352.3859999987
1827
0
403
text/html
Script
http://visariomedia.com/y.html?_=e1&v=4&ukqDJMFQ=1560023&minBid=0.00021&DuqTRBQm=0,0&KluXjvVA=&RHodNIqe=&s=800,600,1,800,600,0
1463.122000001
1512.0319999987
273
0
200
application/javascript
Script
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
149.261
13.376
257.441
5.809
271.723
25.161
810.645
37.512
848.177
24.662
876.018
33.461
909.601
159.165
1071.322
62.531
1136.687
36.604
1173.315
22.877
1204.205
5.018
1209.276
15.415
1228.101
19.574
1399.384
37.298
1494.978
6.421
1515.92
20.126
1699.341
37.19
1748.578
29.754
1781.419
5.959
1799.454
37.533
1943.221
101.838
3101.831
5.944
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data

Opportunities

Properly size images
Images can slow down the page's load time. Pirateiro.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Pirateiro.com should consider lazy-loading offscreen and hidden images.
Minify CSS — Potential savings of 4 KiB
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Pirateiro.com should consider minifying CSS files.
URL Transfer Size (Bytes) Potential Savings (Bytes)
http://pirateiro.com/styles/default.css
20085
4289
Minify JavaScript — Potential savings of 4 KiB
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Pirateiro.com should consider minifying JS files.
URL Transfer Size (Bytes) Potential Savings (Bytes)
http://pirateiro.com/js/all.js
7510
3840
Remove unused CSS — Potential savings of 17 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Pirateiro.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)
http://pirateiro.com/styles/default.css
20085
17720
Remove unused JavaScript
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats — Potential savings of 36 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://pirateiro.com/pic/spriteContent.png
62365
36427
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Initial server response time was short — Root document took 100 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://pirateiro.com/
104.503
Avoid multiple page redirects
Redirects can cause additional delays before the page can begin loading. Pirateiro.com should avoid multiple or unnecessary page redirects.
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Pirateiro.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)
http://pirateiro.com/js/slideout.min.js
76

Diagnostics

Avoids enormous network payloads — Total size was 298 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
http://pirateiro.com/
124206
http://pirateiro.com/pic/spriteContent.png
63188
http://pirateiro.com/js/jquery.2.2.4.min.js
30922
http://pirateiro.com/js/jquery.fancybox.min.js
22987
http://pirateiro.com/styles/default.css
20085
http://www.google-analytics.com/analytics.js
19274
https://www.visariomedia.com/sequence-diagram-min.js
9759
http://pirateiro.com/js/all.js
7510
http://pirateiro.com/js/slideout.min.js
3109
http://c.adsco.re/
1827
Uses efficient cache policy on static assets — 10 resources found
Pirateiro.com can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Transfer Size (Bytes)
http://www.google-analytics.com/analytics.js
7200000
19274
https://www.visariomedia.com/sequence-diagram-min.js
604800000
9759
http://visariomedia.com/y.html?_=e1&v=4&ukqDJMFQ=1560023&minBid=0.00021&DuqTRBQm=0,0&KluXjvVA=&RHodNIqe=&s=800,600,1,800,600,0
604800000
273
http://pirateiro.com/js/jquery.2.2.4.min.js
2592000000
30922
http://pirateiro.com/js/jquery.fancybox.min.js
2592000000
22987
http://pirateiro.com/styles/default.css
2592000000
20085
http://pirateiro.com/js/all.js
2592000000
7510
http://pirateiro.com/js/slideout.min.js
2592000000
3109
http://pirateiro.com/js/validationTopLogin.js
2592000000
1355
http://pirateiro.com/pic/spriteContent.png
5184000000
63188
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. Pirateiro.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.1 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
http://pirateiro.com/
614.981
28.236
4.118
http://pirateiro.com/js/jquery.2.2.4.min.js
91.114
52.934
2.059
Unattributable
54.027
3.367
0.254
Minimizes main-thread work — 0.9 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)
Style & Layout
225.885
Other
224.287
Rendering
213.051
Script Evaluation
175.171
Parse HTML & CSS
27.462
Script Parsing & Compilation
14.063
All text remains visible during webfont loads
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
Keep request counts low and transfer sizes small — 13 requests • 298 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
13
305116
Document
1
124206
Script
9
97016
Image
1
63188
Stylesheet
1
20085
Other
1
621
Media
0
0
Font
0
0
Third-party
5
31754
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)
19895
0
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Avoid large layout shifts
Below is a list of all DOM elements that contribute to the CLS of the page.
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)
http://pirateiro.com/
338
80
http://pirateiro.com/
608
51
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.

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. Pirateiro.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)
http://pirateiro.com/styles/default.css
20085
150
http://pirateiro.com/js/jquery.2.2.4.min.js
30922
230
http://pirateiro.com/js/all.js
7510
150
http://pirateiro.com/js/jquery.fancybox.min.js
22987
190

Diagnostics

Avoid an excessive DOM size — 1,906 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
1,906
Maximum DOM Depth
15
Maximum Child Elements
50
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
http://pirateiro.com/js/slideout.min.js
line: 0
54

Accessibility

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

Navigation

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

ARIA

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

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.

Names and labels

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

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.

Audio and video

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

ARIA

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

Names and labels

Buttons do not 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.
Failing Elements
Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
Form elements do not have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
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.

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
126
959
325
733
614
716
126
667
222
553
224
482
28
709
154
531
67
387
54
277
42
274
27
250
33
235
29
201
58
201
34
142
58
140
17
138
30
112
26
108
31
752
284
548
47
471
160
406
66
337
94
329
79
311
122
104
85
57
44
41
38
35
400
424
202
13
154
59
139
12
122
91
60
30
157
119
116
102
95
95
74
94
api
rss
YTS

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

Best practices

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

Manual Checks

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

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that pirateiro.com 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.

Audits

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

Audits

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

Audits

Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.
Avoids Application Cache
Application cache is deprecated and is no longer recommended.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
jQuery
2.2.4
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.

Audits

Does not use HTTPS — 11 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://pirateiro.com/
http://pirateiro.com/styles/default.css
http://pirateiro.com/js/jquery.2.2.4.min.js
http://pirateiro.com/js/all.js
http://pirateiro.com/js/jquery.fancybox.min.js
http://pirateiro.com/js/validationTopLogin.js
http://pirateiro.com/js/slideout.min.js
http://www.google-analytics.com/analytics.js
http://pirateiro.com/pic/spriteContent.png
http://c.adsco.re/
http://visariomedia.com/y.html?_=e1&v=4&ukqDJMFQ=1560023&minBid=0.00021&DuqTRBQm=0,0&KluXjvVA=&RHodNIqe=&s=800,600,1,800,600,0
Links to cross-origin destinations are unsafe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.
Includes front-end JavaScript libraries with known security vulnerabilities — 4 vulnerabilities detected
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Library Version Vulnerability Count Highest Severity
4
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
http://c.adsco.re/
Failed to load resource: the server responded with a status of 403 (Forbidden)
91

SEO

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

Mobile Friendly

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

Content Best Practices

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

Crawling and Indexing

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

Content Best Practices

Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img

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

Fast and reliable

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

PWA Optimized

Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
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 pirateiro.com on 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 — 11 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://pirateiro.com/
http://pirateiro.com/styles/default.css
http://pirateiro.com/js/jquery.2.2.4.min.js
http://pirateiro.com/js/all.js
http://pirateiro.com/js/jquery.fancybox.min.js
http://pirateiro.com/js/validationTopLogin.js
http://pirateiro.com/js/slideout.min.js
http://www.google-analytics.com/analytics.js
http://pirateiro.com/pic/spriteContent.png
http://c.adsco.re/
http://visariomedia.com/y.html?_=e1&v=4&ukqDJMFQ=1560023&minBid=0.00021&DuqTRBQm=0,0&KluXjvVA=&RHodNIqe=&s=800,600,1,800,600,0
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 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) 67
Performance 90
Accessibility 54
Best Practices 64
SEO 89
Progressive Web App 39
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: http://pirateiro.com
Updated: 28th January, 2021

1.50 seconds
First Contentful Paint (FCP)
57%
36%
7%

0.03 seconds
First Input Delay (FID)
85%
14%
1%

Simulate loading on mobile
90

Performance

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

Metrics

Speed Index — 2.6 s
The time taken for the page contents to be visibly populated.
Time to Interactive — 3.5 s
The time taken for the page to become fully interactive.
Total Blocking Time — 170 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
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

First CPU Idle — 2.8 s
The time taken for the page's main thread to be quiet enough to handle input.
Estimated Input Latency — 20 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 pirateiro.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://pirateiro.com/
0
73.508000001311
124392
299641
200
text/html
Document
http://pirateiro.com/styles/default.css
103.56499999762
181.71299993992
20087
139959
200
text/css
Stylesheet
http://pirateiro.com/js/jquery.2.2.4.min.js
103.96099998616
175.64499983564
30924
85577
200
application/javascript
Script
http://pirateiro.com/js/all.js
104.21599983238
134.89299989305
7517
23753
200
application/javascript
Script
http://pirateiro.com/js/jquery.fancybox.min.js
104.88299978897
150.47100000083
22988
67881
200
application/javascript
Script
http://pirateiro.com/js/validationTopLogin.js
105.20099988207
132.50999990851
1352
1163
200
application/javascript
Script
http://pirateiro.com/js/slideout.min.js
114.01599994861
154.63099977933
3107
6865
200
application/javascript
Script
http://www.google-analytics.com/analytics.js
222.83999994397
243.52899985388
19274
47051
200
text/javascript
Script
https://www.visariomedia.com/sequence-diagram-min.js
254.44899988361
324.76999983191
9759
31307
200
application/x-javascript
Script
251.70599995181
251.82999996468
0
4688
200
image/png
Image
252.15399987064
252.24299984984
0
4502
200
image/png
Image
252.59299995378
253.13799991272
0
4959
200
image/png
Image
253.48699977621
253.60499997623
0
5058
200
image/png
Image
253.94699978642
254.04299981892
0
4534
200
image/png
Image
254.32199984789
254.4259999413
0
4771
200
image/png
Image
254.69599990174
254.82199992985
0
4553
200
image/png
Image
255.09199989028
255.1819998771
0
4427
200
image/png
Image
255.48799987882
255.62699977309
0
4825
200
image/png
Image
255.93299977481
256.05999981053
0
5000
200
image/png
Image
256.36399979703
256.46699988283
0
5145
200
image/png
Image
256.80499989539
256.91499980167
0
6062
200
image/png
Image
257.20599992201
257.31899985112
0
5538
200
image/png
Image
257.62599986047
257.74299982004
0
5273
200
image/png
Image
258.04299977608
258.18099989556
0
6105
200
image/png
Image
258.49299994297
258.60199984163
0
4849
200
image/png
Image
258.88899993151
258.99699982256
0
4301
200
image/png
Image
259.30199981667
259.4229998067
0
5229
200
image/png
Image
259.6879999619
259.79899987578
0
4421
200
image/png
Image
260.03899984062
260.12099999934
0
3979
200
image/png
Image
260.41999994777
260.52599982359
0
4796
200
image/png
Image
260.82999981008
260.93799993396
0
5297
200
image/png
Image
261.23499986716
261.33599993773
0
4983
200
image/png
Image
261.62699982524
261.7199998349
0
4487
200
image/png
Image
http://pirateiro.com/pic/spriteContent.png
310.65999995917
346.95599996485
63196
62365
200
image/png
Image
https://www.google-analytics.com/j/collect?v=1&_v=j87&a=2117886622&t=pageview&_s=1&dl=http%3A%2F%2Fpirateiro.com%2F&ul=en-us&de=UTF-8&dt=Download%20movies%2C%20music%2C%20tv%20series%2C%20games%2C%20software!%20Pirateiro&sd=24-bit&sr=360x640&vp=360x640&je=0&_u=IEBAAEABAAAAAC~&jid=646165864&gjid=2092100679&cid=1480596478.1611865696&tid=UA-34472775-2&_gid=1761678372.1611865696&_r=1&_slc=1&z=489480201
611.87299992889
615.44099985622
621
2
200
text/plain
XHR
http://c.adsco.re/
744.68399980105
785.05499986932
1828
0
403
text/html
Script
http://visariomedia.com/y.html?_=e1&v=4&ukqDJMFQ=1560023&minBid=0.00021&DuqTRBQm=0,0&KluXjvVA=&RHodNIqe=&s=360,640,1,360,640,0
892.51999999397
926.46099999547
273
0
200
application/javascript
Script
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
119.825
12.008
215.248
5.093
220.413
50.252
270.955
29.28
300.255
216.082
517.255
47.213
569.18
30.443
600.476
18.253
618.75
5.863
624.683
19.113
643.824
17.101
664.243
13.814
765.587
13.683
883.576
14.368
902.144
9.069
1180.271
12.671
1381.882
52.8
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data

Opportunities

Properly size images
Images can slow down the page's load time. Pirateiro.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Pirateiro.com should consider lazy-loading offscreen and hidden images.
Remove unused JavaScript
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Initial server response time was short — Root document took 70 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://pirateiro.com/
74.504
Avoid multiple page redirects
Redirects can cause additional delays before the page can begin loading. Pirateiro.com should avoid multiple or unnecessary page redirects.
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Pirateiro.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)
http://pirateiro.com/js/slideout.min.js
76

Diagnostics

Avoids enormous network payloads — Total size was 298 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
http://pirateiro.com/
124392
http://pirateiro.com/pic/spriteContent.png
63196
http://pirateiro.com/js/jquery.2.2.4.min.js
30924
http://pirateiro.com/js/jquery.fancybox.min.js
22988
http://pirateiro.com/styles/default.css
20087
http://www.google-analytics.com/analytics.js
19274
https://www.visariomedia.com/sequence-diagram-min.js
9759
http://pirateiro.com/js/all.js
7517
http://pirateiro.com/js/slideout.min.js
3107
http://c.adsco.re/
1828
Uses efficient cache policy on static assets — 10 resources found
Pirateiro.com can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Transfer Size (Bytes)
http://www.google-analytics.com/analytics.js
7200000
19274
https://www.visariomedia.com/sequence-diagram-min.js
604800000
9759
http://visariomedia.com/y.html?_=e1&v=4&ukqDJMFQ=1560023&minBid=0.00021&DuqTRBQm=0,0&KluXjvVA=&RHodNIqe=&s=360,640,1,360,640,0
604800000
273
http://pirateiro.com/js/jquery.2.2.4.min.js
2592000000
30924
http://pirateiro.com/js/jquery.fancybox.min.js
2592000000
22988
http://pirateiro.com/styles/default.css
2592000000
20087
http://pirateiro.com/js/all.js
2592000000
7517
http://pirateiro.com/js/slideout.min.js
2592000000
3107
http://pirateiro.com/js/validationTopLogin.js
2592000000
1352
http://pirateiro.com/pic/spriteContent.png
5184000000
63196
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. Pirateiro.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.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)
http://pirateiro.com/
1796.152
82.876
10.712
http://pirateiro.com/js/jquery.2.2.4.min.js
334
216.704
7.952
Unattributable
231.324
9.792
1.104
https://www.visariomedia.com/sequence-diagram-min.js
133.864
109.42
2.964
http://www.google-analytics.com/analytics.js
82.428
69.824
6.364
http://pirateiro.com/js/validationTopLogin.js
68.116
43.108
0.768
http://pirateiro.com/js/jquery.fancybox.min.js
55.336
49.704
5.632
All text remains visible during webfont loads
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
Keep request counts low and transfer sizes small — 13 requests • 298 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
13
305318
Document
1
124392
Script
9
97022
Image
1
63196
Stylesheet
1
20087
Other
1
621
Media
0
0
Font
0
0
Third-party
5
31755
Minimize third-party usage — Third-party code blocked the main thread for 20 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)
19895
15.812
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Avoid large layout shifts
Below is a list of all DOM elements that contribute to the CLS of the page.
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 — 12 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)
http://pirateiro.com/
1285
432
http://pirateiro.com/js/jquery.2.2.4.min.js
3600
201
http://pirateiro.com/
1717
122
http://pirateiro.com/js/validationTopLogin.js
3801
117
http://pirateiro.com/
2049
106
http://pirateiro.com/js/slideout.min.js
3960
94
http://www.google-analytics.com/analytics.js
2460
76
Unattributable
1839
73
https://www.visariomedia.com/sequence-diagram-min.js
2536
68
http://pirateiro.com/
1967
57
http://pirateiro.com/
1912
55
http://pirateiro.com/js/jquery.2.2.4.min.js
4054
55
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 — 2.6 s
The time taken for the first image or text on the page to be rendered.
Largest Contentful Paint — 3.1 s
The timing of the largest text or image that is painted.

Other

Max Potential First Input Delay — 200 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 2.6 s
The time taken for the primary content of the page to be rendered.
First Contentful Paint (3G) — 5279.5 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.

Opportunities

Minify CSS — Potential savings of 4 KiB
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Pirateiro.com should consider minifying CSS files.
URL Transfer Size (Bytes) Potential Savings (Bytes)
http://pirateiro.com/styles/default.css
20087
4289
Minify JavaScript — Potential savings of 4 KiB
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Pirateiro.com should consider minifying JS files.
URL Transfer Size (Bytes) Potential Savings (Bytes)
http://pirateiro.com/js/all.js
7517
3843
Remove unused CSS — Potential savings of 17 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Pirateiro.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)
http://pirateiro.com/styles/default.css
20087
17833
Serve images in next-gen formats — Potential savings of 36 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://pirateiro.com/pic/spriteContent.png
62365
36427

Diagnostics

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)
Style & Layout
1061.276
Script Evaluation
601.544
Rendering
503.204
Other
458.868
Parse HTML & CSS
82.184
Script Parsing & Compilation
43.52

Opportunities

Eliminate render-blocking resources — Potential savings of 920 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Pirateiro.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)
http://pirateiro.com/styles/default.css
20087
780
http://pirateiro.com/js/jquery.2.2.4.min.js
30924
930
http://pirateiro.com/js/all.js
7517
480
http://pirateiro.com/js/jquery.fancybox.min.js
22988
780

Diagnostics

Avoid an excessive DOM size — 1,906 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
1,906
Maximum DOM Depth
15
Maximum Child Elements
50
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
http://pirateiro.com/js/slideout.min.js
line: 0
54

Accessibility

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

Navigation

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

ARIA

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

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.

Names and labels

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

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.

Audio and video

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

ARIA

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

Names and labels

Buttons do not 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.
Failing Elements
Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
Form elements do not have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
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.

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
126
959
325
733
614
716
126
667
222
553
224
482
28
709
154
531
67
387
54
277
42
274
27
250
33
235
29
201
58
201
34
142
58
140
17
138
30
112
26
108
31
752
284
548
47
471
160
406
66
337
94
329
79
311
122
104
85
57
44
41
38
35
400
424
202
13
154
59
139
12
122
91
60
30
157
119
116
102
95
95
74
94
api
rss
YTS

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

Best practices

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

Manual Checks

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

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that pirateiro.com 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.

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
jQuery
2.2.4
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.

Audits

Does not use HTTPS — 11 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://pirateiro.com/
http://pirateiro.com/styles/default.css
http://pirateiro.com/js/jquery.2.2.4.min.js
http://pirateiro.com/js/all.js
http://pirateiro.com/js/jquery.fancybox.min.js
http://pirateiro.com/js/validationTopLogin.js
http://pirateiro.com/js/slideout.min.js
http://www.google-analytics.com/analytics.js
http://pirateiro.com/pic/spriteContent.png
http://c.adsco.re/
http://visariomedia.com/y.html?_=e1&v=4&ukqDJMFQ=1560023&minBid=0.00021&DuqTRBQm=0,0&KluXjvVA=&RHodNIqe=&s=360,640,1,360,640,0
Links to cross-origin destinations are unsafe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.
Includes front-end JavaScript libraries with known security vulnerabilities — 4 vulnerabilities detected
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Library Version Vulnerability Count Highest Severity
4
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
68 x 100
100 x 147
179 x 263

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
http://c.adsco.re/
Failed to load resource: the server responded with a status of 403 (Forbidden)
89

SEO

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

Mobile Friendly

Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of pirateiro.com on mobile screens.
Document uses legible font sizes — 84.39% 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
small
0.60%
9.6px
0.57%
10px
0.53%
10px
0.53%
10px
0.43%
10px
0.43%
11px
0.38%
11px
0.31%
10px
0.31%
10px
0.28%
11px
0.26%
10px
0.26%
10px
0.26%
11px
0.26%
10px
0.26%
10px
0.25%
10px
0.25%
10px
0.24%
11px
0.22%
10px
0.22%
10px
0.22%
11px
0.22%
11px
0.20%
10px
0.20%
10px
0.19%
10px
0.19%
10px
0.18%
10px
0.18%
11px
0.17%
11px
0.17%
10px
0.17%
10px
0.16%
11px
0.13%
10px
0.13%
11px
0.12%
10px
0.12%
10px
0.12%
11px
5.90%
< 12px
84.39%
≥ 12px

Content Best Practices

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

Crawling and Indexing

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

Mobile Friendly

Tap targets are not sized appropriately — 58% 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.
Tap Target Size Overlapping Target
2x1
21x14
3x4
21x14
3x3
21x14
4x6
21x14
4x8
21x14
28x14
31x11
31x11
31x11
31x11
3x4
21x14
3x3
3x3
21x14
3x2
3x3
21x14
3x2
3x2
21x14
3x1
4x6
21x14
4x5
4x5
21x14
4x4
4x8
21x14
4x7
4x7
21x14
4x6
28x14
28x14
36x11
36x11
36x11
36x11
38x11
38x11
38x11
38x11
38x11
40x11
40x11
40x11
32x17
53x11
53x11
53x11
38x11
38x11
44x17
40x11
53x11
a
18x18
a
18x18
33x17
56x14
44x17
64x17
37x18
a
16x16
a
16x16
a
16x16
a
16x16
a
16x16
a
16x16
a
16x16
a
16x16
a
16x16
48x18
54x17
a
16x16
a
16x16
52x17
33x17
33x17
59x17
32x17
54x18
34x17
18x11
59x17
72x17
59x17
a
16x16
a
16x16
a
16x16
a
16x16
31x11
31x11
53x11
53x11
51x18
36x11
72x17
38x11
38x11
38x11
38x11
40x11
40x11
77x17
86x17
86x17
55x17
74x18
51x18
105x18
57x18
74x17
87x17
87x17
93x17
57x17
103x17
52x17
104x17
93x17
72x17

Content Best Practices

Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img
img

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

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

Fast and reliable

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

PWA Optimized

Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
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 pirateiro.com on 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 — 11 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://pirateiro.com/
http://pirateiro.com/styles/default.css
http://pirateiro.com/js/jquery.2.2.4.min.js
http://pirateiro.com/js/all.js
http://pirateiro.com/js/jquery.fancybox.min.js
http://pirateiro.com/js/validationTopLogin.js
http://pirateiro.com/js/slideout.min.js
http://www.google-analytics.com/analytics.js
http://pirateiro.com/pic/spriteContent.png
http://c.adsco.re/
http://visariomedia.com/y.html?_=e1&v=4&ukqDJMFQ=1560023&minBid=0.00021&DuqTRBQm=0,0&KluXjvVA=&RHodNIqe=&s=360,640,1,360,640,0
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 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: 172.67.158.94
Continent: North America
Country: United States
United States Flag
Region:
City:
Longitude: -97.822
Latitude: 37.751
Currencies: USD
USN
USS
Languages: English

Web Hosting Provider

Name IP Address
Cloudflare, Inc.
Registration

Domain Registrant

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

Domain Registrar

Name IP Address
Public Interest Registry 34.234.52.18
Security

Visitor Safety

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

SSL/TLS Certificate

Issued To: sni.cloudflaressl.com
Issued By: Cloudflare Inc ECC CA-3
Valid From: 4th July, 2020
Valid To: 4th July, 2021
Subject: CN = sni.cloudflaressl.com
O = Cloudflare, Inc.
L = San Francisco
S = US
Hash: 4d04c09a
Issuer: CN = Cloudflare Inc ECC CA-3
O = Cloudflare, Inc.
S = US
Version: 2
Serial Number: 12261310488064377543799912441534566803
Serial Number (Hex): 09397147DA5BF45CE02B5AB387D15193
Valid From: 4th July, 2024
Valid To: 4th July, 2024
Signature Algorithm (Short Name): ecdsa-with-SHA256
Signature Algorithm (Long Name): ecdsa-with-SHA256
Authority Key Identifier: keyid:A5:CE:37:EA:EB:B0:75:0E:94:67:88:B4:45:FA:D9:24:10:87:96:1F
Extended Key Usage: TLS Web Server Authentication, TLS Web Client Authentication
CRL Distribution Points:
Full Name:
URI:http://crl3.digicert.com/CloudflareIncECCCA-3.crl

Full Name:
URI:http://crl4.digicert.com/CloudflareIncECCCA-3.crl

Certificate Policies: Policy: 2.16.840.1.114412.1.1
CPS: https://www.digicert.com/CPS
Policy: 2.23.140.1.2.2

Authority Information Access: OCSP - URI:http://ocsp.digicert.com
CA Issuers - URI:http://cacerts.digicert.com/CloudflareIncECCCA-3.crt

SCT List: Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : F6:5C:94:2F:D1:77:30:22:14:54:18:08:30:94:56:8E:
E3:4D:13:19:33:BF:DF:0C:2F:20:0B:CC:4E:F1:64:E3
Timestamp : Jul 4 13:17:30.587 2020 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:46:02:21:00:AC:11:4D:60:5F:FC:B7:F7:97:57:35:
7D:44:91:60:60:C3:C3:72:02:78:0A:21:D3:47:11:A3:
36:1C:A2:3E:1A:02:21:00:BD:38:A1:B7:30:C4:4E:6E:
DC:C9:DE:00:36:52:9C:9B:CD:2D:58:13:AB:62:11:0F:
83:8E:83:7F:55:8E:07:3A
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 5C:DC:43:92:FE:E6:AB:45:44:B1:5E:9A:D4:56:E6:10:
37:FB:D5:FA:47:DC:A1:73:94:B2:5E:E6:F6:C7:0E:CA
Timestamp : Jul 4 13:17:30.637 2020 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:44:02:20:5A:BB:05:BC:C2:19:B8:84:C3:DA:1E:F6:
CB:9A:F5:C3:42:EB:A7:E1:B7:94:2C:D4:4B:5F:D3:0E:
5D:D7:EA:35:02:20:65:8B:0D:A2:B8:67:97:63:7A:CC:
90:AC:63:8B:E1:38:13:65:CC:D6:7D:5F:DF:50:6D:88:
5E:23:17:0B:0A:01
Key Usage: Digital Signature
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:pirateiro.com
DNS:sni.cloudflaressl.com
DNS:*.pirateiro.com
Technical

DNS Lookup

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Date: 28th January, 2021
Content-Type: text/html; charset=utf-8
cache-control: public, max-age=259200
Server: cloudflare
Connection: keep-alive
Set-Cookie: *
vary: Accept-Encoding
x-xss-protection: 1; mode=block
x-content-type-options: nosniff
x-nginx-upstream-cache-status: HIT
x-server-powered-by: Engintron
CF-Cache-Status: HIT
Age: 1467
cf-request-id: 07ec4744340000e8496197e000000001
Expect-CT: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
Report-To: {"group":"cf-nel","endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report?s=vwGzp3fz7BxnXjYJo2%2Fs4YnFnPReDAlNTm2aQ6WMX1Gii8M2%2FGq7GoqSNsDOefYUegK8qdLIF%2B5cUPMHl4ZTRI9g2nh2ud%2BvcsPrJY7u"}],"max_age":604800}
NEL: {"max_age":604800,"report_to":"cf-nel"}
CF-RAY: 618d74b38fb6e849-EWR

Whois Lookup

Created: 18th June, 2015
Changed: 1st June, 2020
Expires: 18th June, 2021
Registrar: Tucows Domains Inc.
Status: clientTransferProhibited
clientUpdateProhibited
Nameservers: dora.ns.cloudflare.com
gerald.ns.cloudflare.com
Full Whois: Domain Name: PIRATEIRO.COM
Registry Domain ID: 1940062218_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.tucows.com
Registrar URL: http://www.tucows.com
Updated Date: 2020-06-01T12:21:54Z
Creation Date: 2015-06-18T19:09:10Z
Registry Expiry Date: 2021-06-18T19:09:10Z
Registrar: Tucows Domains Inc.
Registrar IANA ID: 69
Registrar Abuse Contact Email:
Registrar Abuse Contact Phone:
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Domain Status: clientUpdateProhibited https://icann.org/epp#clientUpdateProhibited
Name Server: DORA.NS.CLOUDFLARE.COM
Name Server: GERALD.NS.CLOUDFLARE.COM
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of whois database: 2021-01-28T20:27:38Z <<<

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

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

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

The Registry database contains ONLY .COM, .NET, .EDU domains and
Registrars.

Nameservers

Name IP Address
dora.ns.cloudflare.com 108.162.192.108
gerald.ns.cloudflare.com 173.245.59.168
Related

Subdomains

Similar Sites

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Domain Valuation Snoop Score
0/5
0/5

Sites hosted on the same IP address

Domain Valuation Snoop Score
0/5