1 Rookie
•
3 Posts
0
61
April 19th, 2025 18:27
Inspiron 14 Plus 7440 Browsers operate slowly or don't function properly
I have a very new Inspiron 14 Plus 7440. I have tried using Microsoft Edge, Chrome, and Avast Secure Browser. All these browsers operate slowly, don't load Facebook/Pinterest/YouTube well or at all. I have followed advice on this site, and from friends, everything from clearing cache, optimizing/boosting performance, and short of returning to factory settings, so many other options in between. I just don't feel I should have this issue on a NEW device. All device and browser settings have been reviewed. And support here is during my work hours. Not a very satisfied customer at this time.
No Events found!
anne_droid
3 Apprentice
•
655 Posts
0
April 21st, 2025 11:27
Hi
So
C:\>tracert bbc.co.uk
Tracing route to bbc.co.uk [151.101.192.81]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms broadband [192.168.1.1]
2 8 ms 5 ms 5 ms 84.65.192.1
3 * 10 ms 11 ms 63.130.172.35
4 10 ms 11 ms 10 ms 90.255.251.117
5 10 ms 10 ms 9 ms 151.101.192.81
Trace complete.
The 63.130.172.35 is my ISP, and for you those first few hops are vital. Probably a bottleneck.
Could you try a known location, like MS 13.107.4.52
Next ....
ipconfig -all and this is the relevant part ....
Wireless LAN adapter WiFi:
Connection-specific DNS Suffix broadband
Description . . . . . . . . . . . : Intel(R) Wi-Fi 6 AX101
Physical Address. . . . . . . . . : C8-58-B3XXXXXXXXXX
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::XXXXXXXXXXXXXXXXXX(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.41(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : 21 April 2025 12:05:22
Lease Expires . . . . . . . . . . : 28 May 2161 18:37:38
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DHCPv6 IAID
DHCPv6 Client
DUID
DNS Servers . . . . . . . . . . . : fe80::
192.168.1.1
If you could try to extract the Default gateway and DHCP server details please.
or try ipconfig /all | find /i "DHCP Server"
DHCP Server . . . . . . . . . . . : 192.168.1.1
(edited)
anne_droid
3 Apprentice
•
655 Posts
0
April 20th, 2025 13:02
Hi
I hope I am not covering ground already well trodden.....
My thoughts are to split this into parts, and try to prove the pieces before assembling a jigsaw.
So (Assuming an MS OS)...........
WinkeY +R brings up the Run, type cmd
then press CTRL + Shift + Enter and hopefully a DOS-BOX command window appears.
ping 127.0.0.1 && ping 13.107.4.52
OVER 2 & OVER 20ms is a POOR result IMO.
ping 127.0.0.1 && ping 13.107.4.52
PING 127.0.0.1 (127.0.0.1) 56(84) bytes of data.
64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.076 ms
--- 127.0.0.1 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3049ms
That is 3.049 milli-seconds for 4 pings.
PING 13.107.4.52 (13.107.4.52) 56(84) bytes of data.
64 bytes from 13.107.4.52: icmp_seq=1 ttl=117 time=15.4 ms
--- 13.107.4.52 ping statistics ---
3 packets transmitted, 3 received, 0% loss
AVERAGE 16.796 milli-seconds
The above gives a state of your underlying connection.
I am in the UK and the ping was to Microsoft, you may do better.
13.107.4.52 Redmond, Washington, United States
If you can please post your results, then further analysis can be done.
Like tracert, is there a proxy or a VPN etc etc.
SassyGee
1 Rookie
•
3 Posts
0
April 20th, 2025 18:20
Thank you for your reply.
It is MS OS - apologies I did not specify.
Performing the indicated ping, I got the following results:
Pinging 127.0.0.1 with 32 bytes of data:
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Ping statistics for 127.0.0.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
Pinging 13.107.4.52 with 32 bytes of data:
Reply from 13.107.4.52: bytes=32 time=12ms TTL=251
Reply from 13.107.4.52: bytes=32 time=11ms TTL=251
Reply from 13.107.4.52: bytes=32 time=11ms TTL=251
Reply from 13.107.4.52: bytes=32 time=11ms TTL=251
Ping statistics for 13.107.4.52:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 11ms, Maximum = 12ms, Average = 11ms
No Proxy or VPN.
Windows 11 over WiFi 5G.
anne_droid
3 Apprentice
•
655 Posts
0
April 21st, 2025 10:57
@SassyGee
Hi
I did realise that when you stated a new laptop and EDGE it was going to be W11, after I posted and engaged my brain.
Your pings are better than mine, so it is something in the W11 setup.
If I run tracert (traceroute) then I can see how many hops to the destination, and the times taken.
Next would be your Gateway and DNS setup.
So I will try and establish some simple checks to try.
SassyGee
1 Rookie
•
3 Posts
1
April 23rd, 2025 00:43
I connected with Dell support during my work hours today, and they did a lot of things to optimize performance. After doing all within their scope, the issue persisted, and they recommended I wait until the next Microsoft release is updated, and see if it fixes it, with no estimated release date.
anne_droid
3 Apprentice
•
655 Posts
0
April 23rd, 2025 09:02
Hi
I would just say that I do think it is a routing problem, and putting in an IP address was definitely quicker, which makes me consider the DHCP server(s) need tweaking.
If in doubt please come back and ask again.