Sudden drop in ranking mystery

Hi Faz

It looks as if you've lost a lot of links in the last few months, PM me and I'll send you a list of the lost links. You may be able to rebuild them.

Also, you have a lot of low DA links pointing to your site. You may want to look at increasing the number of high DA links.

HTH

Gaz

Have you tried using more long-tail keywords and update your reading materials on a regular basis?

Hi Gaz, YourGotoWriter,

Thank you for your response.

I actually found out in the search console that my homepage has been partailly indexed due to a googlemap api being blocked

URLhttps://maps.googleapis.com/maps/api/js/AuthenticationService.Authenticate?1shttps%3A%2F%2 Fwww.google.com%2Fmaps%2Fembed%3Fpb%3D!1m18!1m12!1 m3!1d2886.3505877338207!2d-79.38503068457408!3d43.66167797912095!2m3!1f0!2f0! 3f0!3m2!1i1024!2i768!4f13.1!3m3!1m2!1s0x882b34b675 9843cd%253A0x2b0d724370c9ab95!2sAches%2BAway%2BTor onto%2BMassage%2BTherapy!5e0!3m2!1sen!2sca!4v15242 37873041&2sgoogle-maps-embed&callback=_xdc_._k24eq2&token=49130

Type: Script

Reason: Blocked

Severity: Low

robots.txt

I removed a jetpack contact and locations widget that had the blocked api but when I run a page speed analysis - It seems to be still somewhere in the background coding. Along with a bunch of other 'on page' problems.

I need urgent help to fix these as I've already asked google to re-index and I am not sure it will pass.

Can you help - with the backend stuff to correct these issues or suggest a developer who could help me with this in the next day or two?

Thank you for your help,
Faz

PageSpeed Insight
Optimization Good 81 / 100
Data about the real-world performance of this page was unavailable. PageSpeed Insights was still able to analyze this page to find potential optimizations. Applying these optimizations may improve the speed of this page. Please investigate the recommendations below. Learn more.
Page Stats
PSI estimates this page requires 4 render-blocking round trips and ~91 resources (1.3MB) to load. The median page requires 4 render-blocking round trips and ~75 resources (1MB) to load. Fewer round trips and bytes results in faster pages.
Optimization Suggestions
Eliminate render-blocking JavaScript and CSS in above-the-fold content
Show how to fix
Leverage browser caching
Show how to fix
Optimizations Already Present
Show details
The speed data is updated weekly, and the optimization results are cached for 30s. To see updated optimization analysis, please wait for 30s before re-running the test.

Speed
Unavailable
Optimization
Good
81 / 100
Data about the real-world performance of this page was unavailable. PageSpeed Insights was still able to analyze this page to find potential optimizations. Applying these optimizations may improve the speed of this page. Please investigate the recommendations below. Learn more.
Page Stats
PSI estimates this page requires 6 render-blocking round trips and ~90 resources (1.1MB) to load. The median page requires 4 render-blocking round trips and ~89 resources (1.3MB) to load. Fewer round trips and bytes results in faster pages.
Optimization Suggestions
Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 15 blocking script resources and 8 blocking CSS resources. This causes a delay in rendering your page.
None of the above-the-fold content on your page could be rendered without waiting for the following resources to load. Try to defer or asynchronously load blocking resources, or inline the critical portions of those resources directly in the HTML.
Remove render-blocking JavaScript:
http://achesawaytoronto.ca/...-inclu....js?ver=1.12.4
http://achesawaytoronto.ca/...s/jque...n.js?ver=1.4.1
http://achesawaytoronto.ca/.../build...s?ver=20130122
https://s0.wp.com/...ontent/js/devic....js?ver=201818
http://s.gravatar.com/js/gprofiles.js?ver=2018Mayaa
http://achesawaytoronto.ca/....js?ve...7749cee43055c1
http://achesawaytoronto.ca/...assets...fix.js?ver=1.0
http://achesawaytoronto.ca/...evente...ion.js?ver=1.0
http://achesawaytoronto.ca/...ntysev...bal.js?ver=1.0
http://achesawaytoronto.ca/...n/asse...o.js?ver=2.1.2
http://achesawaytoronto.ca/....js?ve...7749cee43055c1
http://achesawaytoronto.ca/...ment-a...=4.2.6-78496d1
http://achesawaytoronto.ca/....js?ve...7749cee43055c1
http://achesawaytoronto.ca/....js?ve...7749cee43055c1
http://achesawaytoronto.ca/...render...=4.2.6-78496d1
Optimize CSS Delivery of the following:
https://fonts.googleapis.com/...0i%2...in%2Clatin-ext
http://achesawaytoronto.ca/...css?ve...7749cee43055c1
http://achesawaytoronto.ca/...cial-i...s?ver=20170506
http://achesawaytoronto.ca/.../plugi...ck.css?ver=6.0
http://achesawaytoronto.ca/...tplaye...=4.2.6-78496d1
http://achesawaytoronto.ca/...css?ve...7749cee43055c1
http://s.gravatar.com/css/hovercard.css?ver=2018Mayaa
http://s.gravatar.com/css/services.css?ver=2018Mayaa
Hide details
Leverage browser caching
Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.
Leverage browser caching for the following cacheable resources:
http://achesawaytoronto.ca/...cludes...s-controls.svg (expiration not specified)
https://www.google.com/...aps!4e3!12...5&token=120703 (5 minutes)
https://www.google.com/...aps!4e3!12...5&token=110278 (5 minutes)
https://www.google.com/...1!1ssmartm...25&token=54775 (5 minutes)
https://www.google.com/...1!1ssmartm...25&token=64786 (5 minutes)
https://www.google.com/...!1ssmartma...5&token=124996 (5 minutes)
https://www.google.com/...m1!1ssmart...425&token=3936 (5 minutes)
https://www.google.com/...1!1ssmartm...25&token=64146 (5 minutes)
https://www.google.com/...1!1ssmartm...25&token=74157 (5 minutes)
https://www.googletagmanager.com/gta...=UA-31082528-1 (15 minutes)
https://apis.google.com/....js?ver=8...7749cee43055c1 (30 minutes)
https://apis.google.com/js/rpc:shind...js?onload=init (30 minutes)
https://maps.googleapis.com/...,sear...n_US&region=ca (30 minutes)
https://www.google-analytics.com/analytics.js (2 hours)
Hide details
Prioritize visible content
Your page requires additional network round trips to render the above-the-fold content. For best performance, reduce the amount of HTML needed to render above-the-fold content.
The entire HTML response was not sufficient to render the above-the-fold content. This usually indicates that additional resources, loaded after HTML parsing, were required to render above-the-fold content. Prioritize visible content that is needed for rendering above-the-fold by including it directly in the HTML response.
Only about 37% of the final above-the-fold content could be rendered with the full HTML response.
Click to see the screenshot with only the HTML response: see screenshot
Click to see the fully-rendered page: see fully-rendered page
Hide details
Minify CSS
Compacting CSS code can save many bytes of data and speed up download and parse times.
Minify CSS for the following resources to reduce their size by 4.2KiB (25% reduction).
Minifying http://achesawaytoronto.ca/...css?ve...7749cee43055c1 could save 4KiB (26% reduction) after compression.
Minifying http://s.gravatar.com/css/hovercard.css?ver=2018Mayaa could save 234B (13% reduction) after compression.
Hide details
Optimize images
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 3.9KiB (29% reduction).
Compressing https://lh3.googleusercontent.com/.....f/IMG_5871.jpg could save 3.1KiB (31% reduction).
Compressing https://lh4.googleusercontent.com/.....hoto.jpg?sz=85 could save 910B (22% reduction).
Hide details
Enable compression
Compressing resources with gzip or deflate can reduce the number of bytes sent over the network.
Enable compression for the following resources to reduce their transfer size by 3.1KiB (69% reduction).
Compressing http://achesawaytoronto.ca/...cludes...s-controls.svg could save 3.1KiB (69% reduction).
Hide details
Minify JavaScript
Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.
Minify JavaScript for the following resources to reduce their size by 2.4KiB (38% reduction).
Minifying http://achesawaytoronto.ca/...n/asse...o.js?ver=2.1.2 could save 1KiB (44% reduction) after compression.
Minifying http://achesawaytoronto.ca/...ntysev...bal.js?ver=1.0 could save 927B (36% reduction) after compression.
Minifying http://achesawaytoronto.ca/...evente...ion.js?ver=1.0 could save 360B (31% reduction) after compression.
Minifying http://achesawaytoronto.ca/...assets...fix.js?ver=1.0 could save 138B (34% reduction) after compression.
Hide details
Optimizations Already Present
Hide details
Avoid landing page redirects
Your page has no redirects. Learn more about avoiding landing page redirects.
Minify HTML
Your HTML is minified. Learn more about minifying HTML.
Reduce server response time
Your server responded quickly. Learn more about server response time optimization.
Download optimized image, JavaScript, and CSS resources for this page.
The speed data is updated weekly, and the optimization results are cached for 30s. To see updated optimization analysis, please wait for 30s before re-running the test.


Web Page Speed Report
URL:

achesawaytoronto.ca

Title:

Toronto's choice for Registered Massage Therapy: Aches Away Toronto

Date:

Report run on Tue May 1 06:55:44EDT2018

Diagnosis
Global Statistics
Total HTTP Requests:

38

Total Size:

632468 bytes

Object Size Totals
Object type

Size (bytes)

Download @ 56K (seconds)

Download @ T1 (seconds)

HTML:

99068

20.34

1.12

HTML Images:

10889

2.57

0.46

CSS Images:

134444

29.39

3.31

Total Images:

145333

31.96

3.77

Javascript:

372767

77.89

5.57

CSS:

15300

3.45

0.48

Multimedia:

0

0.00

0.00

Other:

0

0.00

0.00

External Objects
External Object

QTY

Total HTML:

3

Total HTML Images:

2

Total CSS Images:

13

Total Images:

15

Total Scripts:

18

Total CSS imports:

2

Total Frames:

0

Total Iframes:

2

Download Times*
Connection Rate

Download Time

14.4K

497.79 seconds

28.8K

252.70 seconds

33.6K

217.68 seconds

56K

133.65 seconds

ISDN 128K

46.20 seconds

T1 1.44Mbps

10.95 seconds

*Note that these download times are based on the full connection rate for ISDN and T1 connections. Modem connections (56Kbps or less) are corrected by a packet loss factor of 0.7. All download times include delays due to round-trip latency with an average of 0.2 seconds per object. With 38 total objects for this page, that computes to a total lag time due to latency of 7.6 seconds. Note also that this download time calculation does not take into account delays due to XHTML parsing and rendering.

Page Objects
QTY

SIZE#

TYPE

PAGE

URL

COMMENTS

1

156559

SCRIPT

Main Doc

achesawaytoronto.ca ... ent-and-player.min.js?...

Header size = 221 bytes

Up to 118596 bytes could have been saved through compression.

1

98822

HTML

Main Doc

http://achesawaytoronto.ca

Header size = 284 bytes

Up to 70496 bytes could have been saved through compression.

View a formatted version of this HTML file

1

97184

SCRIPT

Main Doc

achesawaytoronto.ca ... s/js/jquery/jquery.js?...

Header size = 220 bytes

Up to 63500 bytes could have been saved through compression.

1

83132

CSS*

Main Doc

achesawaytoronto.ca ... tyseventeen/style.css?...

Header size = 206 bytes

1

66756

CSS*

Main Doc

achesawaytoronto.ca ... tpack/css/jetpack.css?...

Header size = 206 bytes

1

58798

CSS IMG

Main Doc

secure.gravatar.com ... /grav-share-sprite-2x.png

Header size = 291 bytes

1

44037

SCRIPT

Main Doc

http://apis.google.com/js/platform.js?...

Header size = 917 bytes

1

22861

SCRIPT

Main Doc

http://www.googletagmanager.com/gtag/js?...

Header size = 478 bytes

Congratulations! This file was compressed.

1

21370

CSS IMG

Main Doc

secure.gravatar.com ... ges/grav-share-sprite.png

Header size = 291 bytes

1

18924

CSS IMG

Main Doc

http://wordpress.com/i/noticons/Noticons.woff

Header size = 446 bytes

1

11232

CSS

Main Doc

achesawaytoronto.ca ... player-legacy.min.css?...

Header size = 206 bytes

Up to 8675 bytes could have been saved through compression.

View a formatted version of this CSS file

1

10063

CSS IMG

Main Doc

achesawaytoronto.ca ... usel/images/arrows-2x.png

Header size = 207 bytes

1

10056

SCRIPT

Main Doc

achesawaytoronto.ca ... jquery-migrate.min.js?...

Header size = 220 bytes

Up to 6060 bytes could have been saved through compression.

1

8072

IMG

Main Doc

i0.wp.com ... 018/04/AA-logo-ph.gif?...

Header size = 444 bytes

1

7682

SCRIPT

Main Doc

achesawaytoronto.ca ... n/assets/js/global.js?...

Header size = 219 bytes

Up to 5096 bytes could have been saved through compression.

1

6790

SCRIPT

Main Doc

http://s.gravatar.com/js/gprofiles.js?...

Header size = 329 bytes

Congratulations! This file was compressed.

1

6170

SCRIPT

Main Doc

achesawaytoronto.ca ... enderers/vimeo.min.js?...

Header size = 219 bytes

Up to 3970 bytes could have been saved through compression.

1

5836

SCRIPT

Main Doc

achesawaytoronto.ca ... js/jquery.scrollTo.js?...

Header size = 219 bytes

Up to 3445 bytes could have been saved through compression.

1

5704

CSS IMG

Main Doc

achesawaytoronto.ca ... odes/images/slide-nav.png

Header size = 206 bytes

3

4598

CSS IMG

Main Doc

achesawaytoronto.ca ... element/mejs-controls.svg

Header size = 210 bytes

1

4529

CSS IMG

Main Doc

achesawaytoronto.ca ... arousel/images/arrows.png

Header size = 206 bytes

1

4068

CSS

Main Doc

achesawaytoronto.ca ... -mediaelement.min.css?...

Header size = 205 bytes

Up to 2935 bytes could have been saved through compression.

View a formatted version of this CSS file

1

3754

SCRIPT

Main Doc

achesawaytoronto.ca ... sets/js/navigation.js?...

Header size = 219 bytes

Up to 2608 bytes could have been saved through compression.

1

3646

CSS*

Main Doc

achesawaytoronto.ca ... en/assets/css/ie8.css?...

Header size = 205 bytes

1

3163

SCRIPT

Main Doc

s0.wp.com ... s/devicepx-jetpack.js?...

Header size = 344 bytes

Congratulations! This file was compressed.

1

2892

SCRIPT

Main Doc

http://stats.wp.com/e-201818.js

Header size = 308 bytes

Congratulations! This file was compressed.

1

2817

IMG

Main Doc

i2.wp.com ... ches-Away-Toronto.png?...

Header size = 496 bytes

1

2076

CSS IMG

Main Doc

achesawaytoronto.ca ... arousel-sprite-2x.png?...

Header size = 206 bytes

1

2072

CSS IMG

Main Doc

achesawaytoronto.ca ... codes/images/collapse.png

Header size = 206 bytes

1

2039

CSS IMG

Main Doc

achesawaytoronto.ca ... rtcodes/images/expand.png

Header size = 206 bytes

1

1944

CSS IMG

Main Doc

achesawaytoronto.ca ... slideshow-controls-2x.png

Header size = 206 bytes

1

1398

SCRIPT

Main Doc

achesawaytoronto.ca ... es/js/wp-embed.min.js?...

Header size = 219 bytes

Up to 665 bytes could have been saved through compression.

1

1318

CSS IMG

Main Doc

achesawaytoronto.ca ... s/carousel-sprite.png?...

Header size = 206 bytes

1

1193

SCRIPT

Main Doc

achesawaytoronto.ca ... lement-migrate.min.js?...

Header size = 219 bytes

Up to 660 bytes could have been saved through compression.

1

1015

SCRIPT

Main Doc

achesawaytoronto.ca ... ck/modules/wpgroho.js?...

Header size = 219 bytes

Up to 544 bytes could have been saved through compression.

1

1009

CSS IMG

Main Doc

achesawaytoronto.ca ... mg/slideshow-controls.png

Header size = 206 bytes

1

922

CSS*

Main Doc

achesawaytoronto.ca ... cons/social-icons.css?...

Header size = 204 bytes

1

914

SCRIPT

Main Doc

achesawaytoronto.ca ... p-mediaelement.min.js?...

Header size = 218 bytes

Up to 451 bytes could have been saved through compression.

1

683

SCRIPT

Main Doc

achesawaytoronto.ca ... kip-link-focus-fix.js?...

Header size = 218 bytes

Up to 285 bytes could have been saved through compression.

1

580

SCRIPT

Main Doc

achesawaytoronto.ca ... /photon/photon.min.js?...

Header size = 218 bytes

Up to 242 bytes could have been saved through compression.

1

184

CSS*

Main Doc

http://fonts.googleapis.com/css?...

Header size = 462 bytes

1

123

HTML

Iframe #1

http://www.google.com/maps/embed?...

352

1

123

HTML

Iframe #2

http://www.google.com/maps/embed?...

352

38 ^

632714*

Total (^unique objects)



# Congratulations. This site is using HTTP compression, otherwise called content encoding using gzip. The sizes reported here are for compressed content sent from the server to the client.

* CSS alternate stylesheets may be referenced in the HTML but are not actually downloaded until they are needed and are therefore not included in the total page size.

Analysis and Recommendations
TOTAL_HTML - Congratulations, the total number of HTML files on this page (including the main HTML file) is 3 which most browsers can multithread. Minimizing HTTP requests is key for web site optimization. Y

TOTAL_OBJECTS - Warning! The total number of objects on this page is 38 which by their number will dominate web page delay. Consider reducing this to a more reasonable number. Above 20 objects per page the overhead from dealing with the actual objects (description time and wait time) accounts for more than 80% of whole page latency. See Figure II-3: Relative distribution of latency components showing that object overhead dominates web page latency in Website Optimization Secrets for more details on how object overhead dominates web page latency. Combine, refine, and optimize your external objects. Replace graphic rollovers with CSS rollovers to speed display and minimize HTTP requests. Consider using CSS sprites to help consolidate decorative images. Using CSS techniques such as colored backgrounds, borders, or spacing instead of graphic techniques can reduce HTTP requests. Replace graphic text headers with CSS text headers to further reduce HTTP requests. Finally, consider optimizing parallel downloads by using different hostnames or a CDN to reduce object overhead.

TOTAL_IMAGES - Caution. You have a moderate amount of images on this page (15 ). Consider using fewer images on the site or try reusing the same image in multiple pages to take advantage of caching. Using CSS techniques such as colored backgrounds, borders, or spacing instead of graphic techniques can help reduce HTTP requests.

TOTAL_CSS - Congratulations, the total number of external CSS files on this page is 2 . Because external CSS files must be in the HEAD of your HTML document, they must load first before any BODY content displays. Although they are cached, CSS files slow down the initial display of your page. Remember to place CSS files in the HEAD and JavaScript files at the end of the BODY to enable progressive display.

TOTAL_SIZE - Warning! The total size of this page is 632714 bytes, which will load in 133.65 seconds on a 56Kbps modem. Consider reducing total page size to less than 100K to achieve sub 20 second response times on 56K connections. Pages over 100K exceed most attention thresholds at 56Kbps, even with feedback. Consider optimizing your site with Website Optimization Secrets, Speed Up Your Site or contacting us about our optimization services.

TOTAL_SCRIPT - Warning! The total number of external script files on this page is 18 , consider reducing this to a more reasonable number. Combine, refactor, and minify to optimize your JavaScript files. Ideally you should have one (or even embed scripts for high-traffic pages) on your pages. Consider suturing JavaScript files together at the server to minimize HTTP requests. Placing external JavaScript files at the bottom of your BODY, and CSS files in the HEAD enables progressive display in XHTML web pages.

HTML_SIZE - Caution. The total size of this HTML file is 99068 bytes, which is above 50K but below 100K. With 50K of images and multimedia this means that your page will load in about 20 seconds. Consider optimizing your HTML and eliminating unnecessary features. To give your users feedback, consider layering your page or using positioning to display useful content within the first two seconds.

IMAGES_SIZE - Warning! The total size of your images is 145333 bytes, which is over 100K. Consider switch graphic formats to achive smaller file sizes (from JPEG to PNG for example). Finally, substitute CSS techniques for graphics techniques to create colored borders, backgrounds, and spacing.

SCRIPT_SIZE - Warning! The total size of external your scripts is 372767 bytes, which is over 20K. Consider optimizing your JavaScript for size, combining them, and using HTTP compression where appropriate for any scripts placed in the HEAD of your documents. You can substitute CSS menus for JavaScript-based menus to minimize or even eliminate the use of JavaScript.

CSS_SIZE - Caution. The total size of your external CSS is 15300 bytes, which is above 8K and less than 20K. For external files, ideally keep them less than 1160 bytes to fit within one higher-speed TCP-IP packet (or an approximate multiple thereof). Consider optimizing your CSS and eliminating features to reduce this to a more reasonable size.

MULTIM_SIZE - Congratulations, the total size of all your external multimedia files is 0 bytes, which is less than 10K.

it's common for page rank to drop after doing even tiny change to your website, even changing your post title can cause your ranking to drop.

what you should do is to reindex the page again. after some time you may restore your rankings, it's gonna take time thought, like 3 months.

but in my opinion since you haven't change the content on the page, you only added some plugins, you should not try tweaking the page with more SEO stuffs in attempt to get back your ranking. just reindex the page and wait.

when your website reach first page, you shouldn't be tweaking your web pages with SEO plugins, only focus on high quality links. when you have enough links you can then make the changes you want to make on your web pages.

You may be lost your some good links in the meantime. You have to fix it and it would be good keep doing some backlinks once in a while to avoid rank drop