Hello I am creatin a new wordpress website for my client. It is: http://kaliammanagencies.com/ Can give me your professional advices? Thanks.
reports 500 error right now... though if it's turdpress it is VERY unlikely I'd have kind words review-wise given the steaming pile of manure tp vomits up and has the giant brass monkey balls to call markup. PARTICULARLY now that skinners have hopped on the HTML 5 idiot wagon setting coding practices back to the worst of the late 1990's.
Hello I deleted malware attacts. Do you get any malware attention now? I dont get any one. You can review now.
It's ok in chrome given this is a wordpress site why, oh why, is the stylesheet in the page and not in a separate file? who created the theme? I'm guessing they're totally inexperienced!
The attempt at a fully fluid layout is just plain broken at every width I'm testing here, with most everything looking more like rendering errors than intentional design. The inaccessible fixed (px) metric fonts, multiple points of illegible color contrasts, and complete gibberish/nonsensical use of numbered headings make it a /FAIL/ at web design from an accessibility standpoint. Much of what the layout attempts to do, in particular the "gee ain't it neat" scripttard nonsense has no business on a website in the first place, and on the whole contributes to why it's just plain broken and inaccessible. Even the site logo randomly jumping around position is just garbage. Under the hood it's just another laundry list of how not to build a website. What with the absolute re-re bandwidth wasting comments (like "open HTML" right before <html>), HTML 5 garbage (not a fan), dozens of stylesheets just to make 100% sure it takes forever to load (with incomplete media stacks), endless pointless jquery bloat, STATIC STYLE INLINED IN THE MARKUP, and that's before we even get to BODY, where we can see the usual turdpress manure of endless pointless DIV for nothing, classes for nothing, id's for nothing, invalid/broken headings, nothing remotely resembling semantic markup, again the gibberish use of numbered headings, SPAN with classes instead of tags with meaning on obvious content, comment placements (YES, COMMENTS) that could be tripping rendering bugs, static scripting in the markup... I could go on for quite a while. It is then hardly a shock it's a massive and completely ridiculous 116k of markup to deliver 1.6k of plaintext and a dozen content images -- easily TEN TIMES as much code as neccessary. You figure that into the absurdly massive 1.35 MEGABYTES which only a THIRD OF is the images, in an even more absurd 85 files leading to the half-minute plus page-load I'm seeing here... since each file has a time penalty regardless of connection speed that can run anywhere from 50ms to 1 second. (real world guesstimate is usually 200ms). In other words, entirely what I've come to expect from a bunch of off the shelf scripts slapped together any old way, and trying to turn turpress into something it isn't. As I tell a great many people, throw it out and start over. There is little if anything I'd try to salvage from that mess.