Markus Schwingruber

Forum Replies Created

Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • in reply to: Insert additional line in footer with link #5141
    Markus Schwingruber
    Participant

    Perfect. But how can I do this?
    Cheers,
    Markus

    in reply to: Change footer #3207
    Markus Schwingruber
    Participant

    Dicot theme.
    Thanks,
    Markus

    in reply to: Remove Date from Post List #1703
    Markus Schwingruber
    Participant

    Wow, this was fast! And great, it works perfectly, thanks a lot!

    in reply to: Performance problem: Images are resized in HTML or CSS #1686
    Markus Schwingruber
    Participant

    Hello DeginOrbital-Team

    Thanks a lot for discussing my questions, I really appreciate it. Still I am not quite happy with your answer, I am afraid. There might be a missunderstanding: I do not worry so much about page speed in millisecs or secs but about the PageSpeed score of Google. You can run this test at https://developers.google.com/speed/pagespeed/insights/. And this score affects the page ranking in Google’s search engine heavily. I have attached an image of my PageSpeed Score from gtmetrix.com. You can see there that the main problem resulting in a below average score is «not serving scaled images».
    After reading quite a lot about this issue I am sure that serving double resolution images on non-retina devices and adjusting their size client-side is not a good way to go regarding serach engine optimization (it will result in bad ranking). I think a far better way is to detect retina-ready devices on the server and serve the retina-ready image (double size) to that device. And all non-retina devices should be served the smaller, lighter non-retina image (normal size).

    Reducing the file size in the theme’s function file as you have suggested would do the trick regarding the above problem but my website would then look bad on retina displays. So this is not really a solution.

    I wonder why you would object to the above outlined approach. May I ask you to reconsider your decision?

    Thanks a lot and warm regards,
    Markus

    in reply to: Performance problem: Images are resized in HTML or CSS #1684
    Markus Schwingruber
    Participant

    Hello
    I was wondering if the development team could already have a look at this and if not by when I could expect an answer.
    Thanks a lot and best regards,
    Markus

    in reply to: Performance problem: Images are resized in HTML or CSS #1682
    Markus Schwingruber
    Participant

    Hi Admin,

    Thanks for your quick reply. But this time I do not agree with your answer. I am sure there will be a severe problem in the ranking of Google if the “must have” recommendations of their page speed analysis regarding image optimization are ignored (and these are the ones I have in my original post above). After reading several articles on the web regarding this issue I find on of the most helpful article this one:
    https://fruition.net/blog/page-speed-vs-high-res-images/
    It says in the section “Best Practices for Images on Your Website”:
    “Make the low-resolution version of your graphic available by default. While HiDPI displays are becoming more widely available, the technology has not yet been adopted by many computer and mobile device manufacturers. Serving high-resolution images by default would slow page speed unnecessarily for most users who are not using devices with retina displays. For the time being, using media queries to determine visitors’ screen resolution and serving them the appropriate image seems to be the best solution.”

    Is there a way how you could implement this in Dicot?

    Many thanks and best regards,
    Markus

    PS: Beside this issue a love the Dicot-Theme a lot. It’s awesome! Thanks!

Viewing 6 posts - 1 through 6 (of 6 total)