Tools & Wizards About Us
coreplanner.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

coreplanner.com

CorePlanner | Standards | Lesson Planning Software

Page Load Speed

1.5 sec in total

First Response

200 ms

Resources Loaded

1.2 sec

Page Rendered

142 ms

coreplanner.com screenshot

About Website

Click here to check amazing Core Planner content. Otherwise, check out these important facts you probably never knew about coreplanner.com

CorePlanner is a web based lesson planning application that helps teachers and administrators easily integrate and track the usage of Standards within your lesson plans. Get Started.

Visit coreplanner.com

Key Findings

We analyzed Coreplanner.com page load time and found that the first response time was 200 ms and then it took 1.3 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

coreplanner.com performance score

0

Network Requests Diagram

coreplanner.com

200 ms

coreplanner.com

294 ms

reset-min.css

63 ms

coreplanner.css

179 ms

tipTip.css

170 ms

Our browser made a total of 30 requests to load all elements on the main page. We found that 73% of them (22 requests) were addressed to the original Coreplanner.com, 13% (4 requests) were made to S7.addthis.com and 7% (2 requests) were made to Ssl.google-analytics.com. The less responsive or slowest element that took the longest time to load (449 ms) belongs to the original domain Coreplanner.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.2 MB (68%)

Content Size

1.8 MB

After Optimization

576.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Coreplanner.com main page is 1.8 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. 45% of websites need less resources to load. Javascripts take 1.5 MB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 91.0 kB

  • Original 117.9 kB
  • After minification 117.0 kB
  • After compression 26.9 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 91.0 kB or 77% of the original size.

Image Optimization

-5%

Potential reduce by 7.6 kB

  • Original 165.8 kB
  • After minification 158.2 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. Core Planner images are well optimized though.

JavaScript Optimization

-74%

Potential reduce by 1.1 MB

  • Original 1.5 MB
  • After minification 1.5 MB
  • After compression 384.3 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 1.1 MB or 74% of the original size.

CSS Optimization

-81%

Potential reduce by 31.3 kB

  • Original 38.6 kB
  • After minification 28.9 kB
  • After compression 7.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. Coreplanner.com needs all CSS files to be minified and compressed as it can save up to 31.3 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 19 (68%)

Requests Now

28

After Optimization

9

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

coreplanner.com

coreplanner.com

200 ms

coreplanner.com

coreplanner.com

294 ms

reset-min.css

reset-min.css

63 ms

coreplanner.css

coreplanner.css

179 ms

tipTip.css

tipTip.css

170 ms

jquery.fancybox.css

jquery.fancybox.css

177 ms

jquery-1.4.2.min.js

jquery-1.4.2.min.js

289 ms

cufon-yui.js

cufon-yui.js

229 ms

Museo_Sans_500_400-Museo_Sans_500_italic_400.font.js

Museo_Sans_500_400-Museo_Sans_500_italic_400.font.js

401 ms

Museo_Sans_700_600.font.js

Museo_Sans_700_600.font.js

389 ms

Museo_Sans_900_700.font.js

Museo_Sans_900_700.font.js

449 ms

jquery.tipTip.minified.js

jquery.tipTip.minified.js

236 ms

browser-check.js

browser-check.js

306 ms

jquery.fancybox.pack.js

jquery.fancybox.pack.js

307 ms

jquery.zclip.min.js

jquery.zclip.min.js

346 ms

scripts.js

scripts.js

346 ms

addthis_widget.js

addthis_widget.js

36 ms

ga.js

ga.js

70 ms

background.gif

background.gif

109 ms

coreplanner-logo.gif

coreplanner-logo.gif

109 ms

cp-logo.gif

cp-logo.gif

107 ms

core-standards-planning.png

core-standards-planning.png

139 ms

8hugsdotcom.jpg

8hugsdotcom.jpg

107 ms

_ate.track.config_resp

_ate.track.config_resp

38 ms

300lo.json

300lo.json

129 ms

__utm.gif

__utm.gif

12 ms

sh.48536d49e4da3bdba54606b4.html

sh.48536d49e4da3bdba54606b4.html

25 ms

layers.0ee9c4d64cf5ebc35dab.js

layers.0ee9c4d64cf5ebc35dab.js

16 ms

counter.e61152ce165bc90fac45.js

counter.e61152ce165bc90fac45.js

89 ms

print.css

print.css

79 ms

SEO Factors

coreplanner.com SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

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

coreplanner.com

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