pr.com

pr.com is SSL secured

Free website and domain report on pr.com

Last Updated: 13th September, 2023 Update Now
Overview

Snoop Summary for pr.com

This is a free and comprehensive report about pr.com. Our records indicate that pr.com is owned/operated by PR Group, Inc.. Pr.com is expected to earn an estimated $172 USD per day from advertising revenue. The sale of pr.com would possibly be worth $125,832 USD. This figure is based on the daily revenue potential of the website over a 24 month period. Pr.com receives an estimated 40,757 unique visitors every day - a massive amount of traffic! This report was last updated 13th September, 2023.

About pr.com

Site Preview: pr.com pr.com
Title: PR.com: Directory of Businesses Jobs Press Releases Products Services Articles - Find Companies
Description: Find businesses, products, services, jobs. Also offers company profiles, press release distribution and published articles.
Keywords and Tags: business
Related Terms: press release distribution services, press releases, press releases distribution
Fav Icon:
Age: Over 25 years old
Domain Created: 9th April, 1999
Domain Updated: 24th September, 2020
Domain Expires: 9th April, 2030
Review

Snoop Score

4/5 (Excellent!)

Valuation

$125,832 USD
Note: All valuation figures are estimates.

Popularity

High
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 21,595
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: 40,757
Monthly Visitors: 1,240,526
Yearly Visitors: 14,876,444
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $172 USD
Monthly Revenue: $5,246 USD
Yearly Revenue: $62,911 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: pr.com 6
Domain Name: pr 2
Extension (TLD): com 3
Expiry Check:

Page Speed Analysis

Average Load Time: 2.12 seconds
Load Time Comparison: Faster than 41% of sites

PageSpeed Insights

Avg. (All Categories) 69
Performance 90
Accessibility 65
Best Practices 71
SEO 83
Progressive Web App 37
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://www.pr.com/
Updated: 19th January, 2021

2.22 seconds
First Contentful Paint (FCP)
43%
42%
15%

0.00 seconds
First Input Delay (FID)
99%
0%
1%

Simulate loading on desktop
90

Performance

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

Metrics

Speed Index — 1.1 s
The time taken for the page contents to be visibly populated.
Time to Interactive — 1.1 s
The time taken for the page to become fully interactive.
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 — 1.1 s
The time taken for the page's main thread to be quiet enough to handle input.
Max Potential First Input Delay — 30 ms
Users could experience a delay when interacting with the page.
Estimated Input Latency — 10 ms
The time taken for the page to respond to user input (during the busiest 5 second window of page load). Users are likely to perceive pr.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://pr.com/
0
45.400999952108
267
0
301
text/html
https://pr.com/
46.211999841034
152.26799994707
297
0
301
text/html
https://www.pr.com/
152.86599984393
402.59800013155
5020
21269
200
text/html
Document
https://www.pr.com/style/style_home6_1302.css
419.1999998875
502.45899986476
1736
6451
200
text/css
Stylesheet
https://www.pr.com/javascript/header.js
419.47699990124
499.18799987063
1052
1599
200
application/javascript
Script
https://www.pr.com/javascript/jquery-1.7.2.min.js
419.67799980193
508.20800010115
33943
94840
200
application/javascript
Script
https://www.pr.com/javascript/jquery.ba-outside-events.js
419.94599997997
485.15499988571
3089
8868
200
application/javascript
Script
https://www.pr.com/javascript/jquery.class-toggler.js
420.32200004905
510.50300011411
827
2082
200
application/javascript
Script
https://www.pr.com/javascript/jquery.html-placeholder.js
420.56699981913
500.01299986616
692
1078
200
application/javascript
Script
https://www.pr.com/style/style_header_1302.css?v=2
421.22599994764
483.31000003964
3400
17418
200
text/css
Stylesheet
https://www.pr.com/javascript/dd_menu.js
421.50499997661
490.61099998653
2891
9758
200
application/javascript
Script
https://www.pr.com/javascript/header_1302.js?v=2
421.87999980524
498.69199981913
2370
8471
200
application/javascript
Script
https://www.googletagmanager.com/gtag/js?id=UA-4680984-1
512.26000022143
528.98300020024
39705
98649
200
application/javascript
Script
https://www.pr.com/images/twitter_home.gif
515.95100015402
546.50999978185
877
552
200
image/gif
Image
https://www.pr.com/images/logo_home_1302.png
535.72400007397
572.90699984878
17815
17487
200
image/png
Image
https://www.pr.com/contrib/slir/index.php?i=release/2101/482600/pressrelease_482600_1610676521.jpg&w=92&h=57&c=92x57
536.02600004524
714.08599987626
3545
3235
200
image/jpeg
Image
https://www.pr.com/contrib/slir/index.php?i=release/2101/449117/pressrelease_449117_1610987310.jpg&w=92&h=57&c=92x57
536.25199990347
648.599000182
2561
2251
200
image/jpeg
Image
https://www.pr.com/contrib/slir/index.php?i=release/2101/416814/pressrelease_416814_1611000888.png&w=92&h=57&c=92x57
536.41099995002
578.55299999937
6868
6559
200
image/png
Image
https://img.pr.com/article/1209/article_small_1348664121.jpg
536.66599979624
643.8049999997
7080
6825
200
image/jpeg
Image
https://img.pr.com/article/1208/article_small_1344540100.jpg
536.90599976107
646.1479999125
7297
7042
200
image/jpeg
Image
https://img.pr.com/article/1206/article_small_1340724602.jpg
537.0999998413
627.69200000912
6144
5889
200
image/jpeg
Image
https://www.pr.com/images/style_001/header_gradient.gif
542.63499984518
563.58799990267
388
65
200
image/gif
Image
https://www.pr.com/images/header_search_dark.gif
544.04200008139
561.9060001336
648
323
200
image/gif
Image
https://www.pr.com/images/arrow_down_gray_4x7.gif
544.79499999434
573.38699977845
372
49
200
image/gif
Image
https://www.pr.com/images/homepage_big_image.png
568.54599993676
640.40799997747
27231
26903
200
image/png
Image
https://www.google-analytics.com/analytics.js
628.36100021377
632.9370001331
19452
47051
200
text/javascript
Script
https://www.googletagmanager.com/gtag/js?id=AW-1070483724&l=dataLayer&cx=c
629.17400011793
654.73099984229
39704
98672
200
application/javascript
Script
https://www.google-analytics.com/j/collect?v=1&_v=j87&a=141223013&t=pageview&_s=1&dl=https%3A%2F%2Fwww.pr.com%2F&ul=en-us&de=UTF-8&dt=PR.com%3A%20Directory%20of%20Businesses%20Jobs%20Press%20Releases%20Products%20Services%20Articles%20-%20Find%20Companies&sd=24-bit&sr=800x600&vp=1350x940&je=0&_u=IGBACUABBAAAAC~&jid=1892841776&gjid=295874002&cid=1392249666.1611079789&tid=UA-4680984-1&_gid=1760434509.1611079789&_r=1&gtm=2ou161&z=976343164
667.52200014889
670.79599993303
619
2
200
text/plain
XHR
https://stats.g.doubleclick.net/j/collect?t=dc&aip=1&_r=3&v=1&_v=j87&tid=UA-4680984-1&cid=1392249666.1611079789&jid=1892841776&gjid=295874002&_gid=1760434509.1611079789&_u=IGBACUAABAAAAC~&z=1793935126
675.1120002009
678.4930001013
691
1
200
text/plain
XHR
https://www.googleadservices.com/pagead/conversion_async.js
697.52799998969
786.90999979153
13345
31040
200
text/javascript
Script
https://googleads.g.doubleclick.net/pagead/viewthroughconversion/1070483724/?random=1611079789190&cv=9&fst=1611079789190&num=1&bg=ffffff&guid=ON&resp=GooglemKTybQhCsO&u_h=600&u_w=800&u_ah=600&u_aw=800&u_cd=24&u_his=2&u_tz=-480&u_java=false&u_nplug=0&u_nmime=0&gtm=2oa161&sendb=1&ig=1&data=event%3Dgtag.config&frm=0&url=https%3A%2F%2Fwww.pr.com%2F&tiba=PR.com%3A%20Directory%20of%20Businesses%20Jobs%20Press%20Releases%20Products%20Services%20Articles%20-%20Find%20Companies&hn=www.googleadservices.com&async=1&rfmt=3&fmt=4
798.56299981475
807.5850000605
2532
1706
200
text/javascript
Script
https://www.google.com/pagead/1p-user-list/1070483724/?random=1611079789190&cv=9&fst=1611079200000&num=1&bg=ffffff&guid=ON&u_h=600&u_w=800&u_ah=600&u_aw=800&u_cd=24&u_his=2&u_tz=-480&u_java=false&u_nplug=0&u_nmime=0&gtm=2oa161&sendb=1&data=event%3Dgtag.config&frm=0&url=https%3A%2F%2Fwww.pr.com%2F&tiba=PR.com%3A%20Directory%20of%20Businesses%20Jobs%20Press%20Releases%20Products%20Services%20Articles%20-%20Find%20Companies&async=1&fmt=3&is_vtc=1&random=2345923893&resp=GooglemKTybQhCsO&rmt_tld=0&ipr=y
811.18000019342
835.86200000718
746
42
200
image/gif
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)
436.126
9.238
545.468
25.007
570.492
19.042
606.983
25.094
632.132
8.984
644.744
14.199
667.1
30.601
710.919
20.869
819.845
8.209
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. Pr.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Pr.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Pr.com should consider minifying CSS files.
Minify JavaScript — Potential savings of 3 KiB
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Pr.com should consider minifying JS files.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.pr.com/javascript/jquery.ba-outside-events.js
3089
2601
Remove unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Pr.com 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 65 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.googletagmanager.com/gtag/js?id=AW-1070483724&l=dataLayer&cx=c
39704
22338
https://www.pr.com/javascript/jquery-1.7.2.min.js
33943
22258
https://www.googletagmanager.com/gtag/js?id=UA-4680984-1
39705
21462
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)
https://www.pr.com/images/homepage_big_image.png
26903
24147
https://www.pr.com/images/logo_home_1302.png
17487
12673
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 250 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
https://www.pr.com/
250.728
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Pr.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
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 247 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://www.googletagmanager.com/gtag/js?id=UA-4680984-1
39705
https://www.googletagmanager.com/gtag/js?id=AW-1070483724&l=dataLayer&cx=c
39704
https://www.pr.com/javascript/jquery-1.7.2.min.js
33943
https://www.pr.com/images/homepage_big_image.png
27231
https://www.google-analytics.com/analytics.js
19452
https://www.pr.com/images/logo_home_1302.png
17815
https://www.googleadservices.com/pagead/conversion_async.js
13345
https://img.pr.com/article/1208/article_small_1344540100.jpg
7297
https://img.pr.com/article/1209/article_small_1348664121.jpg
7080
https://www.pr.com/contrib/slir/index.php?i=release/2101/416814/pressrelease_416814_1611000888.png&w=92&h=57&c=92x57
6868
Avoids an excessive DOM size — 305 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
305
Maximum DOM Depth
13
Maximum Child Elements
16
Avoid chaining critical requests — 9 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Pr.com should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
JavaScript execution time — 0.0 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://www.pr.com/
58.811
9.798
2.553
Minimizes main-thread work — 0.2 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Script Evaluation
112.532
Other
45.686
Style & Layout
28.73
Script Parsing & Compilation
14.328
Parse HTML & CSS
11.692
Rendering
9.669
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 — 32 requests • 247 KiB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.
Resource Type Requests Transfer Size (Bytes)
Total
32
253204
Script
12
159602
Image
13
81572
Stylesheet
2
5136
Document
1
5020
Other
4
1874
Media
0
0
Font
0
0
Third-party
8
116794
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)
79409
0
20071
0
16568
0
746
0
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.00040109917489153
2.7561479458639E-5
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
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 — 1.1 s
The time taken for the first image or text on the page to be rendered.
Largest Contentful Paint — 1.8 s
The timing of the largest text or image that is painted.

Other

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

Opportunities

Eliminate render-blocking resources — Potential savings of 680 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Pr.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
https://www.pr.com/style/style_home6_1302.css
1736
70
https://www.pr.com/javascript/header.js
1052
150
https://www.pr.com/javascript/jquery-1.7.2.min.js
33943
270
https://www.pr.com/javascript/jquery.ba-outside-events.js
3089
150
https://www.pr.com/javascript/jquery.class-toggler.js
827
150
https://www.pr.com/javascript/jquery.html-placeholder.js
692
70
https://www.pr.com/style/style_header_1302.css?v=2
3400
150
https://www.pr.com/javascript/dd_menu.js
2891
70
https://www.pr.com/javascript/header_1302.js?v=2
2370
70
Avoid multiple page redirects — Potential savings of 340 ms
Redirects can cause additional delays before the page can begin loading. Pr.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://pr.com/
190
https://pr.com/
150
https://www.pr.com/
0

Diagnostics

Serve static assets with an efficient cache policy — 14 resources found
Pr.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)
https://www.pr.com/javascript/jquery-1.7.2.min.js
0
33943
https://img.pr.com/article/1208/article_small_1344540100.jpg
0
7297
https://img.pr.com/article/1209/article_small_1348664121.jpg
0
7080
https://img.pr.com/article/1206/article_small_1340724602.jpg
0
6144
https://www.pr.com/javascript/jquery.ba-outside-events.js
0
3089
https://www.pr.com/javascript/dd_menu.js
0
2891
https://www.pr.com/javascript/header_1302.js?v=2
0
2370
https://www.pr.com/javascript/header.js
0
1052
https://www.pr.com/javascript/jquery.class-toggler.js
0
827
https://www.pr.com/javascript/jquery.html-placeholder.js
0
692
https://www.google-analytics.com/analytics.js
7200000
19452
https://www.pr.com/contrib/slir/index.php?i=release/2101/416814/pressrelease_416814_1611000888.png&w=92&h=57&c=92x57
604800000
6868
https://www.pr.com/contrib/slir/index.php?i=release/2101/482600/pressrelease_482600_1610676521.jpg&w=92&h=57&c=92x57
604800000
3545
https://www.pr.com/contrib/slir/index.php?i=release/2101/449117/pressrelease_449117_1610987310.jpg&w=92&h=57&c=92x57
604800000
2561
65

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of pr.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.
`[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.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
`[aria-hidden="true"]` is not present on the document `<body>`
If aria-hidden=true is set on the document body, assistive technologies, like a screen reader will work inconsistently.
`[aria-hidden="true"]` elements do not contain focusable descendents
Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.
ARIA input fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when an input field does not have an accessible name specified.
`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.
`[role]`s are contained by their required parent element
Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.
`[role]` values are valid
All ARIA roles require valid values to perform their intended functions.
ARIA toggle fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when a toggle field does not have an accessible name specified.
`[aria-*]` attributes have valid values
ARIA attributes cannot be interpreted with invalid values when used by screen readers and other assistive technologies.
`[aria-*]` attributes are valid and not misspelled
ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.
ARIA IDs are unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.

Names and labels

Buttons have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
`<frame>` or `<iframe>` elements have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Links have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.
`<object>` elements have `[alt]` text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<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"]`
Pr.com may provide assistance to deaf or hearing-impaired users with captions on videos.
`<video>` elements contain a `<track>` element with `[kind="description"]`
Pr.com may provide relevant information that dialogue cannot, by using audio descriptions.

Navigation

The page does not contain a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.
Some elements have 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.
Failing Elements

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

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

Names and labels

Form elements do not have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
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 pr.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

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
1.7.2
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.

Audits

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

Audits

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

SEO

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

Content Best Practices

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

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
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

Document uses legible font sizes
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.
Tap targets are sized appropriately
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.

Mobile Friendly

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

Content Best Practices

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

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

Fast and reliable

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

PWA Optimized

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

Fast and reliable

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

Installable

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

PWA Optimized

Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Does not set a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of pr.com on mobile screens.
Does not provide a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.
Manifest doesn't have a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

Manual Checks

Site works cross-browser
Ensure that the Progressive Web App works correctly across every major browser.
Page transitions don't feel like they block on the network
Users perceive apps with responsive, snappy transitions as higher peforming and ensures a great user experience, even on a slow network.
Each page has a URL
Ensure that all pages are deep linkable via URL. They should also be unique for the purpose of shareability on social media.
Avg. (All Categories) 62
Performance 72
Accessibility 65
Best Practices 64
SEO 71
Progressive Web App 36
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://www.pr.com/
Updated: 19th January, 2021

3.84 seconds
First Contentful Paint (FCP)
20%
40%
40%

0.26 seconds
First Input Delay (FID)
3%
85%
12%

Simulate loading on mobile
72

Performance

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

Metrics

Speed Index — 3.3 s
The time taken for the page contents to be visibly populated.
Total Blocking Time — 40 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

Max Potential First Input Delay — 110 ms
Users could experience a delay when interacting with the page.
Estimated Input Latency — 10 ms
The time taken for the page to respond to user input (during the busiest 5 second window of page load). Users are likely to perceive pr.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://pr.com/
0
197.91299989447
267
0
301
text/html
https://pr.com/
198.53599974886
271.25199977309
297
0
301
text/html
https://www.pr.com/
271.80499956012
327.50499993563
5020
21269
200
text/html
Document
https://www.pr.com/style/style_home6_1302.css
342.28999959305
360.84899958223
1736
6451
200
text/css
Stylesheet
https://www.pr.com/javascript/header.js
342.48199965805
366.94099986926
1052
1599
200
application/javascript
Script
https://www.pr.com/javascript/jquery-1.7.2.min.js
342.63699967414
387.54399958998
33943
94840
200
application/javascript
Script
https://www.pr.com/javascript/jquery.ba-outside-events.js
342.79799973592
402.2559998557
3089
8868
200
application/javascript
Script
https://www.pr.com/javascript/jquery.class-toggler.js
343.26699981466
401.08899958432
827
2082
200
application/javascript
Script
https://www.pr.com/javascript/jquery.html-placeholder.js
343.72999984771
361.3999998197
692
1078
200
application/javascript
Script
https://www.pr.com/style/style_header_1302.css?v=2
343.93299976364
362.17599967495
3400
17418
200
text/css
Stylesheet
https://www.pr.com/javascript/dd_menu.js
344.3619995378
363.1489998661
2891
9758
200
application/javascript
Script
https://www.pr.com/javascript/header_1302.js?v=2
344.65299965814
404.40599992871
2370
8471
200
application/javascript
Script
https://www.googletagmanager.com/gtag/js?id=UA-4680984-1
411.28199966624
433.1679996103
39705
98649
200
application/javascript
Script
https://www.pr.com/images/twitter_home.gif
414.60399981588
441.87199976295
877
552
200
image/gif
Image
https://www.pr.com/images/logo_home_1302.png
415.51399976015
446.91499974579
17815
17487
200
image/png
Image
https://www.pr.com/contrib/slir/index.php?i=release/2101/482600/pressrelease_482600_1610676521.jpg&w=92&h=57&c=92x57
415.68699991331
455.56399971247
3545
3235
200
image/jpeg
Image
https://www.pr.com/contrib/slir/index.php?i=release/2101/449117/pressrelease_449117_1610987310.jpg&w=92&h=57&c=92x57
415.89199984446
501.86299998313
2561
2251
200
image/jpeg
Image
https://www.pr.com/contrib/slir/index.php?i=release/2101/416814/pressrelease_416814_1611000888.png&w=92&h=57&c=92x57
416.21299972758
454.67799995095
6868
6559
200
image/png
Image
https://img.pr.com/article/1209/article_small_1348664121.jpg
416.46199999377
486.78999999538
7080
6825
200
image/jpeg
Image
https://img.pr.com/article/1208/article_small_1344540100.jpg
416.78299987689
439.931999892
7297
7042
200
image/jpeg
Image
https://img.pr.com/article/1206/article_small_1340724602.jpg
416.95199999958
485.20099977031
6144
5889
200
image/jpeg
Image
https://www.pr.com/images/style_001/header_gradient.gif
421.61899991333
440.80199999735
388
65
200
image/gif
Image
https://www.pr.com/images/header_search_dark.gif
421.86199966818
440.36299968138
648
323
200
image/gif
Image
https://www.pr.com/images/arrow_down_gray_4x7.gif
422.16399963945
443.96199984476
372
49
200
image/gif
Image
https://www.pr.com/images/homepage_big_image.png
437.12299969047
509.07899998128
27231
26903
200
image/png
Image
https://www.google-analytics.com/analytics.js
491.32299982011
497.00799956918
19452
47051
200
text/javascript
Script
https://www.googletagmanager.com/gtag/js?id=AW-1070483724&l=dataLayer&cx=c
492.18799965456
517.480999697
39704
98672
200
application/javascript
Script
https://www.google-analytics.com/j/collect?v=1&_v=j87&a=873825993&t=pageview&_s=1&dl=https%3A%2F%2Fwww.pr.com%2F&ul=en-us&de=UTF-8&dt=PR.com%3A%20Directory%20of%20Businesses%20Jobs%20Press%20Releases%20Products%20Services%20Articles%20-%20Find%20Companies&sd=24-bit&sr=360x640&vp=980x1742&je=0&_u=IGBACUABBAAAAC~&jid=486474800&gjid=1227709123&cid=1626774812.1611079800&tid=UA-4680984-1&_gid=806269402.1611079800&_r=1&gtm=2ou161&z=1268594279
527.48599974439
533.1859998405
619
2
200
text/plain
XHR
https://stats.g.doubleclick.net/j/collect?t=dc&aip=1&_r=3&v=1&_v=j87&tid=UA-4680984-1&cid=1626774812.1611079800&jid=486474800&gjid=1227709123&_gid=806269402.1611079800&_u=IGBACUAABAAAAC~&z=1796685181
536.05999983847
541.29099985585
691
1
200
text/plain
XHR
https://www.googleadservices.com/pagead/conversion_async.js
548.11799991876
637.21599988639
13458
31095
200
text/javascript
Script
https://googleads.g.doubleclick.net/pagead/viewthroughconversion/1070483724/?random=1611079800627&cv=9&fst=1611079800627&num=1&bg=ffffff&guid=ON&resp=GooglemKTybQhCsO&u_h=640&u_w=360&u_ah=640&u_aw=360&u_cd=24&u_his=2&u_tz=-480&u_java=false&u_nplug=0&u_nmime=0&gtm=2oa161&sendb=1&ig=1&data=event%3Dgtag.config&frm=0&url=https%3A%2F%2Fwww.pr.com%2F&tiba=PR.com%3A%20Directory%20of%20Businesses%20Jobs%20Press%20Releases%20Products%20Services%20Articles%20-%20Find%20Companies&hn=www.googleadservices.com&async=1&rfmt=3&fmt=4
647.61499967426
693.82799975574
2401
1706
200
text/javascript
Script
https://www.google.com/pagead/1p-user-list/1070483724/?random=1611079800627&cv=9&fst=1611079200000&num=1&bg=ffffff&guid=ON&u_h=640&u_w=360&u_ah=640&u_aw=360&u_cd=24&u_his=2&u_tz=-480&u_java=false&u_nplug=0&u_nmime=0&gtm=2oa161&sendb=1&data=event%3Dgtag.config&frm=0&url=https%3A%2F%2Fwww.pr.com%2F&tiba=PR.com%3A%20Directory%20of%20Businesses%20Jobs%20Press%20Releases%20Products%20Services%20Articles%20-%20Find%20Companies&async=1&fmt=3&is_vtc=1&random=3676287294&resp=GooglemKTybQhCsO&rmt_tld=0&ipr=y
697.17799965292
708.96799955517
746
42
200
image/gif
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)
365.804
7.819
430.609
13.74
449.302
5.129
454.443
11.619
479.534
18.588
505.046
9.324
514.789
12.587
536.681
26.3
571.768
14.807
675.458
7.24
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. Pr.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Pr.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Pr.com should consider minifying CSS files.
Minify JavaScript — Potential savings of 3 KiB
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Pr.com should consider minifying JS files.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.pr.com/javascript/jquery.ba-outside-events.js
3089
2601
Remove unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Pr.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats — 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)
https://www.pr.com/images/homepage_big_image.png
26903
24147
https://www.pr.com/images/logo_home_1302.png
17487
12673
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 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)
https://www.pr.com/
56.698
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Pr.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
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 247 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://www.googletagmanager.com/gtag/js?id=UA-4680984-1
39705
https://www.googletagmanager.com/gtag/js?id=AW-1070483724&l=dataLayer&cx=c
39704
https://www.pr.com/javascript/jquery-1.7.2.min.js
33943
https://www.pr.com/images/homepage_big_image.png
27231
https://www.google-analytics.com/analytics.js
19452
https://www.pr.com/images/logo_home_1302.png
17815
https://www.googleadservices.com/pagead/conversion_async.js
13458
https://img.pr.com/article/1208/article_small_1344540100.jpg
7297
https://img.pr.com/article/1209/article_small_1348664121.jpg
7080
https://www.pr.com/contrib/slir/index.php?i=release/2101/416814/pressrelease_416814_1611000888.png&w=92&h=57&c=92x57
6868
Avoids an excessive DOM size — 305 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
305
Maximum DOM Depth
13
Maximum Child Elements
16
Avoid chaining critical requests — 9 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Pr.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.4 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.pr.com/
182.208
32.64
9.092
https://www.pr.com/javascript/jquery-1.7.2.min.js
122.852
73.852
8.192
https://www.google-analytics.com/analytics.js
118.584
101.792
5.248
Unattributable
106.944
3.516
0.624
https://www.googletagmanager.com/gtag/js?id=UA-4680984-1
95.64
79.232
11.14
https://www.googletagmanager.com/gtag/js?id=AW-1070483724&l=dataLayer&cx=c
79.528
67.028
8.896
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
373.444
Other
168.42
Style & Layout
81.872
Script Parsing & Compilation
55.84
Parse HTML & CSS
39.496
Rendering
26.012
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 — 32 requests • 247 KiB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.
Resource Type Requests Transfer Size (Bytes)
Total
32
253186
Script
12
159584
Image
13
81572
Stylesheet
2
5136
Document
1
5020
Other
4
1874
Media
0
0
Font
0
0
Third-party
8
116776
Minimize third-party usage — Third-party code blocked the main thread for 40 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)
20071
44.588
79409
0
16550
0
746
0
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.00023079495394787
1.5859046292259E-5
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks — 4 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-analytics.com/analytics.js
4350
105
https://www.googletagmanager.com/gtag/js?id=AW-1070483724&l=dataLayer&cx=c
4050
59
https://www.pr.com/javascript/jquery-1.7.2.min.js
3210
55
https://www.googletagmanager.com/gtag/js?id=UA-4680984-1
3339
50
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Avoids large JavaScript libraries with smaller alternatives — 0 large libraries found
It is recommended to work with smaller JavaScript libraries to reduce your bundle size and avoid poor performance.

Budgets

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

Metrics

First Contentful Paint — 3.3 s
The time taken for the first image or text on the page to be rendered.
Time to Interactive — 4.3 s
The time taken for the page to become fully interactive.

Other

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

Opportunities

Remove unused JavaScript — Potential savings of 65 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.googletagmanager.com/gtag/js?id=AW-1070483724&l=dataLayer&cx=c
39704
22338
https://www.pr.com/javascript/jquery-1.7.2.min.js
33943
22258
https://www.googletagmanager.com/gtag/js?id=UA-4680984-1
39705
21462

Diagnostics

Serve static assets with an efficient cache policy — 14 resources found
Pr.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)
https://www.pr.com/javascript/jquery-1.7.2.min.js
0
33943
https://img.pr.com/article/1208/article_small_1344540100.jpg
0
7297
https://img.pr.com/article/1209/article_small_1348664121.jpg
0
7080
https://img.pr.com/article/1206/article_small_1340724602.jpg
0
6144
https://www.pr.com/javascript/jquery.ba-outside-events.js
0
3089
https://www.pr.com/javascript/dd_menu.js
0
2891
https://www.pr.com/javascript/header_1302.js?v=2
0
2370
https://www.pr.com/javascript/header.js
0
1052
https://www.pr.com/javascript/jquery.class-toggler.js
0
827
https://www.pr.com/javascript/jquery.html-placeholder.js
0
692
https://www.google-analytics.com/analytics.js
7200000
19452
https://www.pr.com/contrib/slir/index.php?i=release/2101/416814/pressrelease_416814_1611000888.png&w=92&h=57&c=92x57
604800000
6868
https://www.pr.com/contrib/slir/index.php?i=release/2101/482600/pressrelease_482600_1610676521.jpg&w=92&h=57&c=92x57
604800000
3545
https://www.pr.com/contrib/slir/index.php?i=release/2101/449117/pressrelease_449117_1610987310.jpg&w=92&h=57&c=92x57
604800000
2561

Metrics

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

Opportunities

Eliminate render-blocking resources — Potential savings of 1,730 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Pr.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
https://www.pr.com/style/style_home6_1302.css
1736
180
https://www.pr.com/javascript/header.js
1052
480
https://www.pr.com/javascript/jquery-1.7.2.min.js
33943
930
https://www.pr.com/javascript/jquery.ba-outside-events.js
3089
480
https://www.pr.com/javascript/jquery.class-toggler.js
827
480
https://www.pr.com/javascript/jquery.html-placeholder.js
692
180
https://www.pr.com/style/style_header_1302.css?v=2
3400
480
https://www.pr.com/javascript/dd_menu.js
2891
180
https://www.pr.com/javascript/header_1302.js?v=2
2370
180
Avoid multiple page redirects — Potential savings of 1,110 ms
Redirects can cause additional delays before the page can begin loading. Pr.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://pr.com/
630
https://pr.com/
480
https://www.pr.com/
0

Other

First Contentful Paint (3G) — 6417.5 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.
65

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of pr.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.
`[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.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
`[aria-hidden="true"]` is not present on the document `<body>`
If aria-hidden=true is set on the document body, assistive technologies, like a screen reader will work inconsistently.
`[aria-hidden="true"]` elements do not contain focusable descendents
Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.
ARIA input fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when an input field does not have an accessible name specified.
`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.
`[role]`s are contained by their required parent element
Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.
`[role]` values are valid
All ARIA roles require valid values to perform their intended functions.
ARIA toggle fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when a toggle field does not have an accessible name specified.
`[aria-*]` attributes have valid values
ARIA attributes cannot be interpreted with invalid values when used by screen readers and other assistive technologies.
`[aria-*]` attributes are valid and not misspelled
ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.
ARIA IDs are unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.

Names and labels

Buttons have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
`<frame>` or `<iframe>` elements have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Links have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.
`<object>` elements have `[alt]` text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<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"]`
Pr.com may provide assistance to deaf or hearing-impaired users with captions on videos.
`<video>` elements contain a `<track>` element with `[kind="description"]`
Pr.com may provide relevant information that dialogue cannot, by using audio descriptions.

Navigation

The page does not contain a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.
Some elements have 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.
Failing Elements

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

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

Names and labels

Form elements do not have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
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 pr.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

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
1.7.2
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.

Audits

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

Audits

Serves images with low resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.
URL Displayed size Actual size Expected size
https://www.pr.com/images/logo_home_1302.png
114 x 116
114 x 116
300 x 305
https://img.pr.com/article/1206/article_small_1340724602.jpg
92 x 57
92 x 57
242 x 150
https://img.pr.com/article/1208/article_small_1344540100.jpg
92 x 57
92 x 57
242 x 150
https://img.pr.com/article/1209/article_small_1348664121.jpg
92 x 57
92 x 57
242 x 150
https://www.pr.com/contrib/slir/index.php?i=release/2101/416814/pressrelease_416814_1611000888.png&w=92&h=57&c=92x57
92 x 57
92 x 57
242 x 150
https://www.pr.com/contrib/slir/index.php?i=release/2101/449117/pressrelease_449117_1610987310.jpg&w=92&h=57&c=92x57
92 x 57
92 x 57
242 x 150
https://www.pr.com/contrib/slir/index.php?i=release/2101/482600/pressrelease_482600_1610676521.jpg&w=92&h=57&c=92x57
92 x 57
92 x 57
242 x 150
https://www.pr.com/images/twitter_home.gif
18 x 14
18 x 14
48 x 37

Audits

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

SEO

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

Content Best Practices

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

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
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

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

Content Best Practices

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

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

Fast and reliable

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

PWA Optimized

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

Fast and reliable

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

Installable

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

PWA Optimized

Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Does not set a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Content is not sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of pr.com on mobile screens.
Does not provide a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.
Manifest doesn't have a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

Manual Checks

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

Server Location

Server IP Address: 34.195.83.150
Continent:
Country:
Region:
City:
Longitude:
Latitude:
Currencies:
Languages:

Web Hosting Provider

Name IP Address
Amazon Technologies Inc.
Registration

Domain Registrant

Private Registration: No
Name: PR Group, Inc.
Organization: PR Group, Inc.
Country: US
City: MELVILLE
State: NY
Post Code: 11747-3735
Email: DomainAdministration@PRGroupInc.com
Phone: +1.5165202000
Note: Registration information is derived from various sources and may be inaccurate.

Domain Registrar

Name IP Address
Network Solutions, LLC 162.159.134.53
Security

Visitor Safety

Mature Content: Not Likely
McAfee WebAdvisor Rating: Unknown
WOT Rating: 4.3/5 (2 reviews)
WOT Trustworthiness: 86/100
WOT Child Safety: 90/100
Note: Safety information is not guaranteed.

SSL/TLS Certificate

Issued To: pr.com
Issued By: Amazon
Valid From: 30th August, 2020
Valid To: 29th September, 2021
Subject: CN = pr.com
Hash: d71d2088
Issuer: CN = Amazon
OU = Server CA 1B
O = Amazon
S = US
Version: 2
Serial Number: 9660682276567651795176714537779597292
Serial Number (Hex): 074494690D4B687B1AA35A65BE6C0FEC
Valid From: 30th August, 2024
Valid To: 29th September, 2024
Signature Algorithm (Short Name): RSA-SHA256
Signature Algorithm (Long Name): sha256WithRSAEncryption
Authority Key Identifier: keyid:59:A4:66:06:52:A0:7B:95:92:3C:A3:94:07:27:96:74:5B:F9:3D:D0
Extended Key Usage: TLS Web Server Authentication, TLS Web Client Authentication
CRL Distribution Points:
Full Name:
URI:http://crl.sca1b.amazontrust.com/sca1b.crl

Certificate Policies: Policy: 2.16.840.1.114412.1.2
Policy: 2.23.140.1.2.1

Authority Information Access: OCSP - URI:http://ocsp.sca1b.amazontrust.com
CA Issuers - URI:http://crt.sca1b.amazontrust.com/sca1b.crt

SCT List: Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 7D:3E:F2:F8:8F:FF:88:55:68:24:C2:C0:CA:9E:52:89:
79:2B:C5:0E:78:09:7F:2E:6A:97:68:99:7E:22:F0:D7
Timestamp : Aug 30 15:25:06.942 2020 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:21:00:A2:42:78:78:79:15:69:39:D1:7F:9C:
2D:0F:E3:F9:88:1A:EC:38:FB:8E:E5:4A:F0:3B:A7:7E:
CE:FB:85:3C:E9:02:20:5D:3B:CF:C4:26:AF:86:A9:E2:
7E:EA:63:8C:8C:0A:86:AA:9E:69:8B:BB:C0:24:40:C3:
B6:7F:E9:97:CB:F8:9B
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 : Aug 30 15:25:06.927 2020 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:46:02:21:00:DE:22:DF:92:1E:45:F6:26:6E:38:8B:
D7:E5:9D:BA:B5:71:37:43:C1:F4:24:5D:CC:56:86:2D:
86:A1:5E:C0:A8:02:21:00:F7:C4:B1:66:5B:E8:D6:AB:
5C:64:15:B8:21:D4:6A:6F:F8:9A:BA:A8:44:E2:4C:A0:
C6:43:F1:79:7D:F5:B2:E5
Key Usage: Digital Signature, Key Encipherment
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:*.pr.com
DNS:pr.com
Technical

DNS Lookup

A Records

Host IP Address Class TTL
pr.com. 107.23.209.109 IN 59
pr.com. 34.195.83.150 IN 59

NS Records

Host Nameserver Class TTL
pr.com. ns-1330.awsdns-38.org. IN 21599
pr.com. ns-1935.awsdns-49.co.uk. IN 21599
pr.com. ns-476.awsdns-59.com. IN 21599
pr.com. ns-682.awsdns-21.net. IN 21599

MX Records

Priority Host Server Class TTL
10 pr.com. pr-com.mail.protection.outlook.com. IN 599

SOA Records

Domain Name Primary NS Responsible Email TTL
pr.com. ns-1935.awsdns-49.co.uk. awsdns-hostmaster.amazon.com. 899

TXT Records

Host Value Class TTL
pr.com. MS=ms80787436 IN 599
pr.com. v=spf1 IN 599

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Date: 19th January, 2021
Content-Type: text/html; charset=utf-8
Server: Apache/2.4.6 (CentOS)
Expires: 19th November, 1981
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Connection: keep-alive
Set-Cookie: *
Pragma: no-cache

Whois Lookup

Created: 9th April, 1999
Changed: 24th September, 2020
Expires: 9th April, 2030
Registrar: Network Solutions, LLC
Status: clientTransferProhibited
Nameservers: ns-1330.awsdns-38.org
ns-1935.awsdns-49.co.uk
ns-476.awsdns-59.com
ns-682.awsdns-21.net
Owner Name: PR Group, Inc.
Owner Organization: PR Group, Inc.
Owner Street: 525 BROADHOLLOW RD STE 10
Owner Post Code: 11747-3735
Owner City: MELVILLE
Owner State: NY
Owner Country: US
Owner Phone: +1.5165202000
Owner Email: DomainAdministration@PRGroupInc.com
Admin Name: Domain Administrator, PR Group, Inc.
Admin Organization: PR Group, Inc.
Admin Street: 525 Broadhollow Road
Admin Post Code: 11747-3735
Admin City: Melville
Admin State: NY
Admin Country: US
Admin Phone: +1.5165202000
Admin Email: DomainAdministration@PRGroupInc.com
Tech Name: Domain Administrator, PR Group, Inc.
Tech Organization: PR Group, Inc.
Tech Street: 525 Broadhollow Road
Tech Post Code: 11747-3735
Tech City: Melville
Tech State: NY
Tech Country: US
Tech Phone: +1.5165202000
Tech Email: DomainAdministration@PRGroupInc.com
Full Whois: Domain Name: PR.COM
Registry Domain ID: 5417505_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.networksolutions.com
Registrar URL: http://networksolutions.com
Updated Date: 2020-09-24T15:22:41Z
Creation Date: 1999-04-09T04:00:00Z
Registrar Registration Expiration Date: 2030-04-09T04:00:00Z
Registrar: Network Solutions, LLC
Registrar IANA ID: 2
Reseller:
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Registry Registrant ID:
Registrant Name: PR Group, Inc.
Registrant Organization: PR Group, Inc.
Registrant Street: 525 BROADHOLLOW RD STE 10
Registrant City: MELVILLE
Registrant State/Province: NY
Registrant Postal Code: 11747-3735
Registrant Country: US
Registrant Phone: +1.5165202000
Registrant Phone Ext:
Registrant Fax: +1.9999999999
Registrant Fax Ext:
Registrant Email: DomainAdministration@PRGroupInc.com
Registry Admin ID:
Admin Name: Domain Administrator, PR Group, Inc.
Admin Organization: PR Group, Inc.
Admin Street: 525 Broadhollow Road
Admin City: Melville
Admin State/Province: NY
Admin Postal Code: 11747-3735
Admin Country: US
Admin Phone: +1.5165202000
Admin Phone Ext:
Admin Fax: +1.5165201001
Admin Fax Ext:
Admin Email: DomainAdministration@PRGroupInc.com
Registry Tech ID:
Tech Name: Domain Administrator, PR Group, Inc.
Tech Organization: PR Group, Inc.
Tech Street: 525 Broadhollow Road
Tech City: Melville
Tech State/Province: NY
Tech Postal Code: 11747-3735
Tech Country: US
Tech Phone: +1.5165202000
Tech Phone Ext:
Tech Fax: +1.5165201001
Tech Fax Ext:
Tech Email: DomainAdministration@PRGroupInc.com
Name Server: NS-476.AWSDNS-59.COM
Name Server: NS-682.AWSDNS-21.NET
Name Server: NS-1330.AWSDNS-38.ORG
Name Server: NS-1935.AWSDNS-49.CO.UK
DNSSEC: unsigned
Registrar Abuse Contact Email: abuse@web.com
Registrar Abuse Contact Phone: +1.8003337680
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/
>>> Last update of WHOIS database: 2021-01-19T18:09:41Z <<<

For more information on Whois status codes, please visit https://www.icann.org/resources/pages/epp-status-codes-2014-06-16-en


The data in Networksolutions.com's WHOIS database is provided to you by
Networksolutions.com for information purposes only, that is, to assist you in
obtaining information about or related to a domain name registration
record. Networksolutions.com makes this information available "as is," and
does not guarantee its accuracy. By submitting a WHOIS query, you
agree that you will use this data only for lawful purposes and that,
under no circumstances will you use this data to: (1) allow, enable,
or otherwise support the transmission of mass unsolicited, commercial
advertising or solicitations via direct mail, electronic mail, or by
telephone; or (2) enable high volume, automated, electronic processes
that apply to Networksolutions.com (or its systems). The compilation,
repackaging, dissemination or other use of this data is expressly
prohibited without the prior written consent of Networksolutions.com.
Networksolutions.com reserves the right to modify these terms at any time.
By submitting this query, you agree to abide by these terms.

For more information on Whois status codes, please visit
https://www.icann.org/resources/pages/epp-status-codes-2014-06-16-en.

Nameservers

Name IP Address
ns-1330.awsdns-38.org 205.251.197.50
ns-1935.awsdns-49.co.uk 205.251.199.143
ns-476.awsdns-59.com 205.251.193.220
ns-682.awsdns-21.net 205.251.194.170
Related

Subdomains

Similar Sites

Domain Valuation Snoop Score
$14,927 USD 3/5
$5,946 USD 2/5
$416 USD 2/5
$955 USD 2/5
$3,709 USD 2/5

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Domain Valuation Snoop Score
0/5
0/5
$179 USD
0/5

Sites hosted on the same IP address