Tools & Wizards About Us
p2012.org screenshot

Report Summary

  • 78

    Performance

    Renders faster than
    85% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 83% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 96

    SEO

    Google-friendlier than
    90% of websites

p2012.org

P2012 Race for the White House - The 2012 Presidential Campaign by Democracy in Action

Page Load Speed

1.6 sec in total

First Response

111 ms

Resources Loaded

1.3 sec

Page Rendered

186 ms

p2012.org screenshot

About Website

Welcome to p2012.org homepage info - get ready to check P2012 best content for United States right away, or after learning these important things about p2012.org

Democracy in Action P2012: A framework for understanding and following the 2012 presidential campaign.

Visit p2012.org

Key Findings

We analyzed P2012.org page load time and found that the first response time was 111 ms and then it took 1.5 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

p2012.org performance score

78

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.5 s

95/100

10%

LCP (Largest Contentful Paint)

Value2.5 s

89/100

25%

SI (Speed Index)

Value2.8 s

96/100

10%

TBT (Total Blocking Time)

Value570 ms

52/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value6.6 s

58/100

10%

Network Requests Diagram

p2012.org

111 ms

p2016.org

230 ms

chrnstyles.css

44 ms

adsbygoogle.js

385 ms

404.html

81 ms

Our browser made a total of 27 requests to load all elements on the main page. We found that 7% of them (2 requests) were addressed to the original P2012.org, 74% (20 requests) were made to P2016.org and 7% (2 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (486 ms) relates to the external source Pagead2.googlesyndication.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 14.3 kB (4%)

Content Size

404.5 kB

After Optimization

390.2 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of P2012.org main page is 404.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. 20% of websites need less resources to load. Javascripts take 261.6 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 13.9 kB

  • Original 18.6 kB
  • After minification 15.7 kB
  • After compression 4.7 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 2.9 kB, which is 16% 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 13.9 kB or 75% of the original size.

Image Optimization

-0%

Potential reduce by 315 B

  • Original 124.3 kB
  • After minification 124.0 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. P2012 images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 117 B

  • Original 261.6 kB
  • After minification 261.6 kB
  • After compression 261.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. This website has mostly compressed JavaScripts.

Requests Breakdown

Number of requests can be reduced by 3 (14%)

Requests Now

21

After Optimization

18

  • AJAX
  • Images
  • JavaScript

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

Network Requests Diagram

p2012.org

p2012.org

111 ms

p2016.org

p2016.org

230 ms

chrnstyles.css

chrnstyles.css

44 ms

adsbygoogle.js

adsbygoogle.js

385 ms

404.html

404.html

81 ms

404.html

404.html

136 ms

analytics.js

analytics.js

30 ms

08lightyp2q.gif

08lightyp2q.gif

259 ms

p2016j.jpg

p2016j.jpg

79 ms

chipin75.png

chipin75.png

106 ms

candidatesg.png

candidatesg.png

192 ms

map8.gif

map8.gif

191 ms

calendar.jpg

calendar.jpg

191 ms

partylogos200.gif

partylogos200.gif

190 ms

media702bb.jpg

media702bb.jpg

191 ms

dog200f.jpg

dog200f.jpg

190 ms

interestg200.jpg

interestg200.jpg

256 ms

electorate200g.jpg

electorate200g.jpg

255 ms

commsbutton.jpg

commsbutton.jpg

255 ms

chrngraphic.png

chrngraphic.png

254 ms

twitter43.png

twitter43.png

256 ms

collect

collect

13 ms

js

js

134 ms

show_ads_impl.js

show_ads_impl.js

486 ms

printex.css

printex.css

44 ms

404.html

404.html

35 ms

404.html

404.html

40 ms

Accessibility Review

p2012.org accessibility score

94

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

Links do not have a discernible name

Best Practices

p2012.org 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

Serves images with low resolution

General

Impact

Issue

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

p2012.org SEO score

96

Search Engine Optimization Advices

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 P2012.org 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 P2012.org 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

p2012.org

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