How to Boost your Internet Browsing Speed
Sometimes you might notice that your browsing speed just gone slow even though you are on high bandwidth connection.
So here is the solution to it.
To solve the issue of "my download speed is high but my browsing speed is low" try the following
g33k trick
Open Command prompt as an Administrator.
For that you need to Right click on CMD application and select "Run as Administrator" option
Now,
enter following
C:\windows\system32>netsh interface ipv4 show subinterfaces
Which results:
MTU MediaSenseState Bytes In Bytes Out Interface
------ --------------- --------- --------- -------------
4347436345 1 0 18327511 Loopback
1500 1 746930 629532 WAN OR Local Area connection
Check the "Interface" column has WAN or Local Area Connection
Now ping the google.com server with below command
C:\windows\system32>ping www.google.com -f -l 1500
Which results:
Pinging www.google.com [216.58.196.100] with 1500 bytes of data:
Packet needs to be fragmented but DF set.
Packet needs to be fragmented but DF set.
Packet needs to be fragmented but DF set.
Packet needs to be fragmented but DF set.
If you are seeing above print message , that means your system is set with wrong MTU value and which needs to be optimised.
To optimize the MTU value we need to do the following exercise until we get the optimum number
Ping google with another value less that 1500.
C:\windows\system32>ping www.google.com -f -l 1472
One More time:
C:\windows\system32>ping www.google.com -f -l 1460
Pinging www.google.com [216.58.220.36] with 1460 bytes of data:
Reply from 216.58.220.36: bytes=64 (sent 1460) time=60ms TTL=52
Reply from 216.58.220.36: bytes=64 (sent 1460) time=63ms TTL=52
Reply from 216.58.220.36: bytes=64 (sent 1460) time=58ms TTL=52
Reply from 216.58.220.36: bytes=64 (sent 1460) time=101ms TTL=52
Here you can notice the Time taken for packets for 1460 is 60ms and for 1472 it was 133
We can do more iterations to get the less time taken number.
For me MTU 1465 was giving good result.
C:\windows\system32>ping www.google.com -f -l 1465
Pinging www.google.com [216.58.220.36] with 1465 bytes of data:
Reply from 216.58.220.36: bytes=64 (sent 1465) time=59ms TTL=52
Reply from 216.58.220.36: bytes=64 (sent 1465) time=61ms TTL=52
Reply from 216.58.220.36: bytes=64 (sent 1465) time=62ms TTL=52
Reply from 216.58.220.36: bytes=64 (sent 1465) time=65ms TTL=52
Once you know the MTU optimum number, you can set it via command line with below command.
C:\windows\system32>netsh interface ipv4 set subinterface "Local Area Connection" mtu=1465 store=persistent
In case you have WAN as an interface you need to type following command.
C:\windows\system32>netsh interface ipv4 set subinterface "WAN" mtu=1465 store=persistent
Thats all!!!
Hope you will notice the speed change in browsing webpages.
To solve the issue of "my download speed is high but my browsing speed is low" try the following
g33k trick
Open Command prompt as an Administrator.
For that you need to Right click on CMD application and select "Run as Administrator" option
Now,
enter following
C:\windows\system32>netsh interface ipv4 show subinterfaces
Which results:
MTU MediaSenseState Bytes In Bytes Out Interface
------ --------------- --------- --------- -------------
4347436345 1 0 18327511 Loopback
1500 1 746930 629532 WAN OR Local Area connection
Check the "Interface" column has WAN or Local Area Connection
Now ping the google.com server with below command
C:\windows\system32>ping www.google.com -f -l 1500
Which results:
Pinging www.google.com [216.58.196.100] with 1500 bytes of data:
Packet needs to be fragmented but DF set.
Packet needs to be fragmented but DF set.
Packet needs to be fragmented but DF set.
Packet needs to be fragmented but DF set.
If you are seeing above print message , that means your system is set with wrong MTU value and which needs to be optimised.
To optimize the MTU value we need to do the following exercise until we get the optimum number
Ping google with another value less that 1500.
C:\windows\system32>ping www.google.com -f -l 1472
Which results:
Pinging www.google.com [216.58.220.36] with 1472 bytes of data:
Reply from 216.58.220.36: bytes=64 (sent 1472) time=133ms TTL=52
Reply from 216.58.220.36: bytes=64 (sent 1472) time=58ms TTL=52
Reply from 216.58.220.36: bytes=64 (sent 1472) time=67ms TTL=52
Reply from 216.58.220.36: bytes=64 (sent 1472) time=63ms TTL=52
C:\windows\system32>ping www.google.com -f -l 1460
Pinging www.google.com [216.58.220.36] with 1460 bytes of data:
Reply from 216.58.220.36: bytes=64 (sent 1460) time=60ms TTL=52
Reply from 216.58.220.36: bytes=64 (sent 1460) time=63ms TTL=52
Reply from 216.58.220.36: bytes=64 (sent 1460) time=58ms TTL=52
Reply from 216.58.220.36: bytes=64 (sent 1460) time=101ms TTL=52
Here you can notice the Time taken for packets for 1460 is 60ms and for 1472 it was 133
We can do more iterations to get the less time taken number.
For me MTU 1465 was giving good result.
C:\windows\system32>ping www.google.com -f -l 1465
Pinging www.google.com [216.58.220.36] with 1465 bytes of data:
Reply from 216.58.220.36: bytes=64 (sent 1465) time=59ms TTL=52
Reply from 216.58.220.36: bytes=64 (sent 1465) time=61ms TTL=52
Reply from 216.58.220.36: bytes=64 (sent 1465) time=62ms TTL=52
Reply from 216.58.220.36: bytes=64 (sent 1465) time=65ms TTL=52
Once you know the MTU optimum number, you can set it via command line with below command.
C:\windows\system32>netsh interface ipv4 set subinterface "Local Area Connection" mtu=1465 store=persistent
In case you have WAN as an interface you need to type following command.
C:\windows\system32>netsh interface ipv4 set subinterface "WAN" mtu=1465 store=persistent
Thats all!!!
Hope you will notice the speed change in browsing webpages.
1 comment:
This is great and just what I've been looking for. Thanks alot!!
Fair look Cream
Post a Comment