1. Advertising
    y u no do it?

    Advertising (learn more)

    Advertise virtually anything here, with CPM banner ads, CPM email ads and CPC contextual links. You can target relevant areas of the site and show ads based on geographical location of the user if you wish.

    Starts at just $1 per CPM or $0.10 per CPC.

[Review] Website Seo and Design

Discussion in 'HTML & Website Design' started by irfansyah, Feb 22, 2021.

  1. #1
    Hi, Everybody who help me!
    Try you open my website >> Contoh desain grafis, I need you for give feedback to my site that is. You can see design and seo and you feedback fell me happy
     
    irfansyah, Feb 22, 2021 IP
  2. deathshadow

    deathshadow Acclaimed Member

    Messages:
    9,732
    Likes Received:
    1,998
    Best Answers:
    253
    Trophy Points:
    515
    #2
    Not the right forum area for it, but I'll give it a go. Warning, I don't sugar coat it. I'm going to tell you what you NEED to hear, not what you want to hear.

    First thing I see is illegible colour contrasts in direct violation of accessibility minimums. The white on blue text completely fails.

    I suggest that you use a tool like the one at webAIM:

    https://webaim.org/resources/contrastchecker/

    I also suggest that if you're gonna go with a webfont or anything "thin-glyph", you treat "AA Normal" as your MINIMUM, try for AAA, ignore the "large' values entirely. Differences in font rendering tech since the WCAG norms were established means you need to err on the side of caution.

    We plug in your values -- white #FFFFF and the blue #73A9D6 and the ratio is 2.5:1, /FAIL/ at every level. You'd have to darken the background to #3479B2 to meet AA, or #275B86 for AAA.

    The orange buttons are similarly flawed.

    Next up the layout is slopped together with pixel measurements, telling users with accessibility needs diving for the zoom. The willy-nilly changing of font-sizes isn't helping matters either in terms of clarity or navigation. The moment you see a font-size declared in PX, you're looking at the pesky 3i of web development; ignorance, incompetents, and ineptitude. The measurement that should be used design-wide for font-size, fixed/max-widths, etc, etc, is EM. Likewise it seems to be relying on fixed pixel heights on a lot of things that shouldn't even have height declarations on them in the first place, which is why the layout falls apart when zoomed.

    Keyboard navigation and other non-visual access -- like my braille reader -- is utterly banjaxed. I'm seeing the telltales of some form of presentational classes, which likely means some sort of derpy "framework" garbage. Without even looking at the code I can tell that the markup is non-semantic trash.

    Which a "view source" rapidly confirms because it's the typical halfwit TRAIN WRECK of nube predating scam artist TRASH that is Turdpress. Hence the static style in the markup, fairy tale made up attributes all over the place, opengraph trash that does nothing of value, dozens of separate files doing one or two file's job, static scripting in the markup, blocking scripting in the markup, and once you get to the BODY an utter and complete lack of anything remotely resembling semantic markup.

    A situation only compounded by the use of presentational classes for whatever the blazes was used to build the template. If you don't know what's wrong with:

    
    <body class="home page-template page-template-rbc-frontend page-template-rbc-frontend-php page-id-759 wp-custom-logo wp-embed-responsive theme-pixwell woocommerce-no-js hfeed none-nb sticky-nav smart-sticky is-tooltips is-backtop block-header-dot w-header-1 cat-icon-radius is-parallax-feat is-fmask mh-p-excerpt"><div id="site" class="site"><aside id="off-canvas-section" class="off-canvas-wrap dark-style is-hidden"><div class="close-panel-wrap tooltips-n">
    <a href="#" id="off-canvas-close-btn" title="Close Panel"><i class="btn-close"></i></a></div><div class="off-canvas-holder"><div class="off-canvas-header is-light-text"><div class="header-inner">
    <a href="https://contohdesain.my.id/" class="off-canvas-logo">
    <img data-lazyloaded="1" src="data:image/gif;base64,R0lGODdhAQABAPAAAMPDwwAAACwAAAAAAQABAAACAkQBADs=" data-src="https://contohdesain.my.id/wp-content/uploads/2020/05/logo-05-1.png" alt="Contoh Desain">
    </a><aside class="inner-bottom"><div class="off-canvas-social"></div><div class="inner-bottom-right"><aside class="bookmark-section">
    <a class="bookmark-link" href="#" title="Bookmarks">
    <span class="bookmark-icon"><i class="rbi rbi-book"></i><span class="bookmark-counter rb-counter">0</span></span>
    </a></aside></div>
    
    Code (markup):
    Just stop... stop even TRYING to make a website.

    Hence why the site is slow as molasses in February. It's vomiting up 168k of markup to deliver 3.7k of plaintext and maybe two dozen content images, not even 16k of HTML's flipping job! Just like the ridiculously absurd 1.3 megabyes of CSS in ten files doing the job of 48k or less in one file, and the outright batshit INSANE 3.6 megabytes of scripttardery spread out over 118 separate files on a site where to be frank, I probably wouldn't even have 4k of JS in one file (not counting advertising).

    It is basically wasting 5.8 megabytes of code spread out over 180 separate files, to do the job of 72k or less (1/80th the code) in THREE files. In handshaking ALONE on a "real world" connection the file count is 36 seconds!

    If someone brought this to me as a client, I'd tell them to junk it and start over from scratch. There is little of value from an accessibility or coding perspective to be saved from it. It's a bloated, slow, poorly coded money pit that flips the bird at accessibility minimums.
     
    deathshadow, Feb 26, 2021 IP