WordPress.org

Ready to get started?Download WordPress

Forums

PageSpeed dont like long font-URL in CSS (9 posts)

  1. JulleHans
    Member
    Posted 7 months ago #

    Hi you great ppl.

    When I do a PageSpeed in Google Webmaster Tools it tells that i REALLY need to change something in CSS.

    I dont think it likes the long URL for the fonts:

    http://fonts.googleapis.com/css?family=Vidaloka:100,200,300,400,500,600,700,800,900|Raleway:100,200,300,400,500,600,700,800,900|Playfair+Display:100,200,300,400,500,600,700,800,900|Oswald:100,200,300,400,500,600,700,800,900&subset=latin,latin-ext,cyrillic,cyrillic-ext,greek-ext,greek,vietnamese

    What can I do help solve this problem?

    Website: http://dagensmode.dk/

  2. Andrew
    Forum Moderator
    Posted 7 months ago #

    Google doesn't like its own page URL? Have you talked to Google about this? http://groups.google.com/forum/

  3. JulleHans
    Member
    Posted 7 months ago #

    lol.. the length.. I dont think its cool about the length of the URL. The way the page loads.. it takes to long time when URLs are really long, atleast that's what I understood. The name of the URL I think is not relevant.

  4. Andrew
    Forum Moderator
    Posted 7 months ago #

    Okay, but it's not just a URL, it's an API... You really need to talk to Google.

  5. JulleHans
    Member
    Posted 7 months ago #

    OK, thanks for the adwise.. But Im sure this could be ANY API. The problem is the length of the URL.

    Google Webmaster Tools says this TIP as adwise:

    "Don't inline large data URIs

    Be careful when inlining data URIs in CSS files. While selective use of small data URIs in your CSS may make sense, inlining large data URIs can cause the size of your above-the-fold CSS to be larger, which will slow down page render time."

    I dont know much about WP and Web. But I think the problem is the URL lenght used in the CSS file.. Else i dont..

    Anyone els have an idea to change this prob?

  6. Bill
    Member
    Posted 7 months ago #

    You left out that detail in your original question. Google is telling you not to use them inline. Better to put them in your stylesheets when possible, which also makes changing them site-wide later much easier if you need to.

  7. JulleHans
    Member
    Posted 7 months ago #

    Thank you Bill. Sry for the lag of important information :)

    So if they shouldnt come inline.. would this be the right way?:

    @import url(http://fonts.googleapis.com/css?family=Vidaloka:100,200,300,400,500,600,700,800,900

    @import url(http://fonts.googleapis.com/css?family=Raleway:100,200,300,400,500,600,700,800,900

    @import url(http://fonts.googleapis.com/css?family=Playfair+Display:100,200,300,400,500,600,700,800,900

    ...and so on @ eatch font.

    2. How can I put them in your stylesheets ? do you know what I would have to google to learn that? or do you have a quick guide? :)

    Thanks agin Bill :)

  8. JulleHans
    Member
    Posted 7 months ago #

    you = my stylesheets ... lol!

  9. Bill
    Member
    Posted 7 months ago #

    Taking a step back, I took a quick look at your homepage and saw that there are several link elements for stylesheets at the bottom of the body element. Normally they belong in the head element. (One of those is also for a Google font, by the way.) Maybe this is what webmaster tools is complaining about?

    I don't know enough about that to be much help to you, I'm afraid. Andrew's suggestion about talking to Google is still a very good bet. But I would guess that the link elements are being dropped there by your theme (Braxton?) so you might also try asking them about it. It seems to be a premium theme so they should have support for you.

    Be aware that changes you might make will take a while to show up in webmaster tools because: 1) Google will have to crawl your site again, and 2) You have the W3 Total Cache plugin in use, so you need to clear that as well (which you probably know already). Best of luck with it.

Reply

You must log in to post.

About this Topic

Tags

No tags yet.