Tools & Wizards About Us
frumtoronto.com screenshot

Report Summary

  • 49

    Performance

    Renders faster than
    67% of other websites

  • 42

    Accessibility

    Visual factors better than
    that of 19% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 42

    SEO

    Google-friendlier than
    18% of websites

frumtoronto.com

FrumToronto - Toronto Jewish Orthodox Community Gateway

Page Load Speed

1.2 sec in total

First Response

74 ms

Resources Loaded

971 ms

Page Rendered

198 ms

frumtoronto.com screenshot

About Website

Click here to check amazing Frum Toronto content for Canada. Otherwise, check out these important facts you probably never knew about frumtoronto.com

The Toronto Jewish Orthodox Community Gateway. Connecting the community with businesses, shuls, events, classifieds, and resources.

Visit frumtoronto.com

Key Findings

We analyzed Frumtoronto.com page load time and found that the first response time was 74 ms and then it took 1.2 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

frumtoronto.com performance score

49

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

41/100

10%

LCP (Largest Contentful Paint)

Value4.1 s

47/100

25%

SI (Speed Index)

Value4.4 s

73/100

10%

TBT (Total Blocking Time)

Value670 ms

44/100

30%

CLS (Cumulative Layout Shift)

Value0.191

64/100

15%

TTI (Time to Interactive)

Value9.3 s

31/100

10%

Network Requests Diagram

frumtoronto.com

74 ms

www.frumtoronto.com

438 ms

FrumWebDirector.css

134 ms

marquee.js

118 ms

kdate.js

143 ms

Our browser made a total of 47 requests to load all elements on the main page. We found that 70% of them (33 requests) were addressed to the original Frumtoronto.com, 9% (4 requests) were made to Platform.twitter.com and 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (438 ms) belongs to the original domain Frumtoronto.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 261.7 kB (39%)

Content Size

669.5 kB

After Optimization

407.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Frumtoronto.com main page is 669.5 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. 45% of websites need less resources to load. Images take 363.1 kB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 111.5 kB

  • Original 129.8 kB
  • After minification 116.1 kB
  • After compression 18.3 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 13.7 kB, which is 11% 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 111.5 kB or 86% of the original size.

Image Optimization

-4%

Potential reduce by 13.0 kB

  • Original 363.1 kB
  • After minification 350.2 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. Frum Toronto images are well optimized though.

JavaScript Optimization

-76%

Potential reduce by 116.7 kB

  • Original 152.8 kB
  • After minification 105.7 kB
  • After compression 36.0 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 116.7 kB or 76% of the original size.

CSS Optimization

-86%

Potential reduce by 20.5 kB

  • Original 23.8 kB
  • After minification 16.1 kB
  • After compression 3.2 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. Frumtoronto.com needs all CSS files to be minified and compressed as it can save up to 20.5 kB or 86% of the original size.

Requests Breakdown

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

Requests Now

43

After Optimization

21

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

frumtoronto.com

frumtoronto.com

74 ms

www.frumtoronto.com

www.frumtoronto.com

438 ms

FrumWebDirector.css

FrumWebDirector.css

134 ms

marquee.js

marquee.js

118 ms

kdate.js

kdate.js

143 ms

ksun.js

ksun.js

101 ms

kzmanim.js

kzmanim.js

108 ms

Ajax.js

Ajax.js

226 ms

AC_RunActiveContent.js

AC_RunActiveContent.js

145 ms

HebrewDate.js

HebrewDate.js

137 ms

Omer.js

Omer.js

111 ms

widgets.js

widgets.js

6 ms

counter_xhtml.js

counter_xhtml.js

22 ms

GoogleAnalyticsScript.js

GoogleAnalyticsScript.js

27 ms

ga.js

ga.js

8 ms

__utm.gif

__utm.gif

12 ms

bg.jpg

bg.jpg

92 ms

MainHeader.JPG

MainHeader.JPG

113 ms

Submit.gif

Submit.gif

71 ms

x.gif

x.gif

91 ms

loginblue.gif

loginblue.gif

70 ms

line1.jpg

line1.jpg

91 ms

invisible.gif

invisible.gif

112 ms

horzline.jpg

horzline.jpg

113 ms

arrow-r.gif

arrow-r.gif

139 ms

left.gif

left.gif

139 ms

right.gif

right.gif

139 ms

AskTheRabbi.jpg

AskTheRabbi.jpg

170 ms

Rav_Miller.jpg

Rav_Miller.jpg

243 ms

rav_felder.jpeg

rav_felder.jpeg

154 ms

ChofetzChaim.jpg

ChofetzChaim.jpg

169 ms

spacer.gif

spacer.gif

172 ms

invisible.gif

invisible.gif

170 ms

Torontoinfoemail.jpg

Torontoinfoemail.jpg

309 ms

powered_by.jpg

powered_by.jpg

206 ms

boxc.jpg

boxc.jpg

206 ms

all.js

all.js

46 ms

GetCommunityBlog_xml.asp

GetCommunityBlog_xml.asp

216 ms

all.js

all.js

18 ms

40 ms

template8.php

template8.php

17 ms

t.php

t.php

131 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

34 ms

settings

settings

69 ms

button.856debeac157d9669cf51e73a08fbc93.js

button.856debeac157d9669cf51e73a08fbc93.js

2 ms

embeds

embeds

22 ms

follow_button.2f70fb173b9000da126c79afe2098f02.en.html

follow_button.2f70fb173b9000da126c79afe2098f02.en.html

12 ms

Accessibility Review

frumtoronto.com accessibility score

42

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

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

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

frumtoronto.com best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

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

SEO Factors

frumtoronto.com SEO score

42

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

High

Image elements do not have [alt] attributes

High

Document uses plugins

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Frumtoronto.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Frumtoronto.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

frumtoronto.com

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