mccloud

Yes and that's because Avada it rapidly becoming out of date (not that it was very good to begin with). Good developers won't go near it as it's a complete pain to use.
 
What you want is simple enough to do, it's just not an off the shelf product - it needs custom code.

I agree, which is why I said to move it down the page. People aren't going to land on this site by chance, they will only land after some targeted marketing. This means they are already on the AIDA cycle. If the site begins with the elevator pitch to assure the potential client they are in the right place they will read on. If you then show the short video (and it needs to be really short) you will reinforce the message.
 
The page then needs to continue - this the long copy that will improve conversions, turning the yes-maybe visitor into a yes. And you can even pull in the no-maybe visitor if you keep pushing the benefits.

I'd agree auto play is bloody annoying, reminds me of the JML adverts blasting out in Robert Dyas. I'd say use an image as a backer with hover play icon. Then use js to load the video where the image is when the visitor clicks play ... now the video is not part of the initial load and you won't scare people away, commonly found when people are browsing at work and an auto play lets the office know what they're up to

Your homepage is 9.1Mb - most of that is the video and the rest is all those plugins and scripts you have added. 115 server calls and a number of those to external resources isn't good.
 
And you have got an awful lot of caggage that needs to load before the site functions. And be aware that using a caching plugin can really slow down a site and yoast can hang badly.
 
Test is on a 3g connection on your phone and it's slow as a slow thing. Google thinks so to, only scoring you 58/100
 
However, it loaded pretty fast on my Mac so I suspect the problem is your mac not just the website.

Providers are getting better and better at hiding their content. Cloud providers for example often encode their embeds so you can't extract the media.

The Ajax is javascript. You don't use window.location you use ajax to make the request to the server along with sending the form data.
To prevent the default action of the form you have to capture the event and prevent it. So there's a load more JavaScript required to make this work. You also need some server side handling to make all this work.
 
You can read up on jQuery here http://api.jquery.com/jquery.ajax/
 
and preventing default actions https://api.jquery.com/event.preventdefault/

The onsubmit in the old code is JavaScript. Bad JavaScript - We should never bind event handlers directly in the HTML, you pollute the global scope doing this.
 
In your new code you are doing a click event on your form. You should instead be doing a submit event. And use the `on` method for this.
$('#submitForm').on('submit', function(evt) { evt.preventDefault(); // do something else. }); It's also worth noting that your code should be wrapped in a DOM ready event.
 
But all this aside I highly recommend you spend time learning JavaScript from a reputable source before you start working with jQuery.

Here's a basic gulp boilerplate I create a few months while I was experimenting with gulp https://github.com/rbrtsmith/gulptest/blob/master/gulpfile.js

Well think about what you would search for if looking for a property.
 
Say you want to buy not rent, a house not a flat, with 3 bedrooms priced between £150,000 and £300,000 in Grimsby. So the query string might look something like
?location=grimsby&prop_type=house&beds=3&min_price=100000&max_price=300000 So your search query might be something like
"SELECT * FROM properties WHERE location = 'grimsby' AND prop_type = 'house' AND status = 'sale' AND beds = 3 and price BETWEEN 100000 AND 300000" Depending of course on the complexity of the tables in use. Which can be quite complex as it needs to account for a very wide range of data to comply with legislation. This is why a lot of estate agents turn this side over to Zoopla, Rightmove and similar services.

Yes, you need to create a database, e.g. MySQL, and populate it with all current property data. Then you write script, e.g. using PHP, that give you all the functionality you need, e.g. update property, delete property, view property etc. It's a lot of work to create full functionality, and there are already many many scripts that cover real estate functionality. So, you are bound to be able to find software that could do what you need if you don't want the big job of writing it all yourself.

Answering your own question
 
 
Have a look at other freelancers and their sites, I'm not saying copying them, that would be naughty but it will give you ideas of how others use their websites, to start with I'd put about me (you not me ), examples of your work (portfolio obviously ) and a contact page, maybe a blog, you might want a section that describes what you can do and your skills.
 
I've been developing websites for years (on and off, here an there), somehow though I've still not got anything to show lol, but with a recent change in career I'm working on it at the moment and too are in your position, where I'm wanting to get my site up and running. I work for a web development company near where I live, I'm also attempting to moonlight as a freelancer in my spare time ( I've checked with my boss, as long as it doesn't conflict he's okay with it ).

Hiya McCloud
 
As your client has an existing plan with one of those website builder websites, the first thing you should do is check over their terms and conditions and look out for any "admin fee's" or minimum terms of contract etc, as we have seen quite a number of those website try to lock people in as part of getting a so called "good deal"..
 
If there is nothing in the T&C's, your second move might also be to drop them a line and ask "Is there going to be any charges from you, if we want the domain name transferred to a new registrar", again, some charge but just dont tell you on their website.
 
As for moving it, a change of registrar has no affect on a domain names DNS records, so you could transfer it to a new registrar every 60 days if you like, but it would not affect any hosting already in place.
 
Once you have it transferred to your new registrar of choice, and your hosting is setup, you can then flip the name servers to the new hosting as soon as you are ready, and then 24hrs later go back to the old server to check for any stray emails that will have arrived after the name servers were changed.
 
The worst thing you can do is to start again with a new domain name, as aquiring any page rank and search rankings takes time, so unless you are established enough to not need any top rankings for a while, its best to avoid starting again where possible.
 
Transfer your existing and you retain all "SEO Juice" as you put it :-) [Never heard it being called that before ;-)]
Start with a new domain name and even with a 301, you loose everything, all "SEO Juice" evaporates.
 
We did this back in Sept 2014, we changed our domain name from "wesh.co.uk"(Page rank 5) to just "wesh.uk" and have yet to get a page rank, but we did get back into the top 20 search rankings within a few months.
 
If you need any help/advice, your welcome to ask us :-)
 
A 10 minute chat before doing something is always better than a 10 day headache after something went wrong..

Moving a domain name is straight forward and would be your first option if you have a functioning website with a Google ranking.
 
If the domain belongs to you and you are fully paid up then there is no reason for the current hosting company to refuse your request to transfer it to another domain registrar.
 
Regarding Nameservers, you usually use the ones provided by your domain registrar. The DNS A records are then updated to point to your hosting IP address.
 
Even with the existing domain name you are likely to have to do redirects to the relevant pages on the new website.
 
Let us know if we can be of any assistance with your web hosting or domain names.

@@mccloud I can't send pm's
 
find and replace so
http://www.livelygreen.com/themes/highgrove/wp-content/themes/highgrove/css/woocommerce.css?ver=4.2.1 becomes
./themes/highgrove/wp-content/themes/highgrove/css/woocommerce.css?ver=4.2.1 etc.

You're right, it isn't
 
But plagarism is rife in this industry so I am always keen to push that we can use others work for inspiration but not to blindly copy, there's a massive open source community where we can copy code

Looking at the source all the links are absolute; some find & replace voodoo to make the links relative will allow it to function.

The url will always be the main domain, it'll never change.
 
Say for example www.yourlivedomain.com is hosted on the old server. When a user types this in a browser it looks up the dns for the domain, so for example ns1.mainnamerserver.com. It then goes to this server and asks what ip address the www record should go to. Then the user is redirected to this server for the web page, this is currently the old servers ip address.
 
Once the new site is ready you essentially change the ip address for the www record to go to the new server ip address to get the new web page.
 
A little reading for you.
 
How Domain Name Servers Work
Simple Guide to HTAccess
 
Edit: Because I was on my phone with man hands and missed points out

No worries. Keep the old site live for now and setup hosting elsewhere to get the new design / site ready. Setup the new hosting under the live domains name and then either map a sub domain to this new space or change your windows host file to go to the new ip address when using their live domain name as a url while developing.
 
Once the new site is ready write in the htaccess file to 301 redirect the old site pages to their new versions on the new site. Finally point their live domain to the new host and only then once complete close the old site builder package.
 
It's important to keep the old site live so the juice will still be there.

Your problem is probably that you are outputting wp_list_pages() inside anchor tags when it outputs li elements by default and should therefore be inside ul tags. Check out http://codex.wordpress.org/Function_Reference/wp_list_pages for examples and information.
 
For your second problem it could be that you saved the other pages with a different encoding. Sometimes code editors are to blame here.

Something like..
 
nav > ul > li:hover > a { border-bottom: 3px solid rgba(255,255,255,1); } Although i'd suggest against using '>' and rather specify class names

Great, that fixed it. Also a good thing to know for the future...
Thanks Jane.

I have found that using Nicolas Gallagher's normalize.css can throw up some unexpected results.
 
Try using margin: 40px auto auto; This might lever the margins the way you seem to be trying to.
 
I'm sorry but I have no experience of java and have not had the flicker problem you are describing, but I know somebody here is bound to have the answer.
 
As to the transitions, your vendor prefixed versions are missing the 'all' property value the other version has!
Your site's box shadows will not be identical in all browser's because your missing the essential prefix's on them as well plus your transitions have no algorithym applied, ie linear, or ease-in-out so the browser does not know how to process this task and will dump it. This may even be why you are getting the flicker.
 
As to you centering trick maybe you should have a read of this article on Codrops - justified and verically centered header elements read it through a couple of times and it will suddenly just click, The use of a pseudo element makes things act muck 'friendlier' in the same confined space.
 
I also noticed you are using floats, have the clearfix class and row class clearfix from Nicolas Gallegher, but are not implementing the row class anywhere else in your css. By this I mean your .row { properties: values; } are missing, for a responsive site to work on this principle you will need to rework this. There are some great tutorials on Codrops about responsive grids, and also about adaptive web design as well. It is a resource I use a lot, along with Elated.com & sitepoint.com
 
Hope these links help.