best approach for file structure?

Question

What is better / faster?
We need a short and fast file structure for a javascript / ajax web app

rs -> c (for css files)
rs -> j (for js files)
rs -> i (for images)

or:

-> stylesheets
-> scripts
-> images

or:

-> css
-> js
-> img

does it make any difference if the urls are shorter?

score 1 · Accepted Answer · answered Jun 11 '12 at 08:14

1

If you're concerned about two or three bytes in your source code per resource (pre-compression). Then either your website is already highly optimised or you're looking in the wrong place for performance gains.

I'd be more concerned with how your content delivery is spread across things like subdomains/CDNs to maximise load throughput.

Ensure everything is cacheable, also things like ensuring your script includes are bunched up if you can and includes in your CSS.

answered Jun 11 '12 at 08:14

Jeff Watkins

6,343
16
19

so using client side storage and json combined with cookies for caching requests would improve the performance much more – Jun 11 '12 at 08:21
1

AJAX will decrease the need for full page loads. Your images, CSS and JavaScript should be cached as long as your webserver is set up correctly. If you use multiple subdomains for delivery of your payload or a CDN then you'll find that you'll maximise the amount of parallel loading you can do. – Jeff Watkins Jun 11 '12 at 08:26

score 0 · Answer 2 · answered Jun 11 '12 at 08:14

The folder names make no difference. You should focus on actually optimizing your files and how they are delivered.

Once you have optimized your files, consider looking into a content delivery networking like www.cloudflare.com if you are worried about speed.

best approach for file structure?

2 Answers2

Linked