Tools & Wizards About Us
santorum-2012.com screenshot

Report Summary

  • 60

    Performance

    Renders faster than
    75% of other websites

  • 61

    Accessibility

    Visual factors better than
    that of 27% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 87

    SEO

    Google-friendlier than
    65% of websites

santorum-2012.com

Santorum 2012

Page Load Speed

2.8 sec in total

First Response

367 ms

Resources Loaded

1.7 sec

Page Rendered

731 ms

santorum-2012.com screenshot

About Website

Welcome to santorum-2012.com homepage info - get ready to check Santorum 2012 best content right away, or after learning these important things about santorum-2012.com

This website is for people who are behind or want to be behind former Pennsylvania senator and current U.S. presidential candidate Rick Santorum. Thanks to you, we were the first Google result for...

Visit santorum-2012.com

Key Findings

We analyzed Santorum-2012.com page load time and found that the first response time was 367 ms and then it took 2.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

santorum-2012.com performance score

60

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

59/100

10%

LCP (Largest Contentful Paint)

Value5.4 s

21/100

25%

SI (Speed Index)

Value4.3 s

76/100

10%

TBT (Total Blocking Time)

Value430 ms

65/100

30%

CLS (Cumulative Layout Shift)

Value0.012

100/100

15%

TTI (Time to Interactive)

Value5.9 s

66/100

10%

Network Requests Diagram

santorum-2012.com

367 ms

pre_tumblelog.js

18 ms

reset.css

16 ms

jquery.min.js

15 ms

cufon-yui.js

32 ms

Our browser made a total of 56 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Santorum-2012.com, 16% (9 requests) were made to Googleads.g.doubleclick.net and 14% (8 requests) were made to Assets.tumblr.com. The less responsive or slowest element that took the longest time to load (654 ms) relates to the external source 40.media.tumblr.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.1 MB (31%)

Content Size

3.6 MB

After Optimization

2.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Santorum-2012.com main page is 3.6 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. 70% of websites need less resources to load. Images take 2.1 MB which makes up the majority of the site volume.

HTML Optimization

-73%

Potential reduce by 380.4 kB

  • Original 522.7 kB
  • After minification 514.2 kB
  • After compression 142.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. 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 380.4 kB or 73% of the original size.

Image Optimization

-5%

Potential reduce by 113.1 kB

  • Original 2.1 MB
  • After minification 2.0 MB

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. Santorum 2012 images are well optimized though.

JavaScript Optimization

-64%

Potential reduce by 633.7 kB

  • Original 995.3 kB
  • After minification 995.2 kB
  • After compression 361.5 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 633.7 kB or 64% of the original size.

CSS Optimization

-50%

Potential reduce by 641 B

  • Original 1.3 kB
  • After minification 1.3 kB
  • After compression 651 B

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. Santorum-2012.com needs all CSS files to be minified and compressed as it can save up to 641 B or 50% of the original size.

Requests Breakdown

Number of requests can be reduced by 26 (53%)

Requests Now

49

After Optimization

23

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

santorum-2012.com

santorum-2012.com

367 ms

pre_tumblelog.js

pre_tumblelog.js

18 ms

reset.css

reset.css

16 ms

jquery.min.js

jquery.min.js

15 ms

cufon-yui.js

cufon-yui.js

32 ms

cufon_300.font.js

cufon_300.font.js

15 ms

tumblelog_post_message_queue.js

tumblelog_post_message_queue.js

11 ms

stylesheet.css

stylesheet.css

10 ms

addthis_widget.js

addthis_widget.js

40 ms

show_ads.js

show_ads.js

12 ms

index.js

index.js

88 ms

ga.js

ga.js

59 ms

all.js

all.js

98 ms

tumblr_lzdchs86Jh1qb49cxo1_500.jpg

tumblr_lzdchs86Jh1qb49cxo1_500.jpg

538 ms

tumblr_m1yxhrT43K1qb49cxo1_1280.jpg

tumblr_m1yxhrT43K1qb49cxo1_1280.jpg

392 ms

tumblr_lru99yKJ9n1qb49cxo1_r1_250.jpg

tumblr_lru99yKJ9n1qb49cxo1_r1_250.jpg

56 ms

tumblr_lxg4401Cxu1qb49cxo1_500.jpg

tumblr_lxg4401Cxu1qb49cxo1_500.jpg

594 ms

tumblr_lo82n9guNR1qb49cxo1_500.jpg

tumblr_lo82n9guNR1qb49cxo1_500.jpg

635 ms

tumblr_lmzzowwn7R1qb49cxo1_400.jpg

tumblr_lmzzowwn7R1qb49cxo1_400.jpg

654 ms

tumblr_lzd3dpoweh1qb49cxo1_500.jpg

tumblr_lzd3dpoweh1qb49cxo1_500.jpg

265 ms

tumblr_lp1y03hsI81qb49cxo1_1280.jpg

tumblr_lp1y03hsI81qb49cxo1_1280.jpg

57 ms

tumblr_lo2v79YZJ51qb49cxo1_r2_1280.jpg

tumblr_lo2v79YZJ51qb49cxo1_r2_1280.jpg

56 ms

get_num_replies.js

get_num_replies.js

159 ms

__utm.gif

__utm.gif

30 ms

268 ms

xd_arbiter.php

xd_arbiter.php

145 ms

xd_arbiter.php

xd_arbiter.php

319 ms

ca-pub-4253163553461907.js

ca-pub-4253163553461907.js

283 ms

zrt_lookup.html

zrt_lookup.html

267 ms

show_ads_impl.js

show_ads_impl.js

103 ms

ads

ads

305 ms

osd.js

osd.js

112 ms

ads

ads

275 ms

ads

ads

209 ms

ads

ads

177 ms

ads

ads

147 ms

ads

ads

63 ms

ads

ads

31 ms

abg.js

abg.js

57 ms

ads

ads

27 ms

impixu

impixu

235 ms

search.jpg

search.jpg

134 ms

300lo.json

300lo.json

256 ms

analytics.html

analytics.html

150 ms

impixu

impixu

64 ms

login_check.html

login_check.html

56 ms

sh.8e5f85691f9aaa082472a194.html

sh.8e5f85691f9aaa082472a194.html

53 ms

avatar_d48edc79dbff_40.png

avatar_d48edc79dbff_40.png

56 ms

iframe_logo.png

iframe_logo.png

16 ms

rapid-3.36.js

rapid-3.36.js

55 ms

rapidworker-1.2.js

rapidworker-1.2.js

52 ms

ga.js

ga.js

97 ms

analytics.js

analytics.js

83 ms

cs.js

cs.js

132 ms

__utm.gif

__utm.gif

19 ms

cedexis.radar.js

cedexis.radar.js

5 ms

Accessibility Review

santorum-2012.com accessibility score

61

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

Links do not have a discernible name

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

santorum-2012.com best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

santorum-2012.com SEO score

87

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

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 Santorum-2012.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 Santorum-2012.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

santorum-2012.com

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