Tools & Wizards About Us
timeline2012.net screenshot

Report Summary

  • 39

    Performance

    Renders faster than
    59% of other websites

  • 75

    Accessibility

    Visual factors better than
    that of 42% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

timeline2012.net

Time Line 2012

Page Load Speed

6.9 sec in total

First Response

530 ms

Resources Loaded

6.1 sec

Page Rendered

242 ms

timeline2012.net screenshot

About Website

Visit timeline2012.net now to see the best up-to-date Time Line 2012 content and also check out these interesting facts you probably never knew about timeline2012.net

MISSION: To present truthful and scientific information to support conclusions regarding the coming geological, cosmic, and social economic changes, as well as solutions on how to thrive through these...

Visit timeline2012.net

Key Findings

We analyzed Timeline2012.net page load time and found that the first response time was 530 ms and then it took 6.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

timeline2012.net performance score

39

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.2 s

1/100

10%

LCP (Largest Contentful Paint)

Value14.6 s

0/100

25%

SI (Speed Index)

Value10.5 s

7/100

10%

TBT (Total Blocking Time)

Value370 ms

71/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value12.5 s

14/100

10%

Network Requests Diagram

timeline2012.net

530 ms

jquery.min.js

27 ms

calendar.css

21 ms

front.css

16 ms

mod_jflanguageselection.css

17 ms

Our browser made a total of 86 requests to load all elements on the main page. We found that 36% of them (31 requests) were addressed to the original Timeline2012.net, 21% (18 requests) were made to Timelinetothefuture.com and 6% (5 requests) were made to Asset.zcache.com. The less responsive or slowest element that took the longest time to load (4.6 sec) relates to the external source Alternate-ad-url.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 570.8 kB (24%)

Content Size

2.3 MB

After Optimization

1.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Timeline2012.net main page is 2.3 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. 40% of websites need less resources to load. Images take 1.8 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 41.5 kB

  • Original 53.5 kB
  • After minification 49.3 kB
  • After compression 12.0 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 41.5 kB or 78% of the original size.

Image Optimization

-15%

Potential reduce by 268.3 kB

  • Original 1.8 MB
  • After minification 1.6 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. Obviously, Time Line 2012 needs image optimization as it can save up to 268.3 kB or 15% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-57%

Potential reduce by 241.6 kB

  • Original 422.1 kB
  • After minification 419.8 kB
  • After compression 180.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 241.6 kB or 57% of the original size.

CSS Optimization

-79%

Potential reduce by 19.5 kB

  • Original 24.7 kB
  • After minification 17.8 kB
  • After compression 5.3 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. Timeline2012.net needs all CSS files to be minified and compressed as it can save up to 19.5 kB or 79% of the original size.

Requests Breakdown

Number of requests can be reduced by 34 (40%)

Requests Now

84

After Optimization

50

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 84 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Time Line 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 14 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

timeline2012.net

timeline2012.net

530 ms

jquery.min.js

jquery.min.js

27 ms

calendar.css

calendar.css

21 ms

front.css

front.css

16 ms

mod_jflanguageselection.css

mod_jflanguageselection.css

17 ms

mootools.js

mootools.js

40 ms

script.js

script.js

33 ms

light.css

light.css

34 ms

ie_suckerfish.js

ie_suckerfish.js

34 ms

styles.ie.css

styles.ie.css

34 ms

styles.ie7.css

styles.ie7.css

38 ms

mootools-fpss-comp.js

mootools-fpss-comp.js

154 ms

show_ads.js

show_ads.js

13 ms

1.js

1.js

303 ms

marquee-founder.gif

marquee-founder.gif

95 ms

template_css.php

template_css.php

110 ms

grand_canyon.jpg

grand_canyon.jpg

161 ms

ian_lungold.jpg

ian_lungold.jpg

142 ms

underground_shelter.jpg

underground_shelter.jpg

146 ms

police_state.jpg

police_state.jpg

151 ms

safe_location.jpg

safe_location.jpg

158 ms

future_map.jpg

future_map.jpg

213 ms

universe1.jpg

universe1.jpg

215 ms

grand_canyon.jpg

grand_canyon.jpg

161 ms

ian_lungold.jpg

ian_lungold.jpg

213 ms

underground_shelter.jpg

underground_shelter.jpg

213 ms

police_state.jpg

police_state.jpg

213 ms

safe_location.jpg

safe_location.jpg

214 ms

future_map.jpg

future_map.jpg

215 ms

universe1.jpg

universe1.jpg

215 ms

cosmic_bg.jpg

cosmic_bg.jpg

12 ms

timeline2012header.jpg

timeline2012header.jpg

80 ms

menu.jpg

menu.jpg

18 ms

en.gif

en.gif

19 ms

es.gif

es.gif

21 ms

fr.gif

fr.gif

22 ms

de.gif

de.gif

23 ms

nl.gif

nl.gif

44 ms

vn.gif

vn.gif

44 ms

facebook-button.png

facebook-button.png

42 ms

paypal_donate.gif

paypal_donate.gif

45 ms

button.mozilla-firefox-sml.png

button.mozilla-firefox-sml.png

45 ms

button.internet-explorer-sml.png

button.internet-explorer-sml.png

57 ms

button.google-chrome-sml.png

button.google-chrome-sml.png

57 ms

button.safari-sml.png

button.safari-sml.png

59 ms

button.adobe-flash-player-sml.png

button.adobe-flash-player-sml.png

58 ms

button.windows-media-player-sml.png

button.windows-media-player-sml.png

78 ms

button.apple-quicktime-sml.png

button.apple-quicktime-sml.png

79 ms

button.adobe-acrobat-reader-sml.png

button.adobe-acrobat-reader-sml.png

81 ms

green_arrow.gif

green_arrow.gif

12 ms

zrt_lookup.html

zrt_lookup.html

31 ms

show_ads_impl.js

show_ads_impl.js

40 ms

loading_black.gif

loading_black.gif

90 ms

nav.gif

nav.gif

92 ms

zpanel

zpanel

453 ms

ads

ads

176 ms

osd.js

osd.js

19 ms

alternate

alternate

4574 ms

s.gif

s.gif

49 ms

r-0e60733aad0f032ea9ea1d68c888bb26.css

r-0e60733aad0f032ea9ea1d68c888bb26.css

81 ms

2012_neck_tie_2_customize_it-r30b5c383fc9b4eb39ebc5618d5b1d630_z5ndj_125.jpg

2012_neck_tie_2_customize_it-r30b5c383fc9b4eb39ebc5618d5b1d630_z5ndj_125.jpg

72 ms

c.php

c.php

107 ms

menu0.png

menu0.png

38 ms

2012_womens_shirts_3_customize_it-rea04b4f136e24b59a22687a9974ba011_k2gl9_125.jpg

2012_womens_shirts_3_customize_it-rea04b4f136e24b59a22687a9974ba011_k2gl9_125.jpg

68 ms

2012_get_ready_t_shirts_2-rd0614cefbdde4a448ea9c5744166e4c3_k2glg_125.jpg

2012_get_ready_t_shirts_2-rd0614cefbdde4a448ea9c5744166e4c3_k2glg_125.jpg

70 ms

r.php

r.php

209 ms

logo_v2.png

logo_v2.png

33 ms

ga.js

ga.js

7 ms

footerBgTile.gif

footerBgTile.gif

31 ms

footerLeft.gif

footerLeft.gif

31 ms

footerRight.gif

footerRight.gif

29 ms

f.php

f.php

339 ms

0.jpg

0.jpg

203 ms

t.php

t.php

104 ms

c.php

c.php

114 ms

px.js

px.js

41 ms

px.js

px.js

79 ms

min.js

min.js

127 ms

bg.gif

bg.gif

63 ms

logo.png

logo.png

140 ms

browserfp.min.js

browserfp.min.js

245 ms

lhs.gif

lhs.gif

136 ms

rhs.gif

rhs.gif

136 ms

h_bg.gif

h_bg.gif

56 ms

srch-bg.gif

srch-bg.gif

57 ms

bg.gif

bg.gif

9 ms

Accessibility Review

timeline2012.net accessibility score

75

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[role]s are not contained by their required parent element

High

[aria-*] attributes do not have valid values

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

timeline2012.net 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

timeline2012.net SEO score

75

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

    EN

  • Encoding

    UTF-8

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

timeline2012.net

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