Member Avatar for JoelBox
JoelBox 0 Newbie Poster

Hi, I have a puzzle that is difficult to fix,
My website running drupal on wamp is running fine with Firefox and safari. But IE performance is bad. The symptom, IE performs the first couple of gets, then delays 5 seconds and then the next couple. The total page takes nearly a minute. But in firefox its only 10 -20 seconds.

I suspect something in the generated code, however I have it on every page of the site.

This is from the performance:

+ 4.565		0.007	641	852	GET	200	image/gif	
+ 10.738		0.005	0	0	GET	(Cache)	text/html

note the jump from 4.565 to 10.738 seconds, what is happening there?

I hope you can help me figure out what to change to make IE perform like Firefox.
kind regards from Groningen

  • 1 Contributor
  • 0 Replies
  • 66 Views

Dani AI

Generated

Note for : the pattern you describe — bursts of fast requests separated by roughly five‑second pauses — usually points to a blocking network step, not rendering. Common culprits are a globally included third‑party script that does synchronous polling (live chat, analytics, ad scripts), IE proxy/auto‑detect (WPAD) DNS/proxy lookups, or an IE‑only add‑on/toolbar. Any resource that forces a synchronous connect or blocks the parser will show as a gap in your profiler even though Firefox/Safari behave differently.

Practical diagnostic steps and quick fixes:

  • Reproduce with add‑ons disabled (start IE without add‑ons) to rule out toolbars.
  • Capture a network trace (Fiddler/Wireshark or IE’s network tools) and inspect where the time is spent: DNS/Connect vs. Wait/Receive. That tells whether it is name resolution/proxy or a slow server response.
  • Temporarily disable global modules (chat/livehelp, analytics) on a test page. If the gap disappears, convert the widget to non‑blocking loading (inject after onload or use async/defer patterns) or move it to the page bottom.
  • Check Internet Options → Connections → LAN settings: if “Automatically detect settings” is on, try turning it off (or add external domains to proxy bypass) — WPAD can introduce ~5s delays per new host.
  • If the issue is per‑host connection queuing, reduce cross‑domain resources, combine files, and add proper caching/keep‑alive.

These steps will pinpoint whether the delay is network/proxy related or a blocking script so the fix can be targeted.

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.