2.7 sec in total
35 ms
2.4 sec
314 ms
Click here to check amazing Global Citizen Year Fundly content for Pakistan. Otherwise, check out these important facts you probably never knew about globalcitizenyear.fundly.com
Visit globalcitizenyear.fundly.comWe analyzed Globalcitizenyear.fundly.com page load time and found that the first response time was 35 ms and then it took 2.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
globalcitizenyear.fundly.com performance score
name
value
score
weighting
Value3.2 s
43/100
10%
Value7.4 s
4/100
25%
Value4.5 s
73/100
10%
Value330 ms
76/100
30%
Value0.001
100/100
15%
Value11.6 s
18/100
10%
35 ms
450 ms
302 ms
127 ms
79 ms
Our browser made a total of 96 requests to load all elements on the main page. We found that 8% of them (8 requests) were addressed to the original Globalcitizenyear.fundly.com, 8% (8 requests) were made to Doapv6pcsx1wa.cloudfront.net and 7% (7 requests) were made to Facebook.com. The less responsive or slowest element that took the longest time to load (658 ms) relates to the external source Use.typekit.net.
Page size can be reduced by 2.4 MB (52%)
4.7 MB
2.3 MB
In fact, the total size of Globalcitizenyear.fundly.com main page is 4.7 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. 65% of websites need less resources to load. CSS take 2.3 MB which makes up the majority of the site volume.
Potential reduce by 118.3 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 118.3 kB or 80% of the original size.
Potential reduce by 18.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. Global Citizen Year Fundly images are well optimized though.
Potential reduce by 396.1 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 396.1 kB or 63% of the original size.
Potential reduce by 1.9 MB
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. Globalcitizenyear.fundly.com needs all CSS files to be minified and compressed as it can save up to 1.9 MB or 80% of the original size.
Number of requests can be reduced by 56 (67%)
83
27
The browser has sent 83 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Global Citizen Year Fundly. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 36 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
globalcitizenyear.fundly.com
35 ms
globalcitizenyear.fundly.com
450 ms
3536001.js
302 ms
application-0dbfec75b6b6ae584ed5d042e377fcf5.css
127 ms
jquery.min.js
79 ms
modernizr-2.5.2-62246608536cb26ae9202f3aa79d6d83.js
81 ms
google_analytics-9df1a932a974dc6f18aa1f09d8d7f8a9.js
79 ms
metrics-c355c055982531a53a966c5162fc6b2b.js
82 ms
cause-d4319ce5522232955327e4b12db95267.css
85 ms
global
106 ms
cause_page-8570c65a8ce984ba785dd545e0262963.js
91 ms
base_js_all-85938a5d248a2fc88d6ce7eda33154d0.js
85 ms
gtm.js
130 ms
webfont.js
39 ms
left.png
111 ms
background_3a1ed2c9-5c0e-44aa-a9cf-2ac9a906fa5f.png
465 ms
right.png
120 ms
icon_search.png
120 ms
cc_placeholder_image.png
119 ms
background_7dad5de8-ffba-4217-9ca0-fa44dbe73250.png
435 ms
background_3e5ee207-9f84-407a-9e7b-a360f9bf5f59.png
455 ms
fundly_logo_knockout.png
96 ms
all.js
137 ms
fontawesome-webfont-c3505b2ba2be317c06bb81329741ee60.woff
60 ms
css
204 ms
rmi4ipp.js
658 ms
conversion_async.js
181 ms
roundtrip.js
153 ms
ed5810faa4f61a65dbc90a9829571f94_ar_h35.jpeg
317 ms
260 ms
xd_arbiter.php
258 ms
f46f04fdc528c735c0164fa512737f70_ar_h233.jpg
265 ms
d371b347831e3292e61632e673d53874_ar_h233.jpg
271 ms
mixpanel-2.2.min.js
295 ms
ga.js
230 ms
fbds.js
140 ms
OWCuIriso0IYBasiGT3pFw.js
218 ms
widgets.js
385 ms
in.js
186 ms
plusone.js
261 ms
PinExt.png
220 ms
pinit.js
218 ms
182 ms
rxxXUYj4oZ6Q5oDJFtEd6i3USBnSvpkopQaUR-2r7iU.ttf
115 ms
like.php
186 ms
like.php
190 ms
67 ms
xd_arbiter.php
72 ms
xd_arbiter.php
69 ms
PTFH5P6GWBCDRFRBOLVWV6.js
197 ms
feedback-tab.png
86 ms
secureAnonymousFramework
141 ms
__utm.gif
143 ms
__utm.gif
143 ms
294 ms
vpc6VNjRPXV.js
292 ms
LVx-xkvaJ0b.png
350 ms
293 ms
315 ms
cb=gapi.loaded_0
210 ms
cb=gapi.loaded_1
249 ms
fastbutton
304 ms
pinit_main.js
197 ms
tab-right-dark-da2413549ce324fc421ae86a0e5881ee.png
171 ms
tr
139 ms
button.831500944bc3eb7ea5276ccdc3f71d2e.js
158 ms
out
188 ms
out
188 ms
out
188 ms
out
185 ms
out
188 ms
out
215 ms
count.json
267 ms
82 ms
postmessageRelay
155 ms
cb=gapi.loaded_0
46 ms
cb=gapi.loaded_1
43 ms
tweet_button.6a78875565a912489e9aef879c881358.en.html
88 ms
u.php
84 ms
sync
112 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
54 ms
adsct
156 ms
ga-audiences
54 ms
pixel
109 ms
tap.php
42 ms
api.js
56 ms
core:rpc:shindig.random:shindig.sha1.js
54 ms
2536007149-postmessagerelay.js
44 ms
377928.gif
9 ms
in
4 ms
sd
27 ms
jot
89 ms
track.js
160 ms
nr-100.js
54 ms
2 ms
bc27c73051
113 ms
globalcitizenyear.fundly.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
Image elements do not have [alt] attributes
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
globalcitizenyear.fundly.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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
globalcitizenyear.fundly.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Globalcitizenyear.fundly.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 Globalcitizenyear.fundly.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.
globalcitizenyear.fundly.com
Open Graph description is not detected on the main page of Global Citizen Year Fundly. 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: