- This topic has 1 reply, 4 voices, and was last updated 11 years, 11 months ago by
.
-
Posts
-
-
-
-
I too ran the same check. There are a lot of errors and non-compliance issues. Looks like too many disparateĀ things were pulled from many sources and boiled into a XHTML/HTML4.01/HTML5 soup. I would suggest going through the code, cleaning up and optimizing it. prettyphoto.js is outdated too, and this can usually be a security concern or at the very least fix some bugs. Server load and speed at which the client side renders is very important. I like what YOOtheme does with their Warp framework. It takes 24 requests / 120KB and squeezes it down to 2 requests / 40KB ….same output. It also integrates lightweight CSS, HTML5 shim (for older browsers), plus a lot more. I haven’t bought any of their themes yet, but in testing them on their demo site, they are VERY fast and responsive, still not at pretty as MikMag though! š ….so, if the developers can clean up the code this would make for a really nice solution.
-
-
One more thing:
MikMag sends to many parallel requests to the Server, the number is in double digits. Can we manage the CSS and png files of the theme in a better manner?
It has been more than one Month and we are still waiting for the fixes for the new WP update. The theme is suffering because of lack of support and upgrade and this is evident with the fallen ratings on Themeforest. Are you working on it ?
-
Hi,
We are indeed working on our mikmag compatibility fixes at the moment and are trying our best to bring them to you as soon as we can, a code cleanup, as you suggested, is also on the list for our programmer in this update.
Kevin
-
- You must be logged in to reply to this topic.