I noticed that my page/onlineshop seems to load quite slowly on mobile. I already optimized anything I could in the past and always get a 95-100 lighthouse score on desktop which is great I guess. Still I cant manage to get it above 60-70 on mobile and I think thats too slow?
Unfortunately I'm not very experienced and have absolutely no idea where the problem is located. I would be very very thankful if someone could take a look and maybe give me at least a direction where I should focus on.
https://gesundbaumarktshop.de/produkt/auro-gartenmoebeloel-nr-102/ for example but basically any product has the same issue
i will recommend you reduce all your website image. that will help alot
Overall, your page size is fine. Lighthouse is also not the end all be all for testing and I tend to use 2-3 services to test speeds.
However, CDNs may make a huge difference along with server side caching.
If you are able to, I'd recommend running your DNS through Cloudflare. They actually have a plan specifically for WordPress that is $5 USD roughly a month?
Related
I've got a WordPress website I'm currently working on. It was loading extremely fast just a couple days ago, then got extremely slow all of a sudden.
I've tried disabling plugins, removing large elements from the homepage (videos and such), and upgrading the server to see if that would help. This problem is especially noticeable on iPhones and in the Safari web browser.
I'm not really entirely sure what I should be asking, but the site can be found at https://dev.kwonkwon.com/ - if anyone can provide any sort of advice or is able to point me in the right direction, I'd greatly appreciate it.
You can optimize your site:
check your website here https://gtmetrix.com and follow the suggestions, it is useful.
I have checked your website, you really need to optimize your images.
I am quite surprised because I just look at your website. A website like this should be loaded in under 3 seconds.
Check out your website test results here
First, You need to optimize your images. Scale the images to a size that you are using and use tinypng.com for compression if you do not know how to use Photoshop.
Second, Use a cache plugin. You can test all of them and see which one suits the best. W3 Total Cache is ok.
Third, Revslider is the worst. Try not using it. You can also add a simple background.
I had a website which was built using the CMS WebYep. Now I want to shift it to WordPress. Can anyone tell me how to do that?
Thanks is advance :)
Regards,
Ryan
I'm afraid there is no automatic process for most CMS.
You can either do it manually, or write a program (or hire somebody to write it) to help do the job.
In most cases the manual way is preferred. Different content management systems work quite differently, so there's usually not a universal way to set things up. Recognizing the differences and how to achieve a similar result is an easy thing to do for a human but a very hard thing to do for a computer. Plus, from my experience, with a relaunch usually comes a re-structuring. When you're moving to a new house, you might just get rid of that old broken sofa while you're at it, basically.
When you have a very large website with lots of similar content, a developer can certainly write scripts to aid in the process of moving your content over to WP. This will usually not be cheap, so it's not a smart idea for a site that consists of a dozen pages or where the content isn't very homogenous.
I am working on a WordPress site for a client that averages 300 - 1500 users daily (these numbers will double five months of the year). They have been consistently bringing up bugs on the site that need fixed.
I am curious if automated tests are worth it for a site this small? If so, any suggestions on what to use? I am leaning towards something like Selenium for functional testing, not unit tests. Suggestions welcome. Thanks.
Here are my thoughts on this (as someone who was considering it for a new Wordpress site):
Consider what you hope to accomplish by testing. In my case, I have a static main page, a static page with a list of resources (links to external sites), and a blog page. If I am going to test this with Selenium, I am not going to worry much about tests of functionality - there isn't any. But I am going to be concerned about the appearance of the site, which Selenium isn't good at testing. For appearance, I need eyes on the site looking for issues.
You mention that your users "have been consistently brining up bugs on the site that need fix[ing]" - what kind of errors?
If the errors are related to functionality (eg. when I click on button X, I get Y when I should get Z), you will probably be able to test that with Selenium. This might be the sort of error that #mathieu-vezina was alluding to: if you have multiple plugins that are conflicting, writing Selenium tests will help you identify when these conflicts are happening. However, this is probably something you could figure out without Selenium and if there are problems with third-party plugins, you're at the mercy of the developers when it comes to bug fixes. So Selenium tests will probably not be much help here.
If the errors are related to appearance (eg. the elements are the wrong shade of pink and shifted up too much), you will not be able to test that with Selenium.
Keep in mind too that it takes a fair amount of work to write Selenium tests and the maintain them - in most cases, the benefit is going to be too small to justify the amount of effort.
I personally do not think it is worth testing your wordpress site if you do not use several plugin and you only have between 1000 and 10000 users. If you use several plugin, I recommend you to read this article to make sure they will not affect your website : https://woocommerce.com/2015/08/evaluate-plugins-woocommerce/
Also, Selenium have few limitations, for example, it is restricted to only Firefox and it lacks the ability to scale well, so you will not test all functionality.
I'm considering putting the Google Analytics tracker on my blog to get better stats (right now I use Summary.net, which is fast but occasionally of questionable accuracy, though way better than awstats). At any rate I have 2 big concerns and though I should ask the community here for opinions:
Privacy. In the past I've gone so far as to block Google's IPs for adsense and tracker. Basically it seems like at this point everything you do online is visible to Google in some way or another, but at the same time I wonder if this really matters. Should I just shrug my shoulders and embed the code?
Latency. I'm not very technically inclined so I don't know much about this, but I heard that if Google is having issues, you site will as well, just by including their code. is that possible?
Thanks!
1) Impossible to answer. If you're running a website for an illegal drug trafficking network, then I probably wouldn't use Analytics. Otherwise, I personally don't care. You could monitor your HTTP traffic and see exactly what the payload is if you're concerned about them tracking anything more than simple IP / browser data. If you're concerned about them knowing "who" visited your site, and have a valid reason, then don't use it.
2) Yep. Have you ever noticed a page taking a while to load and in the status bar it says it's waiting on google-analytics.com? I see it on a somewhat frequent basis on both small and large websites. It's not too big of a problem though IMO.
I believe that it's a recommended best practice to place your analytics script as close to the bottom of your page code as possible (the same would be true for any external scripts).
I'll also add that I didn't really like the idea of Google Analytics much until I started using it. The benefits really seem to outweigh the drawbacks. Its reporting is just fantastic. I still use AwStats on the same sites, however, simply because the data is accessible...and it's nice to compare numbers.
There are probably thousands of applications out there like 'Google Web Accelerator' and all kinds of popup blockers. Then theres header blocking personal firewalls, full site blockers, and paranoid cookie monsters.
Fortunately Web Accelerator is now defunct (I suggest you read the above article - its actually quite funny what issues it caused) but there are so many other plugins and third party apps out there that its impossible to test them all with your app until its out in the wild.
What I'm looking for is advice on the most important things to remember when writing a web-app (whatever technology) with respect to ensuring the user's environment isnt going to break it. Kind of like a checklist.
Whats the craziest thing you've experienced?
PS. I may have linked to net-nanny above, but I'm not trying to make a porn site
The best advice I can give is to program defensively. For example, don't assume that all of your scripts may be loaded. I've seen cases where AdBlocker Plus will block 1/10 scripts that are included in a page just because it has the word "ad" in the name or path. While you can work around this by renaming the file, it's still good to check that a particular object exists before using it.
The weirdest thing I've seen wasn't so much a browser plugin but a firewall/proxy configuration at a user's workplace. They were using a squid proxy that was trying to remove ads by replacing any image HTTP request that it thought was an ad with a single pixel GIF image. Unfortunately it did this for non-GIF images too so when our iPhone application was expecting a PNG image and got a GIF, it would crash.
Internet Explorer 6. :)
No, but seriously. Firefox plugins like noscript and greasemonkey for one, though those are likely to be a very small minority.
Sometimes the user's environment means a screen reader (or even a braille interface like this). If your layout is in any way critical to the content being delivered as intended, you've got a problem right there.
Web pages break, fact of life; the closer you have been coding and designing up against standards, the less your fault it is.
Something I have checked in the past is loading some of the more popular toolbars that people tend to install (Google, Yahoo, MSN, etc) and seeing how that affects the users experience.
To a certain extent it is difficult to preempt which of the products you mentioned will be used by your users since there are so many. I would say your best bet is to test for the most frequent products that your user base may employ and roll with the punches for the rest. If you have the time to test other possible scenarios, by all means do.
Also, making it easy for your users to report possible issues also helps lessen the time it takes to get a fix in place should it be something you can work around.