Tools & Wizards About Us
publicrelay.com screenshot

Report Summary

  • 39

    Performance

    Renders faster than
    58% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

publicrelay.com

PublicRelay: Where Data-Driven Powers Market-Leading

Page Load Speed

1 sec in total

First Response

16 ms

Resources Loaded

534 ms

Page Rendered

481 ms

publicrelay.com screenshot

About Website

Visit publicrelay.com now to see the best up-to-date Public Relay content for United States and also check out these interesting facts you probably never knew about publicrelay.com

Empowering brand leaders to provide data-driven guidance, deliver against company goals, and expand the impact of communications.

Visit publicrelay.com

Key Findings

We analyzed Publicrelay.com page load time and found that the first response time was 16 ms and then it took 1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.

Performance Metrics

publicrelay.com performance score

39

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

39/100

10%

LCP (Largest Contentful Paint)

Value3.7 s

59/100

25%

SI (Speed Index)

Value10.3 s

8/100

10%

TBT (Total Blocking Time)

Value1,200 ms

20/100

30%

CLS (Cumulative Layout Shift)

Value0.175

69/100

15%

TTI (Time to Interactive)

Value9.8 s

28/100

10%

Network Requests Diagram

publicrelay.com

16 ms

publicrelay.com

63 ms

css2

81 ms

api.js

87 ms

script.js

155 ms

Our browser made a total of 34 requests to load all elements on the main page. We found that 62% of them (21 requests) were addressed to the original Publicrelay.com, 12% (4 requests) were made to Fonts.gstatic.com and 6% (2 requests) were made to Cdnjs.cloudflare.com. The less responsive or slowest element that took the longest time to load (294 ms) relates to the external source Googletagmanager.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 270.0 kB (34%)

Content Size

800.6 kB

After Optimization

530.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Publicrelay.com main page is 800.6 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 55% of websites need less resources to load. Javascripts take 508.1 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 157.8 kB

  • Original 196.9 kB
  • After minification 169.6 kB
  • After compression 39.1 kB

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. This page needs HTML code to be minified as it can gain 27.3 kB, which is 14% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 157.8 kB or 80% of the original size.

Image Optimization

-33%

Potential reduce by 1.7 kB

  • Original 5.3 kB
  • After minification 3.6 kB

Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Obviously, Public Relay needs image optimization as it can save up to 1.7 kB or 33% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-13%

Potential reduce by 63.5 kB

  • Original 508.1 kB
  • After minification 508.0 kB
  • After compression 444.6 kB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 63.5 kB or 13% of the original size.

CSS Optimization

-52%

Potential reduce by 46.9 kB

  • Original 90.3 kB
  • After minification 84.4 kB
  • After compression 43.4 kB

CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Publicrelay.com needs all CSS files to be minified and compressed as it can save up to 46.9 kB or 52% of the original size.

Requests Breakdown

Number of requests can be reduced by 19 (70%)

Requests Now

27

After Optimization

8

  • Images
  • JavaScript
  • CSS

The browser has sent 27 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Public Relay. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

publicrelay.com

publicrelay.com

16 ms

publicrelay.com

publicrelay.com

63 ms

css2

css2

81 ms

api.js

api.js

87 ms

script.js

script.js

155 ms

style.min.css

style.min.css

14 ms

cookie-law-info-public.css

cookie-law-info-public.css

46 ms

cookie-law-info-gdpr.css

cookie-law-info-gdpr.css

67 ms

style.css

style.css

67 ms

style.min.css

style.min.css

68 ms

replacement_icons.css

replacement_icons.css

62 ms

jquery.min.js

jquery.min.js

66 ms

jquery-migrate.min.js

jquery-migrate.min.js

68 ms

cookie-law-info-public.js

cookie-law-info-public.js

71 ms

cookie-law-info-table.css

cookie-law-info-table.css

71 ms

ScrollMagic.min.js

ScrollMagic.min.js

79 ms

debug.addIndicators.min.js

debug.addIndicators.min.js

93 ms

scripts.min.js

scripts.min.js

92 ms

smush-lazy-load.min.js

smush-lazy-load.min.js

68 ms

addthis_widget.js

addthis_widget.js

93 ms

3908588.js

3908588.js

106 ms

js

js

294 ms

recaptcha__en.js

recaptcha__en.js

28 ms

true-check.svg

true-check.svg

106 ms

square-svg-shape.svg

square-svg-shape.svg

82 ms

pxiEyp8kv8JHgFVrFJA.ttf

pxiEyp8kv8JHgFVrFJA.ttf

45 ms

pxiByp8kv8JHgFVrLDz8V1s.ttf

pxiByp8kv8JHgFVrLDz8V1s.ttf

60 ms

pxiByp8kv8JHgFVrLEj6V1s.ttf

pxiByp8kv8JHgFVrLEj6V1s.ttf

61 ms

pxiByp8kv8JHgFVrLCz7V1s.ttf

pxiByp8kv8JHgFVrLCz7V1s.ttf

61 ms

1655299267.woff

1655299267.woff

20 ms

PublicRelay-Logo-Color.svg

PublicRelay-Logo-Color.svg

24 ms

subway.svg

subway.svg

22 ms

cruise.svg

cruise.svg

23 ms

Mask-group-1.png

Mask-group-1.png

22 ms

Accessibility Review

publicrelay.com accessibility score

88

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Names and labels

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

<frame> or <iframe> elements do not have a title

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

publicrelay.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

publicrelay.com SEO score

84

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

Mobile Friendly

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Publicrelay.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Publicrelay.com main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

publicrelay.com

Open Graph data is detected on the main page of Public Relay. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: