2.9 sec in total
11 ms
2.1 sec
807 ms
Visit gettingpastyourpast.wordpress.com now to see the best up-to-date Getting Past Your Wordpress content for United States and also check out these interesting facts you probably never knew about gettingpastyourpast.wordpress.com
The Blog for Getting Past Your Breakup (the book)
Visit gettingpastyourpast.wordpress.comWe analyzed Gettingpastyourpast.wordpress.com page load time and found that the first response time was 11 ms and then it took 2.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
gettingpastyourpast.wordpress.com performance score
name
value
score
weighting
Value3.0 s
49/100
10%
Value4.3 s
42/100
25%
Value3.7 s
85/100
10%
Value170 ms
92/100
30%
Value0
100/100
15%
Value4.9 s
77/100
10%
11 ms
547 ms
146 ms
140 ms
138 ms
Our browser made a total of 129 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Gettingpastyourpast.wordpress.com, 25% (32 requests) were made to Gettingpastyourbreakup.com and 7% (9 requests) were made to Static.hupso.com. The less responsive or slowest element that took the longest time to load (622 ms) relates to the external source Gettingbackoutthere.com.
Page size can be reduced by 799.3 kB (35%)
2.3 MB
1.5 MB
In fact, the total size of Gettingpastyourpast.wordpress.com main page is 2.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. 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. Images take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 159.7 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 159.7 kB or 83% of the original size.
Potential reduce by 42.9 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. Getting Past Your Wordpress images are well optimized though.
Potential reduce by 481.8 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 481.8 kB or 62% of the original size.
Potential reduce by 114.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. Gettingpastyourpast.wordpress.com needs all CSS files to be minified and compressed as it can save up to 114.9 kB or 70% of the original size.
Number of requests can be reduced by 72 (57%)
126
54
The browser has sent 126 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Getting Past Your Wordpress. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 39 to 1 for JavaScripts and from 15 to 1 for CSS and as a result speed up the page load time.
gettingpastyourpast.wordpress.com
11 ms
547 ms
style.css
146 ms
style.css
140 ms
style.css
138 ms
yt4wp-frontend.min.css
137 ms
jquery.fancybox.min.css
7 ms
dashicons.min.css
208 ms
thickbox.css
134 ms
baze_styles_youtube.css
206 ms
jquery.js
287 ms
jquery-migrate.min.js
209 ms
jquery-ui.custom.min.js
367 ms
swtcptcf.js
224 ms
jquery.fancybox.min.js
12 ms
youtube_embed_front_end.js
272 ms
iframe_api
48 ms
site.js
136 ms
share_toolbar.js
235 ms
adsbygoogle.js
26 ms
pinit.js
28 ms
plusone.js
56 ms
core.min.js
217 ms
masonry.min.js
220 ms
jquery.masonry.min.js
253 ms
thickbox.js
279 ms
wp-emoji-release.min.js
185 ms
www-widgetapi.js
150 ms
ga.js
61 ms
path112.jpg
616 ms
share-medium.png
135 ms
skiing-150x150.jpg
130 ms
widgets.css
39 ms
settings
110 ms
cs-bk-3d-120x60.gif
231 ms
btn_subscribeCC_LG.gif
141 ms
1agbot.jpg
622 ms
poweredby_FFFFFF.gif
108 ms
116452015056576.1477.1856903108.png
552 ms
pixel.gif
255 ms
change_edited-1-300x207.jpg
100 ms
question.jpg
156 ms
head.jpg
162 ms
check.jpg
144 ms
check_edited-11.jpg
154 ms
learn-300x175.jpg
149 ms
heart21-276x300.jpg
225 ms
trophy1-300x207.jpg
266 ms
stars.png
229 ms
booksmall_edited-1.png
229 ms
__utm.gif
66 ms
twitter.png
120 ms
facebook.png
243 ms
googleplus.png
243 ms
stumbleupon.png
239 ms
digg.png
243 ms
reddit.png
243 ms
email.png
294 ms
widgets.js
7 ms
branding.css
32 ms
branding.css
87 ms
subscribe_widget
48 ms
www-subscribe-widget-vfl_AxbQf.css
28 ms
photo.jpg
280 ms
youtube_icon_small-vfliqe9hM.jpg
130 ms
www-subscribe-widget.js
284 ms
www-hitchhiker-vfluKv9vH.png
240 ms
ca-pub-6549562849083221.js
407 ms
zrt_lookup.html
333 ms
show_ads_impl.js
279 ms
cb=gapi.loaded_0
206 ms
cm
188 ms
cm
201 ms
q
329 ms
cm
191 ms
cm
193 ms
wordpress.png
294 ms
pinit_main.js
235 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
184 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
203 ms
cb=gapi.loaded_1
150 ms
cb=gapi.loaded_2
177 ms
subscribe_embed
170 ms
loadingAnimation.gif
158 ms
4255_300x250._V331031245_.jpg
139 ms
138 ms
124 ms
124 ms
13971_US_AmazonMom_assoc_300x250.jpg
122 ms
KindleCountdown_160x600_wlogo._V353008500_.png
137 ms
118 ms
ffp_assoc_14_728x90.jpg
118 ms
485 ms
ads
430 ms
osd.js
108 ms
www-subscribe-embed-vflWJjAep.css
50 ms
photo.jpg
50 ms
www-subscribe-embed.js
83 ms
a-logo-amazon.png
91 ms
ir
75 ms
json
48 ms
51XGerXeYeL._AC_SR98,95_.jpg
47 ms
prime.png
74 ms
cart.gif
74 ms
postmessageRelay
144 ms
syndication
154 ms
668735400933007360
225 ms
follow_button.b9740740e0bcf9b0657c5b11bd4388da.en.html
57 ms
cb=gapi.loaded_0
47 ms
3193398744-postmessagerelay.js
65 ms
rpc:shindig_random.js
54 ms
cb=gapi.loaded_3
11 ms
subscribe_embed
85 ms
border_3.gif
26 ms
spacer.gif
32 ms
border_3.gif
20 ms
bubbleSprite_3.png
27 ms
bubbleDropR_3.png
46 ms
bubbleDropB_3.png
44 ms
cb=gapi.loaded_0
15 ms
proxy.jpg
138 ms
proxy.jpg
89 ms
proxy.jpg
90 ms
proxy.jpg
85 ms
proxy.jpg
88 ms
www-subscribe-embed-card-vflqARhQ4.css
39 ms
www-subscribe-embed-card.js
38 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.dark.ltr.css
8 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.dark.ltr.css
13 ms
gettingpastyourpast.wordpress.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.
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 IDs are not unique
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
gettingpastyourpast.wordpress.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
gettingpastyourpast.wordpress.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 Gettingpastyourpast.wordpress.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 Gettingpastyourpast.wordpress.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.
gettingpastyourpast.wordpress.com
Open Graph description is not detected on the main page of Getting Past Your Wordpress. 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: