Tools & Wizards About Us
perhapstomorrow.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

perhapstomorrow.com

Perhaps Tomorrow: A Journey of Love & Discovery | perhapstomorrow.com

Page Load Speed

2.8 sec in total

First Response

546 ms

Resources Loaded

2.1 sec

Page Rendered

194 ms

perhapstomorrow.com screenshot

About Website

Welcome to perhapstomorrow.com homepage info - get ready to check Perhaps Tomorrow best content right away, or after learning these important things about perhapstomorrow.com

Visit perhapstomorrow.com

Key Findings

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

Performance Metrics

perhapstomorrow.com performance score

0

Network Requests Diagram

perhapstomorrow.com

546 ms

system.base.css

382 ms

system.menus.css

119 ms

system.messages.css

118 ms

system.theme.css

377 ms

Our browser made a total of 67 requests to load all elements on the main page. We found that 94% of them (63 requests) were addressed to the original Perhapstomorrow.com, 3% (2 requests) were made to Assets.pinterest.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (821 ms) belongs to the original domain Perhapstomorrow.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 252.6 kB (50%)

Content Size

509.5 kB

After Optimization

256.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Perhapstomorrow.com main page is 509.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 242.2 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 16.8 kB

  • Original 21.3 kB
  • After minification 21.0 kB
  • After compression 4.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 16.8 kB or 79% of the original size.

Image Optimization

-2%

Potential reduce by 3.2 kB

  • Original 152.7 kB
  • After minification 149.5 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. Perhaps Tomorrow images are well optimized though.

JavaScript Optimization

-65%

Potential reduce by 158.7 kB

  • Original 242.2 kB
  • After minification 215.1 kB
  • After compression 83.6 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 158.7 kB or 65% of the original size.

CSS Optimization

-79%

Potential reduce by 74.1 kB

  • Original 93.3 kB
  • After minification 71.4 kB
  • After compression 19.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. Perhapstomorrow.com needs all CSS files to be minified and compressed as it can save up to 74.1 kB or 79% of the original size.

Requests Breakdown

Number of requests can be reduced by 59 (89%)

Requests Now

66

After Optimization

7

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

perhapstomorrow.com

perhapstomorrow.com

546 ms

system.base.css

system.base.css

382 ms

system.menus.css

system.menus.css

119 ms

system.messages.css

system.messages.css

118 ms

system.theme.css

system.theme.css

377 ms

comment.css

comment.css

150 ms

field.css

field.css

174 ms

logintoboggan.css

logintoboggan.css

191 ms

node.css

node.css

205 ms

search.css

search.css

227 ms

user.css

user.css

245 ms

views.css

views.css

254 ms

chosen.css

chosen.css

336 ms

ckeditor.css

ckeditor.css

258 ms

colorbox_default_style.css

colorbox_default_style.css

271 ms

ctools.css

ctools.css

315 ms

superfish.css

superfish.css

327 ms

superfish-vertical.css

superfish-vertical.css

365 ms

superfish-navbar.css

superfish-navbar.css

374 ms

alpha-reset.css

alpha-reset.css

385 ms

alpha-mobile.css

alpha-mobile.css

386 ms

alpha-alpha.css

alpha-alpha.css

387 ms

formalize.css

formalize.css

416 ms

omega-text.css

omega-text.css

422 ms

omega-branding.css

omega-branding.css

429 ms

omega-menu.css

omega-menu.css

429 ms

omega-forms.css

omega-forms.css

693 ms

omega-visuals.css

omega-visuals.css

464 ms

navin-base.css

navin-base.css

474 ms

navin-font.css

navin-font.css

476 ms

navin-form.css

navin-form.css

525 ms

navin-branding.css

navin-branding.css

509 ms

navin-menu.css

navin-menu.css

519 ms

navin-header.css

navin-header.css

523 ms

navin-preface.css

navin-preface.css

555 ms

navin-content.css

navin-content.css

570 ms

pinit.js

pinit.js

7 ms

navin-postfix.css

navin-postfix.css

529 ms

navin-footer.css

navin-footer.css

505 ms

navin-alpha-default-normal.css

navin-alpha-default-normal.css

528 ms

alpha-default-normal-24.css

alpha-default-normal-24.css

520 ms

jquery.js

jquery.js

704 ms

jquery.once.js

jquery.once.js

498 ms

drupal.js

drupal.js

546 ms

chosen.jquery.min.js

chosen.jquery.min.js

543 ms

chosen.js

chosen.js

744 ms

jquery.colorbox-min.js

jquery.colorbox-min.js

821 ms

colorbox.js

colorbox.js

503 ms

colorbox_default_style.js

colorbox_default_style.js

507 ms

jquery.hoverIntent.minified.js

jquery.hoverIntent.minified.js

490 ms

jquery.bgiframe.min.js

jquery.bgiframe.min.js

498 ms

superfish.js

superfish.js

521 ms

supersubs.js

supersubs.js

536 ms

supposition.js

supposition.js

545 ms

sftouchscreen.js

sftouchscreen.js

535 ms

googleanalytics.js

googleanalytics.js

550 ms

global.js

global.js

547 ms

jquery.formalize.js

jquery.formalize.js

560 ms

omega-mediaqueries.js

omega-mediaqueries.js

582 ms

omega-equalheights.js

omega-equalheights.js

561 ms

ga.js

ga.js

74 ms

perhaps-tomorrow.png

perhaps-tomorrow.png

194 ms

perhaps-tomorrow-cover.jpg

perhaps-tomorrow-cover.jpg

287 ms

loading_animation.gif

loading_animation.gif

49 ms

controls.png

controls.png

50 ms

__utm.gif

__utm.gif

14 ms

pinit_main.js

pinit_main.js

425 ms

SEO Factors

perhapstomorrow.com SEO score

0

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 Perhapstomorrow.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 Perhapstomorrow.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

perhapstomorrow.com

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