959 ms in total
86 ms
718 ms
155 ms
Welcome to greenp.com homepage info - get ready to check Greenp best content for Canada right away, or after learning these important things about greenp.com
Visit greenp.comWe analyzed Greenp.com page load time and found that the first response time was 86 ms and then it took 873 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.
greenp.com performance score
name
value
score
weighting
Value3.6 s
31/100
10%
Value5.2 s
23/100
25%
Value3.7 s
85/100
10%
Value410 ms
67/100
30%
Value0.073
95/100
15%
Value6.1 s
63/100
10%
86 ms
140 ms
66 ms
90 ms
110 ms
Our browser made a total of 54 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Greenp.com, 93% (50 requests) were made to Parking.greenp.com and 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (241 ms) relates to the external source Parking.greenp.com.
Page size can be reduced by 300.2 kB (41%)
729.2 kB
429.0 kB
In fact, the total size of Greenp.com main page is 729.2 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. 35% of websites need less resources to load. Images take 325.3 kB which makes up the majority of the site volume.
Potential reduce by 13.6 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 13.6 kB or 72% of the original size.
Potential reduce by 15.1 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. Greenp images are well optimized though.
Potential reduce by 195.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 195.5 kB or 66% of the original size.
Potential reduce by 75.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. Greenp.com needs all CSS files to be minified and compressed as it can save up to 75.9 kB or 86% of the original size.
Number of requests can be reduced by 8 (16%)
50
42
The browser has sent 50 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Greenp. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and as a result speed up the page load time.
greenp.com
86 ms
parking.greenp.com
140 ms
screen.css
66 ms
mootools.js
90 ms
mootools-more.js
110 ms
content-slider.js
76 ms
toggler.js
76 ms
init.js
77 ms
parking-finder-form.js
108 ms
carousel.js
121 ms
analytics.js
22 ms
bg-body.jpg
35 ms
logo-decorate.jpg
33 ms
Icon-TM-with-no-border-LG.png
36 ms
bg-ghi2.jpg
32 ms
bg-ghi-div.jpg
33 ms
logo-header.jpg
61 ms
navigationGlobal.jpg
56 ms
bg-drop-nav-top.png
57 ms
bg-drop-nav.png
61 ms
bg-drop-nav-mid.png
62 ms
bg-drop-nav-bottom.png
64 ms
bg-banner-home.jpg
81 ms
bg-form.png
134 ms
title-find-parking-by.png
89 ms
search-options.gif
90 ms
bg-form-input.jpg
91 ms
but-go.gif
94 ms
carousel_00000042_banner.jpg
185 ms
bg-quick-bar.jpg
117 ms
bg-quick-icons-03.jpg
119 ms
bg-quick-icons.jpg
120 ms
bg-quick-icons-02.jpg
123 ms
bg-gate-events-top.jpg
147 ms
but-see-all-events.gif
149 ms
bg-gateway-events.jpg
150 ms
event_00015871_thumb.jpg
153 ms
event_00016135_thumb.png
160 ms
event_00014195_thumb.jpg
175 ms
event_00015936_thumb.png
176 ms
bg-about-gp-tile.jpg
177 ms
bg-comms-tile.jpg
186 ms
annual-report-cover.gif
185 ms
ar_00000063_thumb.png
203 ms
ico-pdf.png
208 ms
bg-tile-right.jpg
208 ms
but-see-all.gif
209 ms
collect
11 ms
bg-tile-bikeshare.png
185 ms
logo-footer.jpg
189 ms
qlassik_tb-webfont.woff
230 ms
qlassikbold_tb-webfont.woff
241 ms
print.css
32 ms
chartbeat.js
24 ms
greenp.com accessibility score
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
ARIA input fields do not have accessible names
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Some elements have a [tabindex] value greater than 0
greenp.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
greenp.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Page is blocked from indexing
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
Document uses legible font sizes
Tap targets are not sized appropriately
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Greenp.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Greenp.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.
greenp.com
Open Graph description is not detected on the main page of Greenp. 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: