Tools & Wizards About Us
wiesenthal.com screenshot

Report Summary

  • 28

    Performance

    Renders faster than
    48% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 72% of websites

  • 0

    Best Practices

  • 74

    SEO

    Google-friendlier than
    32% of websites

wiesenthal.com

Simon Wiesenthal Center

Page Load Speed

2 sec in total

First Response

295 ms

Resources Loaded

1.5 sec

Page Rendered

208 ms

wiesenthal.com screenshot

About Website

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

The Simon Wiesenthal Center is a Jewish global human rights organization researching the Holocaust and hate in a historic and contemporary context.

Visit wiesenthal.com

Key Findings

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

Performance Metrics

wiesenthal.com performance score

28

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.4 s

17/100

10%

LCP (Largest Contentful Paint)

Value15.5 s

0/100

25%

SI (Speed Index)

Value4.6 s

71/100

10%

TBT (Total Blocking Time)

Value670 ms

45/100

30%

CLS (Cumulative Layout Shift)

Value0.352

32/100

15%

TTI (Time to Interactive)

Value15.8 s

7/100

10%

Network Requests Diagram

wiesenthal.com

295 ms

lookup.asp

288 ms

pp.asp

144 ms

default.css

23 ms

content.css

94 ms

Our browser made a total of 55 requests to load all elements on the main page. We found that 62% of them (34 requests) were addressed to the original Wiesenthal.com, 11% (6 requests) were made to Segments.adaptv.advertising.com and 9% (5 requests) were made to Kintera.com. The less responsive or slowest element that took the longest time to load (360 ms) belongs to the original domain Wiesenthal.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 472.5 kB (53%)

Content Size

891.3 kB

After Optimization

418.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Wiesenthal.com main page is 891.3 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. 40% of websites need less resources to load. Javascripts take 513.2 kB which makes up the majority of the site volume.

HTML Optimization

-70%

Potential reduce by 45.5 kB

  • Original 65.0 kB
  • After minification 64.0 kB
  • After compression 19.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 45.5 kB or 70% of the original size.

Image Optimization

-7%

Potential reduce by 16.3 kB

  • Original 225.1 kB
  • After minification 208.9 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. Wiesenthal images are well optimized though.

JavaScript Optimization

-65%

Potential reduce by 334.3 kB

  • Original 513.2 kB
  • After minification 511.4 kB
  • After compression 179.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 334.3 kB or 65% of the original size.

CSS Optimization

-87%

Potential reduce by 76.5 kB

  • Original 87.8 kB
  • After minification 59.2 kB
  • After compression 11.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. Wiesenthal.com needs all CSS files to be minified and compressed as it can save up to 76.5 kB or 87% of the original size.

Requests Breakdown

Number of requests can be reduced by 31 (61%)

Requests Now

51

After Optimization

20

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

wiesenthal.com

wiesenthal.com

295 ms

lookup.asp

lookup.asp

288 ms

pp.asp

pp.asp

144 ms

default.css

default.css

23 ms

content.css

content.css

94 ms

swc-home-spherev17.css

swc-home-spherev17.css

83 ms

util.js

util.js

149 ms

jquery.js

jquery.js

360 ms

jquery.cycle.all.min.js

jquery.cycle.all.min.js

16 ms

jquery.min.js

jquery.min.js

34 ms

jquery.cycle.all.js

jquery.cycle.all.js

71 ms

inlinecontentlisting.css

inlinecontentlisting.css

101 ms

addthis_widget.js

addthis_widget.js

11 ms

analytics.js

analytics.js

44 ms

iconarrowSearch.png

iconarrowSearch.png

156 ms

buttonblueArrow.png

buttonblueArrow.png

137 ms

iconfacebook.png

iconfacebook.png

142 ms

icontwitter.png

icontwitter.png

151 ms

iconyoutube.png

iconyoutube.png

141 ms

bgbody.png

bgbody.png

131 ms

bgshadow.png

bgshadow.png

24 ms

bgutility.png

bgutility.png

127 ms

bgutilityNavleft.png

bgutilityNavleft.png

152 ms

bgutilityNavright.png

bgutilityNavright.png

123 ms

bgheader.png

bgheader.png

123 ms

logo.png

logo.png

122 ms

tnav2.gif

tnav2.gif

126 ms

tnav73.gif

tnav73.gif

202 ms

tnav10.gif

tnav10.gif

202 ms

tnav4.gif

tnav4.gif

129 ms

tnav1_on.gif

tnav1_on.gif

133 ms

bgmedia.png

bgmedia.png

202 ms

Hollywood-Reporter_1-home.jpg

Hollywood-Reporter_1-home.jpg

283 ms

Hollywood-Reporter_3-home.jpg

Hollywood-Reporter_3-home.jpg

145 ms

iconnews.png

iconnews.png

225 ms

BGSUPPORTCENTER2.JPG

BGSUPPORTCENTER2.JPG

360 ms

button.jpg

button.jpg

282 ms

bgsecondaryNav.png

bgsecondaryNav.png

277 ms

bgwrapSocialNetworking.png

bgwrapSocialNetworking.png

279 ms

shop.jpg

shop.jpg

313 ms

shop_ma.jpg

shop_ma.jpg

356 ms

mot_logo_home_footer.jpg

mot_logo_home_footer.jpg

355 ms

BTN_SHARED_BUTTON.GIF

BTN_SHARED_BUTTON.GIF

360 ms

collect

collect

53 ms

300lo.json

300lo.json

43 ms

sh.7c7179124ea24ac6ba46caac.html

sh.7c7179124ea24ac6ba46caac.html

66 ms

6 ms

ca.html

ca.html

30 ms

5 ms

6 ms

5 ms

7 ms

6 ms

pixel

pixel

21 ms

pixel

pixel

21 ms

Accessibility Review

wiesenthal.com accessibility score

89

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.

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

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

SEO Factors

wiesenthal.com SEO score

74

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

    N/A

  • Encoding

    ISO-8859-1

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

wiesenthal.com

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