Page not responsive on mobile

Discussion in 'HTML & Website Design' started by lew1s666, Jul 16, 2015.

  1. #1
    Hi, I am using Roots theme and wordpress.
    The website is scrolling fine on mobile devices, but when you go to portfolio item and open it doesnt scroll at all. I tried to disable overflow: hidden but not working.

    http://projects.qbf.ie/bredican/portfolio/kincora-road/#
     
    lew1s666, Jul 16, 2015 IP
  2. kk5st

    kk5st Prominent Member

    Messages:
    3,497
    Likes Received:
    376
    Best Answers:
    29
    Trophy Points:
    335
    #2
    Unable to replicate. Is there a particular device that has the problem?

    cheers,

    gary
     
    kk5st, Jul 16, 2015 IP
  3. deathshadow

    deathshadow Acclaimed Member

    Messages:
    9,732
    Likes Received:
    1,999
    Best Answers:
    253
    Trophy Points:
    515
    #3
    It's the typical "broken attempt at responsive" I come to expect when bootcrap meets turdpress meets PSD jockey. The scripttard show/hide of the logo and fixed menu, text over images in an illegible fashion, massive image files that have no business on a website in the first place, design concepts that have zero business on a page if you care at all about even TRYING to make it responsive, inaccessible fixed metric (pixel) font sizes, goofy hard to read webfont...

    It's very artsy, very pretty, and ultimately useless to visitors because of it... and that's without talking about how ineptly coded it is. Admittedly, much of the disaster under the hood can be blamed on turdpress with the endless pointless DIV and endless pointless classes for nothing, static style in the markup, multiple separate scripttard and framework files for NOTHING; but you mate it to bootcrap with it's endless pointless PRESENTATIONAL classes for nothing and even more pointless code bloat, much less the complete lack of anything remotely resembling semantics or logical document structure... Screen media files sent to all, scripted scrolling garbage, absolute URI's for no reason other than to waste bandwidth (another TP hallmark), stupid malfing data- attributes identical to the hrefs (that's some serious scripttard herpaderp), multiple anchors where only one should be needed, gibberish use of numbered headings...

    Which is why it's vomiting up 20k of markup for not even 2k of plaintext with less than a half dozen images I'd even be treating as content... so at minimum TWICE the code needed just in HTML; much less the batshit over-the-top 4 megabyte pageload in 36 separate files taking around 15 seconds on first-load here. You'd be lucky if visitors even wait for it to finish loading.

    ... and it's a laundry list of how not to build a website, PARTICULARLY if you care about mobile users or responsive design; throwing bootstrap at it does not magically fix flawed concepts much less skipping every stepping stone that should be in place on a site BEFORE you even THINK about trying to make it responsive -- since as I have said for years now responsive design is just the last step in a long line of accessibility and development practices.

    The whole concept is flawed, and it's poorly executed. As I often tell people the only practical or reasonable advice I'd have is to toss that ENTIRE mess in the trash and start over. There is NOTHING present on that entire site that I'd even CONSIDER deploying as a real website for a business. Give it the Ripley treatment and "Nuke the site from orbit, it's the only way to be sure"

    Then take the time to learn something about HTML, CSS, when NOT to just throw scripting at pages, and forget that any of that framework asshattery even exists. While at it learn about accessibility norms like the WCAG. If that's for a "client" and they signed off on it, I pity the client.
     
    deathshadow, Jul 16, 2015 IP