Jeff Matson

Those are just simply GET requests stating that the user is pulling these files from Apache, probably because they are viewing a page that requires them.

It looks like your post themselves are files under archive. When posting a test comment, it did indeed bring me to the comments. Not sure what you may be seeing but it works fine for me.

As the .htaccess file only contains comments, I severaly doubt that it is causing the issue. Check your Apache error log on the server for more information on what the issue is. .htaccess is also recursive so check within any of the directories above it for problematic .htaccess files.

Usually you will find it in your home directory, but it can vary depending on your host. I recommend calling your host to see what’s up.

Thankfully, the WordPress codex has good information on doing so. Follow the WordPress codex article on changing your site url very, very carefully and you should be all sorted out.

Facebook has always been finnicky with pulling their images properly. Your best bet is to define the image using OpenGraph tabs. I’ve seen a few plugins that can do it if you search for OpenGraph.

It’s still quite finnicky even when defining it as Facebook will still show some strange results sometimes, but when posting it you can use the arrows inside the thumbnail when posting the link to Facebook to choose the image as well.

Everything looks fine to me on both Firefox and Chrome. Could you post a screenshot of what you are seeing? Maybe you may need to clear your cache?

If you’ve set the site URL incorrectly, it is probably redirecting you via .htaccess to an incorrect location. To get back into your WordPress dashboard to fix it you can make an easy change to your wp-config.php file which will do the same thing as changing your site URL in your dashboard.

In addition to what Andrew said above, what are your file permissions for the /wp-content/uploads directory? Be sure that the correct owner and permissions are set. Typically, your permissions for folders will be 755.

This is caused by a PHP extension being called by your php.ini file that does not actually exist within the server.

On many hosts, there will be both a default server php.ini as well as one for your account. Take a look at the one in your account to see if it references xcache.so and if not, check with your host about it to check the main php.ini file on the server.

Is anything produced within your server error logs when the page loads or these objects are clicked?

Have you tried another browser to see if that may be causing it?

775 isn’t the best idea. Go with 755.

The permalinks woun’t cause it as it’s just a simple htaccess call.

The ads definitely seem to the the largest contributor to the issue. When loading the site initially, I do see quite a bit of time until the page is rendered and when blocking the ads (with cache cleared of course to avoid any caching speed-ups) the page comes up for me within a second or two.

Of course, your theme does require a bit more optimization as I see it, but the large majority of the issue is due to rendering the ads and making calls to the ad server.

What specific error are you seeing within your error logs?

You’re probably best off using the comment functionality that is already built within WordPress. Be sure to use a captcha though as surely a large amount of spam will come in if you don’t.