Member Avatar for perfwill

My site uses a CMS called UcenterHome.
It's performance are very bad on firefox (3.6), it lags very terribly whenever I type some text, and, it takes up a lot of memory. I think it's not because of firefox, because other sites are still working very well. I can't find out why.
Can you give me any clue? What can make a site lag like that?
Here is my site: http://banbetot.com.

Thanks in advance,
perfwill

  • 3 Contributors
  • 4 Replies
  • 82 Views
  • 6 Days Discussion Span
  • Latest Post Latest Post by Kraai

Dani AI

Generated

: the symptom you described (heavy memory use and visible lag while typing in Firefox) usually points to client-side activity that blocks the main thread — JavaScript handlers, synchronous AJAX, or repeated DOM/layout work — but it can also come from extensions, plugins, or server delays. and were right to check front-end assets; below are focused, practical checks and fixes to isolate and resolve the problem.

  1. Isolate the cause
  1. Common client-side culprits and quick fixes
  • Event handlers firing on every keystroke (live keypress handlers, autosave, live validation). Debounce expensive work so it runs after typing stops. Example debounce pattern:
function debounce(fn, wait) {
  let t;
  return function(...args) {
    clearTimeout(t);
    t = setTimeout(() => fn.apply(this, args), wait);
  };
}

input.addEventListener('input', debounce(function(e) {
  // expensive work (AJAX, DOM updates)
}, 250));
  • Synchronous XHR on key events blocks the UI. Make calls asynchronous and debounce them.
  • Frequent DOM writes that trigger layout thrash. Batch updates, use requestAnimationFrame, and avoid querying layout properties inside loops.
  1. Server/CMS side checks
  • Disable nonessential CMS plugins/modules one at a time to find problematic extensions.
  • Confirm pages generate quickly (Network waterfall). If server-side PHP is slow, profile with Xdebug or an APM: https://xdebug.org/docs/profiler
  • Enable opcode caching (OPcache) and browser caching for static assets.

Start with a short profiler capture while you type. The profile will point to the offending JS functions or layout operations to target first.

Recommended Answers

All 4 Replies

Member Avatar for SgtMe

Probably the main thing would be the large picture in the background and the music player. I would get rid of the music player altogether on this page, as its just a log-in page. Maybe have a smaller image and a dark-ish coloured pattern for the background...maybe something using black and grey?

Member Avatar for Kraai

Like the poster above me said, that background image is the main problem, it takes long to load.

Member Avatar for perfwill

But it works pretty well on Google Chrome, anyone can give me a clue why?

Member Avatar for Kraai

Ït is a bit faster in Chrome, I agree, but you should remember that the majority of website surfers uses IE, and IE is slower than Fire Fox.

I went back to your site today, and found that the background image is actualy hosted by a third party. The URL to your background is here:

This cannot be good for your site, what if this 3rd party host goes down, or have trouble with their server? Your site also now have to connect to that image on a different server each time to load.

I reccoment you download that image from this 3rd party server, and upload it to the same server your site is hosted on, and change the path to the image to the new location. This may help it to load faster.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.