j09

@michan7

Great!

I checked your page again and there are no more 403 errors.

There are however some images that are giving 404 codes – File not found

@evilsaigon

I just checked again and all four pages are using the green theme. Did you change anything?

@michan7

The images are giving a 403 Forbidden response code. You have some sort of permission issue.

Does the same thing occur if you temporarily disable all plugins?

Hello @sozzysoraan

Whether or not the images are being used, they are being requested. I don’t know how that theme works and it’s unacceptable that they won’t provide support to something you’ve paid for.

Long story short, you have a lot of images on that page and like you said, most of them should’t even be there.

If you open your browser console (using the F12 key) You can see that most of them are being loaded under Project Panel

Now, I don’t know what “project panel” is but it appears to be a function of the theme you’re using. As can be inferred from this support question. Semplicelabs Poject Panels

@kosmicbird

Welcome to the most frustrating part of webdesign – Cross-browser support. Well, at least second most (pleasing Google tops that list by far!)

The first thing you need to do is make sure the problem is not caused by some silly thing like browser cache or things of that nature.

IF the problem persists then you’re most likely using CSS in a way that’s not supported by all browsers.

The thing about browsers is that they are all built differently. Each browser has it’s own support range. Further more, older versions of the same browser may not support the same design elements.

If you’re not interested in the long version of why this is so and you just want a way to fix it and spend your time on creating content instead, consider using or “borrowing” from “standardized” CSS projects like Bootstrap or W3C Core Styles or any other projects along those lines.

If you’re interested in seeing whether a design element is supported by all browsers you can use services like Can I Use

Hello @jzhu5
Adding to what what @wpaleks kindly wrote above.

There are three main problems with your site:

———————————————–

1- You have too many script files (+40)

Each script file is like a mini program that your visitors need to download and process in order for your page to display.

Each of those script files needs to be parsed and processed. You have more than 40 of those. It takes time to process them.

Script files “hog” the browser. This means that they demand the browser’s full attention by default – unless they are marked as asynchronous.

“asynchronising” scripts is a fancy way of saying that you instruct browsers to load other elements on the page while they process the script file

So, what should you do about scripts?

The best practice is to use the least amount of scripts possible. Be aware of how many scripts the plugins / themes you use require. Not all code is created equally and sometimes you should just avoid bloated plugins / themes.

Once you’ve cut down on unnecessary script files, you should then proceed to combining what ever script files you ended up with.

This sounds fancy, I know, but it’s really nothing more than merging the contents of the separate scrip files into fewer file. There are plugins that can do that for you or you can do it manually, although the later requires a bit of knowledge to make sure things still work as intended.

After doing that, you need to make sure you either “async” the script file(s) that you end up with or make sure it loads after your content – near the bottom of the page

———————————————–

2- You have too many CSS files.

CSS files are just files that contain information that tell the browser what to do with the content on the page. Things like how big the text should be or what color the header should be.

Treat them in the same way that you would treat script files I mentioned above.

Reduce any bloated stuff you don’t need, then optimize and combine what you have left at the end. Again, there are plugins that can do this for you or you can do it manually.

Much in the same way that script files “hog” the browser, CSS files also require full attention until they are fully downloaded

The difference is that you can’t “async” CSS files – you can put them at the bottom of the load order – near the footer – but that opens another can of worms.

———————————————–

3- Too many requests.

This is an exaggerated analogy, but it drives the point home.

Imagine this,

You have a grand party and you want to order 100 pizzas, so you call the pizza shop. Now one of two things can happen.

A- you call / order pizza #1 / hang up / call again / order pizza #2 / hang up / call again / order pizza #3 / hang up / ……etc until you get to pizza #100

Or

B- you call / order 100 pizzas / hang up / done.

You can obviously tell that the later is a lot less trouble / much faster.

Your page has 99 separate requests. Each request is an item (can be a script file / or a css file / or an image / or a font file)

Your page is currently using method A from the analogy above.

The goal is to reduce the number of calls (or http requests) – More like method B

Reducing / combining your script files as I mentioned above will help cut down your requests. I should also note that you need to keep the number of fonts to the minimum. You don’t really need more than 1 – 2 fonts. Images can be combine using CSS sprites

After you do all of the above, you need to get familiar with caching

You are not serving cached pages.

When a user visits your a page on your website, your server has to “construct” it from all the different sections of your database / php files and that takes time.

meet Caching!

Caching is like a xerox machine. if you have a xerox machine, you can just make a copy of the document and serve it almost instantly.

Serving dynamic content without caching is literally like typing the whole document all over again – even if you already have the content memorized – every time it’s requested – it takes more time.

There are many great caching plugins.

Note: “WP Super Cache – Clear all cache” is not a caching plugin. IT only adds a function to the actual caching plugin “WP Super Cache”

———————————————–

Now, CloudFlare

You can keep GoDaddy hosting and still use CloudFlare for free.

CloudFlare is a great service and I highly recommend it.

If you set it up correctly, your traffic goes through the CloudFlare network and your pages – which are cached by CloudFlare – are delivered to your users faster.

CloudFlare Cache works this way:

it only stores a cached copy of your content if it’s only been accessed from that CND Data Center before.

This means the same content from same Data Center location, anything else gets loaded directly from your server – and then it’s cached after that.

Even if you use cloudFlare, you still need a server-level cache solution – like a cache plugin.

———————————————–

About those redirection chains:

The first redirection chain is caused by incorrect https redirects; just look for WordPress SSL redirect in google, there are many fixes.

The second one is caused by a plugin / CDN

Good Luck!

You’re welcome and I am glad it worked out!

Good luck