Report Summary

  • 21

    Performance

    Renders faster than
    39% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 48% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

inpublicsafety.com

Public Safety Archives - Edge

Page Load Speed

4.5 sec in total

First Response

746 ms

Resources Loaded

3.5 sec

Page Rendered

335 ms

inpublicsafety.com screenshot

About Website

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

Here you'll find resources geared toward public servants

Visit inpublicsafety.com

Key Findings

We analyzed Inpublicsafety.com page load time and found that the first response time was 746 ms and then it took 3.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

inpublicsafety.com performance score

21

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

20/100

10%

LCP (Largest Contentful Paint)

Value8.6 s

1/100

25%

SI (Speed Index)

Value7.1 s

31/100

10%

TBT (Total Blocking Time)

Value5,290 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.003

100/100

15%

TTI (Time to Interactive)

Value16.0 s

6/100

10%

Network Requests Diagram

inpublicsafety.com

746 ms

style.css

128 ms

diggdigg-style.css

111 ms

jquery.js

271 ms

jquery-migrate.min.js

129 ms

Our browser made a total of 98 requests to load all elements on the main page. We found that 33% of them (32 requests) were addressed to the original Inpublicsafety.com, 16% (16 requests) were made to Static.xx.fbcdn.net and 10% (10 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (746 ms) belongs to the original domain Inpublicsafety.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 621.0 kB (55%)

Content Size

1.1 MB

After Optimization

516.4 kB

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

HTML Optimization

-78%

Potential reduce by 57.5 kB

  • Original 73.9 kB
  • After minification 70.3 kB
  • After compression 16.5 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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 57.5 kB or 78% of the original size.

Image Optimization

-2%

Potential reduce by 7.3 kB

  • Original 302.0 kB
  • After minification 294.7 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. In Public Safety images are well optimized though.

JavaScript Optimization

-65%

Potential reduce by 282.7 kB

  • Original 434.0 kB
  • After minification 431.8 kB
  • After compression 151.2 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 282.7 kB or 65% of the original size.

CSS Optimization

-84%

Potential reduce by 273.5 kB

  • Original 327.5 kB
  • After minification 306.1 kB
  • After compression 54.0 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. Inpublicsafety.com needs all CSS files to be minified and compressed as it can save up to 273.5 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 51 (58%)

Requests Now

88

After Optimization

37

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

Accessibility Review

inpublicsafety.com accessibility score

79

Accessibility Issues

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

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

SEO Factors

inpublicsafety.com SEO score

75

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

Content Best Practices

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

Impact

Issue

High

Image elements do not have [alt] attributes

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

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