5.5 sec in total
914 ms
4.3 sec
246 ms
Click here to check amazing Lilith content for United States. Otherwise, check out these important facts you probably never knew about lilith.org
Independent, Jewish & Frankly Feminist
Visit lilith.orgWe analyzed Lilith.org page load time and found that the first response time was 914 ms and then it took 4.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
lilith.org performance score
name
value
score
weighting
Value3.8 s
28/100
10%
Value6.1 s
12/100
25%
Value4.9 s
65/100
10%
Value860 ms
33/100
30%
Value0.036
100/100
15%
Value7.8 s
45/100
10%
914 ms
70 ms
136 ms
994 ms
1997 ms
Our browser made a total of 65 requests to load all elements on the main page. We found that 54% of them (35 requests) were addressed to the original Lilith.org, 6% (4 requests) were made to W.sharethis.com and 5% (3 requests) were made to T.sharethis.com. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain Lilith.org.
Page size can be reduced by 864.7 kB (44%)
2.0 MB
1.1 MB
In fact, the total size of Lilith.org main page is 2.0 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. 45% of websites need less resources to load. Images take 911.0 kB which makes up the majority of the site volume.
Potential reduce by 44.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. This page needs HTML code to be minified as it can gain 11.1 kB, which is 20% 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 44.9 kB or 80% of the original size.
Potential reduce by 48.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. Lilith images are well optimized though.
Potential reduce by 612.7 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 612.7 kB or 76% of the original size.
Potential reduce by 158.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. Lilith.org needs all CSS files to be minified and compressed as it can save up to 158.9 kB or 85% of the original size.
Number of requests can be reduced by 28 (49%)
57
29
The browser has sent 57 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lilith. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
lilith.org
914 ms
lilith.css
70 ms
style.css
136 ms
widgets.css
994 ms
sharing.css
1997 ms
buttons.js
34 ms
jquery-1.7.1.min.js
2065 ms
jquery.easing.js
2410 ms
script.js
147 ms
lilith.js
201 ms
modernizr.js
203 ms
jquery.js
399 ms
mediaelement-and-player.min.js
271 ms
mediaelementplayer.min.css
339 ms
devicepx-jetpack.js
3 ms
e-201736.js
5 ms
e-201736.js
16 ms
count.js
28 ms
async-buttons.js
3 ms
pview
25 ms
buttons.e80452d5e7cc382dad89d10f50bde247.css
3 ms
sc
4 ms
p.js
3 ms
t.dhj
70 ms
t.dhj
7 ms
t_.js
4 ms
generic
5 ms
13 ms
generic
8 ms
ttd
5 ms
generic
5 ms
pixel
14 ms
tpid=CvQICVmvw4IAAAARLOdAAw%3D%3D
9 ms
pixel
13 ms
cs
7 ms
cs
6 ms
50962
91 ms
4722
144 ms
nc2zdb98_normal.jpg
28 ms
unnamed.jpg
133 ms
load-indicator.gif
78 ms
Screen-Shot-2017-08-29-at-1.03.58-PM.png
279 ms
Screenshot-2017-09-01-18.15.42.png
278 ms
Screen-Shot-2017-08-31-at-4.20.12-PM.png
999 ms
1280px-Abolish_child_slavery-2-150x102.jpg
763 ms
AToback-and-Rita-Margulies-Clara-Lemlichs-Daughter-150x200.jpg
211 ms
Screen-Shot-2017-08-30-at-3.47.38-PM-150x139.png
280 ms
Fania-Mindell-1917-outside-of-a-courthouse-in-New-York-NY-150x291.jpg
279 ms
night-view-2172718_1920-150x75.jpg
360 ms
Covers_FINAL-1-130x174.jpg
345 ms
blond2-140x222.jpg
345 ms
lilith_subscriptions1.jpg
346 ms
lilith_backissues1.jpg
411 ms
lilith_celebration2.jpg
476 ms
bodyBg.gif
410 ms
socialMedia.png
423 ms
downArrowTog.gif
476 ms
logo.png
459 ms
topNavigation.png
471 ms
arrow-bg.png
736 ms
lilithHeading.png
520 ms
nlsn
12 ms
g.gif
18 ms
ga.js
18 ms
__utm.gif
11 ms
lilith.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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Links do not have a discernible name
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
Heading elements are not in a sequentially-descending order
lilith.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
Page has valid source maps
lilith.org 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
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lilith.org can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Lilith.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.
lilith.org
Open Graph data is detected on the main page of Lilith. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: