Forums

The forums ran from 2008-2020 and are now closed and viewable here as an archive.

Home Forums Other Structuring the “head” tag.

  • This topic is empty.
Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #43117
    matt_sanford
    Participant

    I was filing through some of the posts and noticed that the structure of the head tag is pretty important. I know that doctype and charset is first and foremost, but is there a science to organizing the head? (local css, local js, external css, external js, meta tags) My thought process is that you should link local files last since they will render the quickest and the external scripts and styles first since they require more tome to render?

    Not really a problem, just acquiring knowledge.
    Cheers

    #126822
    matt_sanford
    Participant

    Local being files on the server, and external being extra http requests (google web fonts etc.)

    #126823

    @matt_sanford Local files still require a http request.

    Also, here is what I generally start with:






    #126830
    Merri
    Participant

    A generic recommendation:

    1. Charset
    2. Title
    3. Metadata
    4. CSS
    5. Scripts

    It is also good if you can minimize the amount of requests, although if you have stuff that you can cache to far distant future (this can be done via htaccess/server configuration) then it isn’t that bad even if you have a few more than what some consider “ideal”, that is only have one (massive) stylesheet and one (gigantic) JS.

    If you setup a long cache time and still want to do modifications to the CSS and JS files and don’t want to constantly keep on changing filenames there is one trick you can do:

    Adding the last modification date like this is a good idea as just changing that is enough to force browser cache to reload the script when the modification date is changed. Setting up PHP code to output this information is simple enough.

Viewing 4 posts - 1 through 4 (of 4 total)
  • The forum ‘Other’ is closed to new topics and replies.