-
1. Re: speed up website?
Without a link to your site no one really can provide any direct feedback I am afraid.
If your after just general stuff, you can google, there are lots of articles out there.If you want feedback on your site, you will need to provide a link so people can have a look.
-
2. Re: speed up website?
Take a look at what is slowing down your site, client side the most common issue is un-optimised web images, using the web console to take a look. In Chrome right click on the page and inspect element. Click on the network tab and then refresh the page again, it will give you a time on every element on the page and how long it took to load and it's size. Find the bottle neck. If you find that the issue is NOT in fact your HTML / images or code, you can submit a support call to Adobe for them to investigate as I have had issues with slowness that was unrelated to the code but the server itself.
-
3. Re: speed up website?
Thanks TheBCMan. Very helpful will start with that.
I've optimised most via Photoshop but will try another program - is optimising for web speed just reducing the size without loosing clarity?
Liam - sorry that would have been helpful to provide - here is the link.
-
4. Re: speed up website?
There isn't really anything here that seems too heavy your main page as it is 57.9K which is totally fine, was there are particular page on the site that was "slow" or a page google reported as slow?
-
5. Re: speed up website?
/avatar/46.png?a=-1)
Google's PageSpeed Insights tool provides straightforward advice on how to improve your page's performance.
I gave it your site; it scored 35/100 for mobiles and 48/100 for desktop browsers.
Just implementing two of the high-priority suggestions could cut ~620KiB from the page weight for desktop browsers -- 385KiB from crushing the images, 237KiB from minifying your CSS & JS. (what!)
Not to mention the requests that are render-blocking.
As for actually optimizing your images, there's a quick checklist here, which is part of a thorough guide here.
(Ignore the "Leverage Browser Caching" recommendations, there's naught you can do about that)
TheBCMan - where did you get the figure of 57.9K from? My dev tools report 1.6mb downloaded over 96 requests for that page...
-
6. Re: speed up website?
Robert: Ahh yeah good tip. Answering your question I got my data from the console, I might have had some thing cached as I didn't do a hard refresh, I also had 100 requests from the page so that is strange.
-
7. Re: speed up website?
Thank you everyone for your feedback. Much appreciated.
Robert your reply was super helpful
I've optimised images as much as I can and now we are at 64 / 100 for desktop - which is much better!
I asked our web designer to minifying CSS & JS and she's said it's done too.
Now the only things that are showing are:- Leverage browser caching - which we can't do anything about (from Robert's answers) and
- Eliminate render-blocking JavaScript and CSS in above-the-fold content
Our designer's going to go through the css and remove anything not used - would there be anything else that might make a difference?
What was confusing me most was that only a few weeks earlier we were 75/100 and then without any changes we dropped.
Thank you again for all your help
-
8. Re: speed up website?
'Render-blocking CSS and Javascript' refers to the
<script>and<style>tags in the<head>of the HTML. Basically the page can't start being drawn until all that javascript has been processed, and the javascript doesn't get processed until the CSS has been loaded and parsed.The simplest way around it is to have the bare minimum of CSS before your page's content, only what is absolutely necessary to draw the basic page content. The rest of the CSS and all the Javascript should go to the end, just before the
</body>tag.That's not even half the story though; I recommend this one-day course to really understand what's going on behind the scenes, and why it's worth so much to your site's usability: Website Performance Optimization Testing Course - Udacity
-
-
10. Re: speed up website?
Not your CSS Robert, bad practise, that should be in the head and not minimised, increased CSS files is a performance hit.
Things will change anyway with BC.Next.