Tools & Wizards About Us
scansf.com screenshot

Report Summary

  • 33

    Performance

    Renders faster than
    53% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 48% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

scansf.com

ScanSF - San Francisco Police/Fire/EMS Scanner

Page Load Speed

1.5 sec in total

First Response

186 ms

Resources Loaded

1.2 sec

Page Rendered

139 ms

scansf.com screenshot

About Website

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

Scan SF

Visit scansf.com

Key Findings

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

Performance Metrics

scansf.com performance score

33

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

40/100

10%

LCP (Largest Contentful Paint)

Value4.2 s

44/100

25%

SI (Speed Index)

Value5.2 s

60/100

10%

TBT (Total Blocking Time)

Value1,140 ms

22/100

30%

CLS (Cumulative Layout Shift)

Value0.5

16/100

15%

TTI (Time to Interactive)

Value9.9 s

27/100

10%

Network Requests Diagram

scansf.com

186 ms

jplayer.blue.monday.css

31 ms

style.css

54 ms

jquery.min.js

46 ms

jquery.jplayer.min.js

65 ms

Our browser made a total of 54 requests to load all elements on the main page. We found that 20% of them (11 requests) were addressed to the original Scansf.com, 22% (12 requests) were made to Coinbase.com and 13% (7 requests) were made to Cdn.livestream.com. The less responsive or slowest element that took the longest time to load (545 ms) relates to the external source Googleads.g.doubleclick.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.0 MB (71%)

Content Size

1.4 MB

After Optimization

425.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Scansf.com main page is 1.4 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. 50% of websites need less resources to load. CSS take 707.3 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 9.8 kB

  • Original 12.7 kB
  • After minification 11.0 kB
  • After compression 2.9 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 1.8 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 9.8 kB or 77% of the original size.

Image Optimization

-5%

Potential reduce by 1.9 kB

  • Original 36.2 kB
  • After minification 34.3 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. ScanSF images are well optimized though.

JavaScript Optimization

-62%

Potential reduce by 430.9 kB

  • Original 690.6 kB
  • After minification 688.1 kB
  • After compression 259.7 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 430.9 kB or 62% of the original size.

CSS Optimization

-82%

Potential reduce by 578.9 kB

  • Original 707.3 kB
  • After minification 703.0 kB
  • After compression 128.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. Scansf.com needs all CSS files to be minified and compressed as it can save up to 578.9 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 34 (65%)

Requests Now

52

After Optimization

18

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

scansf.com

scansf.com

186 ms

jplayer.blue.monday.css

jplayer.blue.monday.css

31 ms

style.css

style.css

54 ms

jquery.min.js

jquery.min.js

46 ms

jquery.jplayer.min.js

jquery.jplayer.min.js

65 ms

main.js

main.js

51 ms

widgets.js

widgets.js

5 ms

button.js

button.js

123 ms

adsbygoogle.js

adsbygoogle.js

5 ms

analytics.js

analytics.js

24 ms

display_hp.php

display_hp.php

107 ms

display_996xt.php

display_996xt.php

103 ms

display_sffd.php

display_sffd.php

96 ms

scansf

scansf

148 ms

ScanSF_header.png

ScanSF_header.png

88 ms

jplayer.blue.monday.jpg

jplayer.blue.monday.jpg

255 ms

collect

collect

84 ms

jquery-1.8.3.min.js

jquery-1.8.3.min.js

119 ms

collect

collect

52 ms

collect

collect

58 ms

collect

collect

79 ms

ca-pub-9295308861771808.js

ca-pub-9295308861771808.js

191 ms

zrt_lookup.html

zrt_lookup.html

154 ms

show_ads_impl.js

show_ads_impl.js

82 ms

collect

collect

179 ms

embed-min.css

embed-min.css

53 ms

video-min.css

video-min.css

126 ms

json-min.js

json-min.js

135 ms

embed-min.js

embed-min.js

136 ms

ads

ads

545 ms

osd.js

osd.js

21 ms

print.css

print.css

38 ms

mask.png

mask.png

28 ms

alert.png

alert.png

51 ms

30c3e1ba57a9da72643a1b9299dab9aa

30c3e1ba57a9da72643a1b9299dab9aa

51 ms

widget

widget

65 ms

core-3d6b331ebfc5605fa69af75fc5d29bb14a9446e2486c757435a044e837f9148b.css

core-3d6b331ebfc5605fa69af75fc5d29bb14a9446e2486c757435a044e837f9148b.css

41 ms

application-120dd394564832f3dfe6734a83be74704800b475649c9ebf9087b04686a969c9.css

application-120dd394564832f3dfe6734a83be74704800b475649c9ebf9087b04686a969c9.css

61 ms

jquery_turbolinks_bundle-f381d7a450360b4356aa00942b65d7eaa6826a4fa4b52dbf55c4c2d1aa7edbf5.js

jquery_turbolinks_bundle-f381d7a450360b4356aa00942b65d7eaa6826a4fa4b52dbf55c4c2d1aa7edbf5.js

108 ms

application-91e703ece9957898dc80837cf3f753a324698519d09cfcdb6c288db5186acc04.js

application-91e703ece9957898dc80837cf3f753a324698519d09cfcdb6c288db5186acc04.js

147 ms

checkouts-a7727126f9268e96ef00481aae4290e6e4e9bfd986fece25f4864643f7302ef0.css

checkouts-a7727126f9268e96ef00481aae4290e6e4e9bfd986fece25f4864643f7302ef0.css

20 ms

jquery-c64a74367bda6ef8b860f19e74df08927ca99d2be2ac934e9e92d5fd361e0da4.js

jquery-c64a74367bda6ef8b860f19e74df08927ca99d2be2ac934e9e92d5fd361e0da4.js

75 ms

checkouts-ae21dc9ff88e867028bd92792ca63d65a0b2fb41be3512821a3c84475ce696ef.js

checkouts-ae21dc9ff88e867028bd92792ca63d65a0b2fb41be3512821a3c84475ce696ef.js

110 ms

nr-885.min.js

nr-885.min.js

308 ms

buy

buy

333 ms

mixpanel-93b71aeea19b1062b748c2b5f60ed43879b69db239dd99f80e423b1d56c29abd.js

mixpanel-93b71aeea19b1062b748c2b5f60ed43879b69db239dd99f80e423b1d56c29abd.js

209 ms

sb.js

sb.js

229 ms

donation_small-c2401ae30dd0ad6018deadfc4bb506bf56b5b7062738ee449bee97c4e80ec70c.png

donation_small-c2401ae30dd0ad6018deadfc4bb506bf56b5b7062738ee449bee97c4e80ec70c.png

42 ms

m_js_controller.js

m_js_controller.js

49 ms

abg.js

abg.js

72 ms

googlelogo_color_112x36dp.png

googlelogo_color_112x36dp.png

70 ms

nessie_icon_tiamat_white.png

nessie_icon_tiamat_white.png

58 ms

s

s

46 ms

x_button_blue2.png

x_button_blue2.png

32 ms

Accessibility Review

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

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

High

Image elements do not have [alt] attributes

Best Practices

scansf.com best practices score

58

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

scansf.com SEO score

92

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

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Scansf.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Scansf.com main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

scansf.com

Open Graph description is not detected on the main page of ScanSF. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: