200 X-Frame-Options: SAMEORIGIN Content-Security-Policy: frame-ancestors 'self'; X-UA-Compatible: IE=Edge X-XSS-Protection: 1; mode=block X-Content-Type-Options: nosniff X-Telligent-Evolution: 12.x Pragma: no-cache Connection: close Accept-Ranges: bytes Cache-Control: no-store, no-cache, max-age=0 Date: Fri, 02 Jan 2026 10:09:06 GMT ETag: "0x8DE317E31FF1C26" Set-Cookie: .te.csrf=xk5DE7x49NW9L5RV2FmuVY0U42xP9lDOxq_cpHiAz-s; path=/; secure; SameSite=Lax Set-Cookie: .te.auth=_gx7hHICcKcw%2bqhMeHgo6EiuaMcRdbQs23gkYOaTrptoIPm3NVmsHJbvg4C7wb4WuRV0K%2f8PxS5L%2ffSJm7xuhd4t1t5TxwcPlbUCyGLPMkNJSFusD6CS6tk6Wx3db2zs9ufuQy6iwUbumA1Yl%2fbfvO2z4FxVcmyYHp5sxxmlsc8V1MssR7qAYms9c3%2bUakkdQxkHgzcJint3utD8HMzQhoC%2fUuugqgANSAGriJOChIXijUsIp9TVI%2fM2ZZr1ZuLYtauZvrc4472YMGzEU%2f8jGKg%3d%3d; path=/; secure; HttpOnly; SameSite=Lax Set-Cookie: e14Guest=1; expires=Fri, 31-Dec-9999 23:59:59 GMT; path=/; secure; HttpOnly Set-Cookie: e14Country=NL; expires=Fri, 31-Dec-9999 23:59:59 GMT; path=/; secure; HttpOnly Set-Cookie: e14Language=en; expires=Fri, 31-Dec-9999 23:59:59 GMT; path=/; secure; HttpOnly Set-Cookie: e14TimeZone=Etc/UTC; expires=Fri, 31-Dec-9999 23:59:59 GMT; path=/; secure; HttpOnly Server-Timing: cdn-cache; desc=MISS Server-Timing: edge; dur=33 Server-Timing: origin; dur=47 Server-Timing: ak_p; desc="1767348546515_34604952_332773909_7919_5559_4_14_-";dur=1 Strict-Transport-Security: max-age=86400 ; includeSubDomains ; preload #set ($UserId = $core_v2_user.Accessing.Id) #set ($Roles = $core_v2_utility.MakeList('Moderators', 'Almost Admins', 'Administrators')) #set ($IsAdminLike = $e14_utils.IsUserInRoleOrAdmin($UserId, $Roles)) #if($IsAdminLike == 'False') #end
Actions
Forum Thread Details
  • Locked Locked
  • Replies 72 replies
  • Subscribers 28 subscribers
  • Views 2730 views
  • Users 0 members are here
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Page changes painfully slow on Farnell website

rachaelp

When trying to navigate between pages (the ones that work) on Farnell element14 UK - Electronic Components Distributor  it often take 10 seconds or more for the next page to load when clicking on a link. This makes navigating around to find products exceedingly tedious and will definitely be putting people off purchasing from Farnell. UX studies show that a lot of people will go elsewhere if pages take more than a couple of seconds to load. Here is a link I found on this topic https://velocitize.com/2017/03/27/how-site-speed-impacts-your-seo-and-ux/ and a quick search on Google will find a lot of results for pages showing similar statistics so at 10+ seconds I think there is significant cause for concern.

 

The problem isn't my internet connection, computer, or browser, it's definitely a problem with the Farnell website.

 

Best Regards,


Rachael

Top Replies

Parents

  • Hi everyone,

     

    Those of you who have recently posted that you're not seeing an improvement - , , Stillwaiting, PaulD, Jarl Einar Ottesad - our web technical team would really like to work with any of you directly that are willing to try to pinpoint what is causing the issue. We know the site isn't perfect, and work continues to improve it, but there are so many variables that can affect the site load times that it will be most helpful if we can troubleshoot directly with a few of you to find out if there is either a common issue or other things we may not even be aware of yet that need to be addressed.

     

    Please feel free to message me directly, and I will put you in contact with our IT team.

     

    Sincerely,

    Christy

  • in reply to ChristyZ

    Christy, the problem here is the amount of off-site scripts that have to be enabled to make the web pages load in a reasonable time. NoScript lists the following: bing.com, demdex.net, baynote.net, hs-analytics, hs-scripts.com, omtrdc.net, criteo.net, marinism.net, google-analytics.com, googleadservices.com and facebook.net.

     

    None of those are appropriate for a professional electronics supplier's site IMO. I used to be able to use the site just by temporarily enabling scripts from farnell.com, but not since I updated my version of Firefox to 52 ESR (running on OpenBSD 6.2) along with the current version of NoScript around a month ago.

     

    To re-iterate, scripts from the company I'm doing business with are ok, but I don't want other companies involved in what should be a private transaction. Allow these scripts for those who want them by all means, but choosing not to load them should not prevent a customer from being able to submit an order. No other supplier I deal with imposes this restriction.

     

    BTW, I tried sending  you a message but the message form required me to allow Facebook, which I don't use.

  • in reply to johnr2

    Thanks John. I will pass your feedback to the pertinent people at Farnell. I personally use Privacy Badger or something similar to block a lot of these kinds of retargeting/3rd party scripts, but I also know that it is now fairly standard for marketing teams to use them - and the Facebook one for instance is due to the fact that we have/use Facebook in support of all of our Transactional sites AND the Community and linking various promotions together between them. I completely understand not wanting to have those fire for you though, and the site should definitely not become unresponsive if you choose to disable them.

     

     

    Also, thanks Dean Wilson. I will reply to your message. I've been out ill for a few days so apologies for the late reply.

     

    Christy - Director of Development, element14

  • in reply to johnr2

    Hi John,

     

    After passing your feedback to our IT team, we've done some testing here on our end, using No-Script version 10.1.6.3 in FF 57.0 64-bit, and we weren't able to replicate the site having any issues - either anything breaking or it adversely impacting the speed. The features that some of those scripts are used for weren't in evidence, as you'd expect. For example, Baynote is used to provide customer also-bought and similar kinds of recommendations. But otherwise, the pages seemed to load ok and we were able to complete the core site functionality that you'd expect - including adding a product to the car and checking out. We tried this on both Windows and Mac machines.

     

    image

     

    I've got a copy of the NoScript settings we used I'd be happy to send to you if you'd like. Since you can't message me here (you mentioned it was requiring Facebook - which I'll also have the team investigate), please feel free to email me at czurkawicz@newark.com if you'd like me to send them to you, or continue this discussion offline.

     

    I very much want to try to get to the bottom of these issues and find out if there is something we need to change on the site, or if it's some issue with specific browsers/settings, etc. so that we can provide some help information to other members who are likely to be having similar issues.

     

    Thanks,

    Christy - Director of Development, element14

Reply
  • in reply to johnr2

    Hi John,

     

    After passing your feedback to our IT team, we've done some testing here on our end, using No-Script version 10.1.6.3 in FF 57.0 64-bit, and we weren't able to replicate the site having any issues - either anything breaking or it adversely impacting the speed. The features that some of those scripts are used for weren't in evidence, as you'd expect. For example, Baynote is used to provide customer also-bought and similar kinds of recommendations. But otherwise, the pages seemed to load ok and we were able to complete the core site functionality that you'd expect - including adding a product to the car and checking out. We tried this on both Windows and Mac machines.

     

    image

     

    I've got a copy of the NoScript settings we used I'd be happy to send to you if you'd like. Since you can't message me here (you mentioned it was requiring Facebook - which I'll also have the team investigate), please feel free to email me at czurkawicz@newark.com if you'd like me to send them to you, or continue this discussion offline.

     

    I very much want to try to get to the bottom of these issues and find out if there is something we need to change on the site, or if it's some issue with specific browsers/settings, etc. so that we can provide some help information to other members who are likely to be having similar issues.

     

    Thanks,

    Christy - Director of Development, element14

Children
  • in reply to ChristyZ

    Christy, thanks for the reply.

     

    I can get the farnell.com site to work properly if I set NoScript to allow scripts globally, then restart Firefox. It continues to work if I then set all scripts individually to 'Untrusted' apart from the ones from farnell.com.  I can use this as a workaround.

     

    If I set NoScript to forbid all scripts globally, then temporarily allow farnell.com, I just get a blank white page that hangs indefinitely.

     

    I tried installing Firefox 56 (the latest version available for OpenBSD 6.2) but the behaviour remained the same.

     

    Interestingly, if I use the Dillo browser which doesn't support HTML5 or JavaScript, I can navigate the site quite efficiently including using the search engine (but the shopping basket doesn't work, presumably because it needs JavaScript).

     

    I'll stick with the aforementioned workaround for now. Thanks for looking into this.

  • in reply to johnr2

    Further info: whitelisting farnell.com in NoScript settings also works properly (without enabling scripts globally).

     

    Whitelisting obviously does something different from temporarily allowing sites, which surprised me.

  • in reply to ChristyZ

    I have noticed that Firefox stops loading the farnell country websites after a few hours, I just get a long timeout and 'connection was reset' message. It has only been happening for the last few days.

    I am using latest version of Firefox under Windows 10, no adblockers or any other addons, cache cleared and still it happens.

    Using another computer, or even a virtual machine does not have a problem, so not a hardware issue.

     

    My view after many years in software engineering is keep things simple, don't change stuff just because you have engineers with free time (apparently a big time Microsoft strategy).  The old maxim 'if it ain't broke don't fix it' absolutely applies in this case!