Tools & Wizards About Us
cambridgefirefighters.com screenshot

Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 56

    Accessibility

    Visual factors better than
    that of 24% of websites

  • 50

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

cambridgefirefighters.com

Cambridge Professional Fire Fighters' Association

Page Load Speed

2.8 sec in total

First Response

473 ms

Resources Loaded

1.9 sec

Page Rendered

424 ms

cambridgefirefighters.com screenshot

About Website

Visit cambridgefirefighters.com now to see the best up-to-date Cambridge Fire Fighters content and also check out these interesting facts you probably never knew about cambridgefirefighters.com

The Ultimate Website Management and Communications Tool for Unions

Visit cambridgefirefighters.com

Key Findings

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

Performance Metrics

cambridgefirefighters.com performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

23/100

10%

LCP (Largest Contentful Paint)

Value16.7 s

0/100

25%

SI (Speed Index)

Value8.6 s

17/100

10%

TBT (Total Blocking Time)

Value4,190 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.078

95/100

15%

TTI (Time to Interactive)

Value18.4 s

3/100

10%

Network Requests Diagram

www.cambridgefirefighters.com

473 ms

cfform.js

191 ms

masks.js

247 ms

tundra.css

20 ms

site1r.css

401 ms

Our browser made a total of 143 requests to load all elements on the main page. We found that 27% of them (38 requests) were addressed to the original Cambridgefirefighters.com, 66% (94 requests) were made to Ajax.googleapis.com and 3% (5 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (564 ms) belongs to the original domain Cambridgefirefighters.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 244.4 kB (16%)

Content Size

1.5 MB

After Optimization

1.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Cambridgefirefighters.com main page is 1.5 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 932.7 kB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 90.9 kB

  • Original 106.4 kB
  • After minification 93.8 kB
  • After compression 15.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. This page needs HTML code to be minified as it can gain 12.6 kB, which is 12% 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 90.9 kB or 85% of the original size.

Image Optimization

-3%

Potential reduce by 27.9 kB

  • Original 932.7 kB
  • After minification 904.8 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. Cambridge Fire Fighters images are well optimized though.

JavaScript Optimization

-26%

Potential reduce by 111.8 kB

  • Original 424.1 kB
  • After minification 416.5 kB
  • After compression 312.3 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 111.8 kB or 26% of the original size.

CSS Optimization

-17%

Potential reduce by 13.9 kB

  • Original 80.8 kB
  • After minification 76.5 kB
  • After compression 66.9 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. Cambridgefirefighters.com needs all CSS files to be minified and compressed as it can save up to 13.9 kB or 17% of the original size.

Requests Breakdown

Number of requests can be reduced by 117 (84%)

Requests Now

139

After Optimization

22

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.cambridgefirefighters.com

www.cambridgefirefighters.com

473 ms

cfform.js

cfform.js

191 ms

masks.js

masks.js

247 ms

tundra.css

tundra.css

20 ms

site1r.css

site1r.css

401 ms

adminsite.css

adminsite.css

260 ms

dojo.js

dojo.js

26 ms

site.js

site.js

260 ms

nodefire.js

nodefire.js

345 ms

styles.css

styles.css

307 ms

nodefire.js

nodefire.js

341 ms

styles.css

styles.css

283 ms

qtp_library.css

qtp_library.css

221 ms

css3-mediaqueries.js

css3-mediaqueries.js

252 ms

TooltipDialog.js

TooltipDialog.js

33 ms

DropDownButton.js

DropDownButton.js

95 ms

ContentPane.js

ContentPane.js

95 ms

ContentPane.js

ContentPane.js

97 ms

TabContainer.js

TabContainer.js

95 ms

scroll.js

scroll.js

96 ms

parser.js

parser.js

97 ms

bkgrd_IAFF5.jpg

bkgrd_IAFF5.jpg

285 ms

www.cambridgefirefighters.com

www.cambridgefirefighters.com

218 ms

cpffalogo-fullcolor-XS-digital.png

cpffalogo-fullcolor-XS-digital.png

204 ms

home.png

home.png

139 ms

menu.png

menu.png

145 ms

1.jpg

1.jpg

204 ms

2.jpg

2.jpg

282 ms

3.jpg

3.jpg

282 ms

4.jpg

4.jpg

560 ms

5.jpg

5.jpg

282 ms

spacer.png

spacer.png

286 ms

facebook_page_icon.png

facebook_page_icon.png

560 ms

twitter_page_icon.png

twitter_page_icon.png

560 ms

rss-icon.png

rss-icon.png

561 ms

IMG_2669[1].JPG

IMG_2669[1].JPG

561 ms

Rapid%20Fire%20Growth-poster.jpg

Rapid%20Fire%20Growth-poster.jpg

561 ms

Why%20you%20have%20less%20time%20to%20escape%20a%20house%20fire%20today%20than%2030%20years%20ago%20-%20TODAY-com%202-poster.jpg

Why%20you%20have%20less%20time%20to%20escape%20a%20house%20fire%20today%20than%2030%20years%20ago%20-%20TODAY-com%202-poster.jpg

561 ms

Edworthy%20Side%20Rd.jpg

Edworthy%20Side%20Rd.jpg

564 ms

UALOGO.jpg

UALOGO.jpg

562 ms

footer_anchor.png

footer_anchor.png

561 ms

site1r.css

site1r.css

550 ms

focus.js

focus.js

56 ms

_DialogMixin.js

_DialogMixin.js

59 ms

_FormMixin.js

_FormMixin.js

59 ms

_TemplatedMixin.js

_TemplatedMixin.js

58 ms

main.js

main.js

59 ms

FOP86_3.png

FOP86_3.png

527 ms

Rotator.js

Rotator.js

54 ms

AutoRotator.js

AutoRotator.js

55 ms

Controller.js

Controller.js

55 ms

Fade.js

Fade.js

55 ms

flex-direction-nav.png

flex-direction-nav.png

521 ms

qr1xO210h6E

qr1xO210h6E

138 ms

arrow1_down.gif

arrow1_down.gif

478 ms

arrow1_right.gif

arrow1_right.gif

478 ms

down.png

down.png

511 ms

Tooltip.js

Tooltip.js

36 ms

Pan.js

Pan.js

34 ms

registry.js

registry.js

34 ms

popup.js

popup.js

32 ms

Button.js

Button.js

31 ms

_Container.js

_Container.js

31 ms

_HasDropDown.js

_HasDropDown.js

34 ms

a11yclick.js

a11yclick.js

36 ms

_Widget.js

_Widget.js

33 ms

_ContentPaneResizeMixin.js

_ContentPaneResizeMixin.js

34 ms

string.js

string.js

33 ms

html.js

html.js

35 ms

loading.js

loading.js

34 ms

_TabContainerBase.js

_TabContainerBase.js

36 ms

TabController.js

TabController.js

35 ms

ScrollingTabController.js

ScrollingTabController.js

35 ms

Stateful.js

Stateful.js

35 ms

window.js

window.js

36 ms

a11y.js

a11y.js

36 ms

_base.js

_base.js

36 ms

_base.js

_base.js

36 ms

_core.js

_core.js

35 ms

url.js

url.js

36 ms

all.js

all.js

57 ms

stamp.js

stamp.js

56 ms

cache.js

cache.js

58 ms

_AttachMixin.js

_AttachMixin.js

56 ms

easing.js

easing.js

56 ms

fx.js

fx.js

56 ms

_FormWidget.js

_FormWidget.js

20 ms

_ButtonMixin.js

_ButtonMixin.js

20 ms

manager.js

manager.js

22 ms

place.js

place.js

19 ms

BackgroundIframe.js

BackgroundIframe.js

20 ms

Viewport.js

Viewport.js

20 ms

touch.js

touch.js

21 ms

_FocusMixin.js

_FocusMixin.js

19 ms

_WidgetBase.js

_WidgetBase.js

20 ms

_OnDijitClickMixin.js

_OnDijitClickMixin.js

20 ms

uacss.js

uacss.js

20 ms

hccss.js

hccss.js

21 ms

utils.js

utils.js

21 ms

StackController.js

StackController.js

18 ms

Menu.js

Menu.js

19 ms

MenuItem.js

MenuItem.js

18 ms

common.js

common.js

19 ms

_WidgetsInTemplateMixin.js

_WidgetsInTemplateMixin.js

33 ms

StackContainer.js

StackContainer.js

33 ms

_CssStateMixin.js

_CssStateMixin.js

14 ms

_FormWidgetMixin.js

_FormWidgetMixin.js

13 ms

Destroyable.js

Destroyable.js

11 ms

hccss.js

hccss.js

10 ms

ToggleButton.js

ToggleButton.js

9 ms

DropDownMenu.js

DropDownMenu.js

18 ms

_Contained.js

_Contained.js

18 ms

cookie.js

cookie.js

10 ms

_LayoutWidget.js

_LayoutWidget.js

9 ms

_ToggleButtonMixin.js

_ToggleButtonMixin.js

6 ms

blank.gif

blank.gif

6 ms

_MenuBase.js

_MenuBase.js

7 ms

regexp.js

regexp.js

6 ms

www-player.css

www-player.css

6 ms

www-embed-player.js

www-embed-player.js

33 ms

base.js

base.js

66 ms

_KeyNavContainer.js

_KeyNavContainer.js

28 ms

_KeyNavMixin.js

_KeyNavMixin.js

28 ms

Toggler.js

Toggler.js

274 ms

ad_status.js

ad_status.js

184 ms

QGccEJWqd_gIzr4UnyRjJu4DFpzUq3q8RcWI0eePlNs.js

QGccEJWqd_gIzr4UnyRjJu4DFpzUq3q8RcWI0eePlNs.js

140 ms

embed.js

embed.js

53 ms

_base.js

_base.js

49 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

60 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

66 ms

id

id

31 ms

WidgetSet.js

WidgetSet.js

17 ms

focus.js

focus.js

18 ms

place.js

place.js

16 ms

popup.js

popup.js

15 ms

scroll.js

scroll.js

15 ms

sniff.js

sniff.js

16 ms

typematic.js

typematic.js

17 ms

wai.js

wai.js

18 ms

window.js

window.js

22 ms

Create

Create

123 ms

selection.js

selection.js

106 ms

typematic.js

typematic.js

107 ms

Accessibility Review

cambridgefirefighters.com accessibility score

56

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

High

Links do not have a discernible name

High

<object> elements do not have alternate text

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

cambridgefirefighters.com best practices score

50

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

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

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

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Cambridgefirefighters.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 Cambridgefirefighters.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

cambridgefirefighters.com

Open Graph description is not detected on the main page of Cambridge Fire Fighters. 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: