This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

সহায়তা খুঁজুন

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

আরও জানুন

Very slow loading website "Pubmed Central"

  • 2 উত্তরসমূহ
  • 0 এই সমস্যাটি আছে
  • 20 দেখুন
  • শেষ জবাব দ্বারা sabiaceae

more options

Pubmed Central (https://www.ncbi.nlm.nih.gov/pmc/) is a commonly used website for literature reading in life sicences research. I found that it takes a lot of time to load the PMC web page, and even worse to access an aricle in it, always more than 10 seconds (for example, https://www.ncbi.nlm.nih.gov/pmc/articles/PMC1234567/). These pages access smoothly in other browsers on my computer (MacBook Pro with M1, macOS Sonoma 14.0). I've tried the troubleshoot mode, and clearing all the cookies and cache, but it just doesn't work.

Hoping to get some useful feedback on this!

Pubmed Central (https://www.ncbi.nlm.nih.gov/pmc/) is a commonly used website for literature reading in life sicences research. I found that it takes a lot of time to load the PMC web page, and even worse to access an aricle in it, always more than 10 seconds (for example, https://www.ncbi.nlm.nih.gov/pmc/articles/PMC1234567/). These pages access smoothly in other browsers on my computer (MacBook Pro with M1, macOS Sonoma 14.0). I've tried the troubleshoot mode, and clearing all the cookies and cache, but it just doesn't work. Hoping to get some useful feedback on this!

All Replies (2)

more options

PubMed loads fast for me.

Try changing secure DNS over HTTPS (DoH) to "Off" or "Increased Protection" and in Connection Settings change "Use system proxy settings" to "No proxy".

Disable any third-party anti-virus, security software, firewall, VPN, proxy, custom DNS or web filters that may be interfering.

more options

It works when turn "network.prefetch-next" false in about:config