4.9 sec in total
239 ms
2.9 sec
1.8 sec
Visit projectsmile.org now to see the best up-to-date Project Smile content for United States and also check out these interesting facts you probably never knew about projectsmile.org
Project Smile is dedicated to helping people in need through our Suits & Smiles & Smiles for Children programs. Donate stuffed animals and gently used suits today!
Visit projectsmile.orgWe analyzed Projectsmile.org page load time and found that the first response time was 239 ms and then it took 4.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
projectsmile.org performance score
name
value
score
weighting
Value1.5 s
96/100
10%
Value3.7 s
58/100
25%
Value3.7 s
85/100
10%
Value1,340 ms
17/100
30%
Value0.033
100/100
15%
Value12.6 s
14/100
10%
239 ms
489 ms
481 ms
779 ms
532 ms
Our browser made a total of 27 requests to load all elements on the main page. We found that 4% of them (1 request) were addressed to the original Projectsmile.org, 22% (6 requests) were made to Youtube.com and 15% (4 requests) were made to Lirp.cdn-website.com. The less responsive or slowest element that took the longest time to load (779 ms) relates to the external source Youtube.com.
Page size can be reduced by 463.6 kB (76%)
606.9 kB
143.4 kB
In fact, the total size of Projectsmile.org main page is 606.9 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. CSS take 368.5 kB which makes up the majority of the site volume.
Potential reduce by 127.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 127.9 kB or 76% of the original size.
Potential reduce by 24.2 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 24.2 kB or 35% of the original size.
Potential reduce by 311.4 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. Projectsmile.org needs all CSS files to be minified and compressed as it can save up to 311.4 kB or 85% of the original size.
Number of requests can be reduced by 6 (50%)
12
6
The browser has sent 12 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Project Smile. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 7 to 1 for JavaScripts and as a result speed up the page load time.
www.projectsmile.org
239 ms
project-smile-logo-1920w.jpg
489 ms
vector_path_white.svg
481 ms
xIf7NXZbzeA
779 ms
transparent_background.png
532 ms
jquery-3.6.0.min.js
413 ms
d-js-one-runtime-unified-desktop.min.js
413 ms
d-js-jquery-migrate.min.js
414 ms
project-smile-logo-160w.jpg
331 ms
before-after-header2-1920w.jpg
332 ms
project-smile-logo-99w.jpg
332 ms
fontawesome-webfont.woff
151 ms
sp-2.0.0-dm-0.1.min.js
83 ms
i
29 ms
www-player.css
42 ms
www-embed-player.js
193 ms
base.js
247 ms
fetch-polyfill.js
185 ms
fontawesome-webfont.ttf
28 ms
ad_status.js
683 ms
fontawesome-webfont.svg
452 ms
WmYtwbYsvJeTDmsuIOmqRAOrqYQ4FznKv6GQB7SOtoo.js
368 ms
embed.js
108 ms
id
71 ms
KFOmCnqEu92Fr1Mu4mxM.woff
329 ms
KFOlCnqEu92Fr1MmEU9fBBc-.woff
331 ms
Create
256 ms
projectsmile.org accessibility score
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
projectsmile.org best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
projectsmile.org 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
Image elements do not have [alt] attributes
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 Projectsmile.org 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 Projectsmile.org 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.
projectsmile.org
Open Graph data is detected on the main page of Project Smile. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: