3.8 sec in total
166 ms
3 sec
631 ms
Click here to check amazing ProjectW content. Otherwise, check out these important facts you probably never knew about projectw.org
The Free Speech Forum - ProjectW - The Only Place
Visit projectw.orgWe analyzed Projectw.org page load time and found that the first response time was 166 ms and then it took 3.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
projectw.org performance score
name
value
score
weighting
Value3.1 s
47/100
10%
Value11.8 s
0/100
25%
Value9.5 s
11/100
10%
Value5,730 ms
0/100
30%
Value0.9
3/100
15%
Value20.5 s
2/100
10%
166 ms
49 ms
82 ms
75 ms
29 ms
Our browser made a total of 82 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Projectw.org, 71% (58 requests) were made to Barelylegal.com and 7% (6 requests) were made to Ecsm.vs3.com. The less responsive or slowest element that took the longest time to load (1.4 sec) relates to the external source Secure.vs3.com.
Page size can be reduced by 510.4 kB (40%)
1.3 MB
768.9 kB
In fact, the total size of Projectw.org main page is 1.3 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. 60% of websites need less resources to load. Images take 676.7 kB which makes up the majority of the site volume.
Potential reduce by 158.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. This page needs HTML code to be minified as it can gain 23.7 kB, which is 12% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 158.6 kB or 83% of the original size.
Potential reduce by 47.0 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. ProjectW images are well optimized though.
Potential reduce by 170.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 170.1 kB or 67% of the original size.
Potential reduce by 134.8 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. Projectw.org needs all CSS files to be minified and compressed as it can save up to 134.8 kB or 86% of the original size.
Number of requests can be reduced by 26 (33%)
78
52
The browser has sent 78 CSS, Javascripts, AJAX and image requests in order to completely render the main page of ProjectW. 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 6 to 1 for CSS and as a result speed up the page load time.
projectw.org
166 ms
landing
49 ms
www.barelylegal.com
82 ms
jquery.min.js
75 ms
js_combined.js
29 ms
barelylegal.css
55 ms
baseClasses.css
43 ms
hustlerStyle.css
47 ms
menu.css
46 ms
flowplayer-3.2.13.min.js
47 ms
flowplayer.config.js
46 ms
age-warning.css
55 ms
age-warning.js
56 ms
backout.js
59 ms
postroll.js
55 ms
postroll.css
56 ms
analytics.js
108 ms
bl-valentines-bg.jpg
108 ms
LiveWebCams.php
1401 ms
all.js
157 ms
widgets.js
87 ms
ajax.php
96 ms
ajax.php
259 ms
agePopBLlogo.png
43 ms
fixedNavLogo-BL.png
24 ms
social-icons_sprite-vday-BL.png
25 ms
instantAccessHeartBL.gif
25 ms
content_bg-bl-val.png
45 ms
icons_sprite.png
44 ms
search-button.jpg
42 ms
button_search.png
47 ms
content_top.png
49 ms
sidebar_hide.png
49 ms
notification_bg.png
50 ms
slider_left_button.png
102 ms
0c7fd16e7e325bb3c4e2b13f54372ccb.jpg
111 ms
e816db25139293e33715a1ac87e788cb.jpg
113 ms
slider_right_button.png
102 ms
ajax-loader.gif
102 ms
icon_menu_favorite.png
103 ms
icon_mag_details.png
105 ms
354bccc40a866d74155bff9e1bce66cb.jpg
94 ms
get_megapass.jpg
140 ms
footer2_background.png
99 ms
www.barelylegal.com
170 ms
HHButtonNew_AnimVday.gif
161 ms
linkid.js
14 ms
collect
52 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
147 ms
icon_menu_play.png
55 ms
play_empty.png
56 ms
star_left_full.png
58 ms
star_right_full.png
58 ms
barely-legal.png
70 ms
star_right_empty.png
58 ms
star_left_empty.png
71 ms
74e2d434e3d16491615cbb3f12fbf552.jpg
75 ms
109617e5dfbbfce55063fabd263340bc.jpg
75 ms
9274c53d3eb5c281481d782ba6258f05.jpg
75 ms
collect
76 ms
40 ms
xd_arbiter.php
144 ms
xd_arbiter.php
281 ms
follow_button.b9740740e0bcf9b0657c5b11bd4388da.en.html
65 ms
2d30e107139d82fa7e138b8678ad8af5.jpg
43 ms
82d67f53b9153fc11d1859dca3599270.jpg
44 ms
201862a6aac780077f2c214e3c35b390.jpg
44 ms
03f71da724839f7d0a4bf87da8f6b729.jpg
44 ms
1ab5f3915e9fdfc1f0cf0d809d8cf487.jpg
46 ms
87cf34a9307d79b9a48658c87bb0e26f.jpg
45 ms
6b51e52b1aab8dff16b97a42c7840785.jpg
49 ms
8f98579c0f95da251be512970a20a0dd.jpg
49 ms
info.json
112 ms
jot
98 ms
iframe-717x300-wHov-0001-insert.php
260 ms
jquery-1.7.2.min.js
90 ms
swfobject.js
68 ms
hov.js
68 ms
68 ms
2170517.jpg
29 ms
1922737.jpg
29 ms
1973827.jpg
27 ms
projectw.org 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.
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.
projectw.org best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
Issues were logged in the Issues panel in Chrome Devtools
projectw.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 Projectw.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 Projectw.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.
projectw.org
Open Graph description is not detected on the main page of ProjectW. 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: