10.7 sec in total
3.1 sec
7.5 sec
94 ms
Click here to check amazing Verbal Abuse Journals content for United States. Otherwise, check out these important facts you probably never knew about verbalabusejournals.com
Verbal Abuse Journals chronicles a wife's experience with domestic abuse using posts from journal entries that start in 1990.
Visit verbalabusejournals.comWe analyzed Verbalabusejournals.com page load time and found that the first response time was 3.1 sec and then it took 7.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
verbalabusejournals.com performance score
name
value
score
weighting
Value6.1 s
3/100
10%
Value6.7 s
8/100
25%
Value14.0 s
1/100
10%
Value250 ms
85/100
30%
Value0
100/100
15%
Value11.0 s
21/100
10%
3111 ms
23 ms
248 ms
222 ms
14 ms
Our browser made a total of 136 requests to load all elements on the main page. We found that 30% of them (41 requests) were addressed to the original Verbalabusejournals.com, 7% (9 requests) were made to Ecx.images-amazon.com and 5% (7 requests) were made to Dsum-sec.casalemedia.com. The less responsive or slowest element that took the longest time to load (4 sec) relates to the external source I1.wp.com.
Page size can be reduced by 1.2 MB (70%)
1.7 MB
500.7 kB
In fact, the total size of Verbalabusejournals.com main page is 1.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. Javascripts take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 10 B
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. This web page is already compressed.
Potential reduce by 2.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. Verbal Abuse Journals images are well optimized though.
Potential reduce by 1.0 MB
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 1.0 MB or 77% of the original size.
Potential reduce by 128.1 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. Verbalabusejournals.com needs all CSS files to be minified and compressed as it can save up to 128.1 kB or 83% of the original size.
Number of requests can be reduced by 84 (71%)
118
34
The browser has sent 118 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Verbal Abuse Journals. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 47 to 1 for JavaScripts and from 15 to 1 for CSS and as a result speed up the page load time.
verbalabusejournals.com
3111 ms
shareaholic.js
23 ms
wp-emoji-release.min.js
248 ms
jquery-ui.theme.min.css
222 ms
minimalist.css
14 ms
gsc.css
206 ms
style.css
188 ms
styles.css
109 ms
page-list.css
199 ms
css
42 ms
style.css
156 ms
jetpack.css
294 ms
style.css
236 ms
jquery.js
334 ms
jquery-migrate.min.js
251 ms
gsc.js
271 ms
jsapi
40 ms
multi-column-taxonomy-link.css
301 ms
53219654ed8fe7ccde17b43c1f442eff.json
37 ms
minimalist.css
47 ms
verbalabusejournals.com
1247 ms
asw.js
9 ms
pinit.js
10 ms
core.min.js
268 ms
widget.min.js
276 ms
mouse.min.js
364 ms
resizable.min.js
363 ms
draggable.min.js
363 ms
button.min.js
363 ms
position.min.js
363 ms
dialog.min.js
416 ms
photon.js
416 ms
jquery.form.min.js
415 ms
scripts.js
415 ms
devicepx-jetpack.js
7 ms
gprofiles.js
57 ms
wpgroho.js
415 ms
hoverIntent.min.js
466 ms
superfish.min.js
525 ms
superfish.args.min.js
525 ms
superfish.compat.min.js
466 ms
jquery.flexslider.js
525 ms
wp-embed.min.js
525 ms
e-201611.js
4 ms
css
14 ms
analytics.js
5 ms
linkid.js
7 ms
collect
93 ms
collect
195 ms
get-mentor.jpg
62 ms
safetyplan.jpg
61 ms
share-story.png
58 ms
first-steps.png
55 ms
survivors-playlist.jpg
56 ms
share.jpg
58 ms
malware-destroyed.jpg
50 ms
mentors.jpg
55 ms
escaping-abuse-best-not-easy.gif
55 ms
hate-hate-relationship.jpg
4029 ms
collect
19 ms
bgcon2.jpg
281 ms
wrap.png
281 ms
cropped-header.png
184 ms
subnav.png
282 ms
inner.png
283 ms
list.png
284 ms
shrMain.min.js
28 ms
jquery.min.js
46 ms
pageview.gif
49 ms
app.js
7 ms
partners.js
128 ms
angular.min.js
5 ms
sholic.js
12 ms
usermatch
31 ms
beacon.js
13 ms
cms-sh2c.html
152 ms
eexelate.js
6 ms
20 ms
ep
23 ms
usermatch
18 ms
ep
7 ms
pixel
108 ms
Vu5wb8AoJZYAAM9a0TQAAACw%26971
230 ms
gr
156 ms
pm_match
154 ms
i.gif
175 ms
pixelssl.htm
223 ms
casale
152 ms
105 ms
ping_match.gif
50 ms
net.php
18 ms
casaleopenrtb
33 ms
pixel
45 ms
generic
45 ms
rum
167 ms
pixel
171 ms
rum
156 ms
crum
149 ms
crum
145 ms
2964
119 ms
crum
118 ms
ddcssl.htm
118 ms
pixel
67 ms
ermcm
41 ms
pixel.gif
53 ms
xrefid.xgi
26 ms
pixel.gif
48 ms
rs
42 ms
m
135 ms
match-result
130 ms
crum
106 ms
shareaholic-icons.woff
25 ms
ads-common.js
23 ms
xrefid.xgi
17 ms
crum
24 ms
cm
35 ms
cse.js
66 ms
51nyPphYfuL._SY75_SX60_.jpg
36 ms
36 ms
4121GRUDhwL._SY75_SX60_.jpg
34 ms
51ZfTZxIkNL._SY75_SX60_.jpg
33 ms
4128-ga2aQL._SY75_SX60_.jpg
36 ms
51DDmvU5uxL._SY75_SX60_.jpg
34 ms
51nyPphYfuL._OU01_SL75_PI42-percent,BottomRight,0,0_CR0,0,50,75_.jpg
20 ms
51ZfTZxIkNL._OU01_SL75_PI10-percent,BottomRight,0,0_CR0,0,57,75_.jpg
20 ms
4128-ga2aQL._OU01_SL75_PI17-percent,BottomRight,0,0_CR0,0,58,75_.jpg
22 ms
51DDmvU5uxL._OU01_SL75_PI30-percent,BottomRight,0,0_CR0,0,49,75_.jpg
21 ms
footer.png
96 ms
footer-top.png
96 ms
jsapi
72 ms
pinit_main.js
43 ms
default+en.css
12 ms
default.css
17 ms
default+en.I.js
16 ms
337 ms
default.css
40 ms
verbalabusejournals.com 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
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
verbalabusejournals.com 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
Issues were logged in the Issues panel in Chrome Devtools
verbalabusejournals.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
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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Verbalabusejournals.com 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 Verbalabusejournals.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.
verbalabusejournals.com
Open Graph description is not detected on the main page of Verbal Abuse Journals. 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: