Tools & Wizards About Us
plannersource.com screenshot

Report Summary

  • 78

    Performance

    Renders faster than
    85% 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

  • 97

    SEO

    Google-friendlier than
    91% of websites

plannersource.com

PlannerSource, Inc. - Site Selection for Meetings and Conferences

Page Load Speed

1.4 sec in total

First Response

528 ms

Resources Loaded

723 ms

Page Rendered

169 ms

plannersource.com screenshot

About Website

Welcome to plannersource.com homepage info - get ready to check Planner Source best content right away, or after learning these important things about plannersource.com

PlannerSource is a full service meeting consultancy founded to saving planners time, effort, and money.

Visit plannersource.com

Key Findings

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

Performance Metrics

plannersource.com performance score

78

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

61/100

10%

LCP (Largest Contentful Paint)

Value3.9 s

52/100

25%

SI (Speed Index)

Value3.0 s

93/100

10%

TBT (Total Blocking Time)

Value170 ms

93/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value5.7 s

68/100

10%

Network Requests Diagram

plannersource.com

528 ms

ui.css

50 ms

base.css

39 ms

grid.css

38 ms

mediaq.css

37 ms

Our browser made a total of 21 requests to load all elements on the main page. We found that 86% of them (18 requests) were addressed to the original Plannersource.com, 5% (1 request) were made to Fonts.googleapis.com and 5% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (528 ms) belongs to the original domain Plannersource.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 153.3 kB (49%)

Content Size

313.6 kB

After Optimization

160.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Plannersource.com main page is 313.6 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. 25% of websites need less resources to load. Javascripts take 164.7 kB which makes up the majority of the site volume.

HTML Optimization

-71%

Potential reduce by 8.5 kB

  • Original 12.0 kB
  • After minification 11.4 kB
  • After compression 3.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 8.5 kB or 71% of the original size.

Image Optimization

-6%

Potential reduce by 3.6 kB

  • Original 61.5 kB
  • After minification 57.8 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. Planner Source images are well optimized though.

JavaScript Optimization

-47%

Potential reduce by 77.7 kB

  • Original 164.7 kB
  • After minification 159.2 kB
  • After compression 87.0 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 77.7 kB or 47% of the original size.

CSS Optimization

-84%

Potential reduce by 63.4 kB

  • Original 75.4 kB
  • After minification 56.1 kB
  • After compression 11.9 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. Plannersource.com needs all CSS files to be minified and compressed as it can save up to 63.4 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 11 (55%)

Requests Now

20

After Optimization

9

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

plannersource.com

plannersource.com

528 ms

ui.css

ui.css

50 ms

base.css

base.css

39 ms

grid.css

grid.css

38 ms

mediaq.css

mediaq.css

37 ms

custom.css

custom.css

51 ms

superfish.css

superfish.css

37 ms

css

css

21 ms

jquery.min.js

jquery.min.js

8 ms

jquery-ui-1.10.3.custom.min.js

jquery-ui-1.10.3.custom.min.js

85 ms

jquery.cycle2.min.js

jquery.cycle2.min.js

69 ms

hoverIntent.js

hoverIntent.js

61 ms

superfish.js

superfish.js

62 ms

analytics.js

analytics.js

81 ms

logo.png

logo.png

26 ms

icon_ps_rfp.png

icon_ps_rfp.png

25 ms

icon_ps_site.png

icon_ps_site.png

27 ms

icon_ps_neg.png

icon_ps_neg.png

26 ms

icon_ps_contract.png

icon_ps_contract.png

25 ms

shade.jpg

shade.jpg

24 ms

shifter_04.jpg

shifter_04.jpg

36 ms

Accessibility Review

plannersource.com accessibility score

61

Accessibility Issues

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

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

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

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

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

High

Page has valid source maps

SEO Factors

plannersource.com SEO score

97

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

plannersource.com

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