Viewing 8 replies - 1 through 8 (of 8 total)
  • 1.
    Try to fight the 404 Errors of your site… clean the template ??
    https://www.egado.de/wp-support/chrisfawkes.png and the 500 internal server error…

    2.
    Install browser plugins like Yslow and google page speed to test whats going… and what you should improve…

    3.
    Guess you should have a look at wordpress caching solutions… that will speed up your site…you will need to study the plugins, they are very complex, but very very very effective ??

    test it with the pingdom tools ( https://tools.pingdom.com/fpt/ ) or something else… test of your site: click here…

    Caching Plugins…

    Helping resource:

    Yeah, the trick is not to preload the next page (not even possible I think) but to make your site crisp and fast.

    Try egado’s tips above but start with the basics. You probably have way too many scripts en css style sheets running. I’m guessing you’ve got a lot of plugins installed. Remove all the stuff you don’t use/need.

    Also make sure to remove broken code (f.e. line 14 in the source code). try using the latest version of jquery and use the google CDN for jquery.
    Validate your html to check for errors. …

    Do these basic things before you start optimizing the page for speed.

    Thread Starter fawkesblog2

    (@fawkesblog2)

    The site has a ranking of 97% on googles speed tester. Faster than most and faster than googles speed test site.

    The 500 internal error only shows on the speed test and only after adding the gzip capability to compress files as suggested by google. The site gets a higher ranking with gzip so as long as the 500 internal error is not actually interfering with user experience i’ll leave it. Unless there is some reason to change it.

    Does anyone have an answer to my original question?

    Cheers.

    Thread Starter fawkesblog2

    (@fawkesblog2)

    Interestingly the HTTP error code 500 only started appearing right after i added the code for the gzip compression to the header. Removing that code does not change the error code 500 though so must have been something else causing it. Not sure what though.

    Site Speed… yes google speed test 96/100 but it doesnt test the time your page need to be fully loaded… believe me, your site would not be faster while preloading the next page, couse you 1. dont know which page the user will visit next and the 2. most important, without caching the site your server needs a lot of time to proceed the php. I mean your server needs to build the site for every page request by your visitors, caching will serve static files, which will deliver up to 95% faster…

    Test your site witch https://loads.in/ or https://www.webpagetest.org/

    Site speed seems to have improved a bit …?
    Still some errors showing.
    f.e. empty scriptline in line 14 + make sure you use correct html.

    <script type=”text/javascript”></script>

    Don’t use ”, use “.

    Google analytics is in the wrong place. Either put it inside the head tags or inside the body tag, not between the head and body.

    Your html is still flawed. Missing closing elements. Validate your html:
    https://validator.w3.org/check?verbose=1&uri=http%3A//chrisfawkes.net/blog/&charset=%28detect+automatically%29&doctype=Inline&ss=1&group=0&verbose=1&user-agent=W3C_Validator%2F1.606
    (look for missing tags)

    I’m also looking at that jCarouselLite script in your code. Are you actually using that? Can’t see any slider on your site. If not, remove.

    Looking into this, you have some javascript errors. This: jquery.jcarousel.pack.js needs to be loaded after you load jquery.js. This is important.

    Some other points: lots of inline css and scripting on your page. Some is flawed, f.e. line 225
    <div id="logoimg" style="background-color:; padding:1px 0;">
    No background-color declared.

    As a rule, avoid inline scripting (javascript inside html) and try and place all your css together in seperate style sheets.
    Also, would be nice to put css in the head and scripts in the end of the html (just before closing body tag).

    A note on the tabs. All the tabs (and the images inside them) load simultaneously. So that’s a lot of requests to the server before the page is loaded.

    Oh, and that background image is massive! Way too big, get rid of it. That’s unconditional.

    Thread Starter fawkesblog2

    (@fawkesblog2)

    Thanks Guys.

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘Is there a way to have the next page load before the viewer clicks on it.’ is closed to new replies.