I have a macbook pro 2011, and it's running way too slow, the fan runs high and it warms up while normal web browsing. Can someone please tell me what I can do to fix it ?

Question

Here is my activity monitor
1594
Activity Monitor
hajtum
4.5
2
18.2 MB
Intel (64 bit)
382
Adobe Reader
hajtum
0.4
13
14.3 MB
Intel
275
AppleSpell.service
hajtum
0.0
2
9.5 MB
Intel (64 bit)
173
Belkin Router Helper
hajtum
0.0
2
1,004 KB
Intel
183
Belkin Router Monitor
hajtum
0.0
5
9.0 MB
Intel
200
com.apple.dock.extra
hajtum
0.0
2
8.1 MB
Intel (64 bit)
1599
CVMCompiler
hajtum
0.0
1
19.7 MB
Intel (64 bit)
731
DashboardClient
hajtum
0.0
9
15.6 MB
Intel (64 bit)
239
dbfseventsd
hajtum
0.0
1
136 KB
Intel
134
distnoted
hajtum
0.9
9
4.0 MB
Intel (64 bit)
150
Dock
hajtum
0.0
3
9.8 MB
Intel (64 bit)
182
Dropbox
hajtum
0.1
30
35.1 MB
Intel
153
Finder
hajtum
0.0
5
70.1 MB
Intel (64 bit)
159
fontd
hajtum
0.0
2
5.4 MB
Intel (64 bit)
248
Google Chrome
hajtum
0.9
37
183.7 MB
Intel
279
Google Chrome Helper
hajtum
0.0
5
106.3 MB
Intel
1286
Google Chrome Renderer
hajtum
0.0
10
50.1 MB
Intel
1533
Google Chrome Renderer
hajtum
0.1
10
53.5 MB
Intel
1186
Google Chrome Renderer
hajtum
0.0
10
58.5 MB
Intel
443
Google Chrome Renderer
hajtum
0.0
10
29.0 MB
Intel
259
Google Chrome Renderer
hajtum
0.3
10
857.5 MB
Intel
1566
Google Chrome Renderer
hajtum
0.1
11
74.9 MB
Intel
267
Google Chrome Renderer
hajtum
0.9
17
265.4 MB
Intel
1588
Google Chrome Renderer
hajtum
0.0
10
74.3 MB
Intel
254
Google Chrome Worker
hajtum
0.0
11
26.9 MB
Intel
1149
Google Chrome Worker
hajtum
0.0
10
69.9 MB
Intel
257
Google Chrome Worker
hajtum
0.0
10
16.4 MB
Intel
253
Google Chrome Worker
hajtum
0.0
10
19.6 MB
Intel
256
Google Chrome Worker
hajtum
0.0
10
22.1 MB
Intel
268
Google Talk Plugin (Chrome Plug-In Host)
hajtum
0.0
5
7.5 MB
Intel
269
GoogleTalkPlugin
hajtum
0.1
11
23.5 MB
Intel
181
GrowlHelperApp
hajtum
0.0
5
12.5 MB
Intel (64 bit)
176
HSMMonitor
hajtum
0.0
3
5.8 MB
Intel (64 bit)
245
Image Capture Extension
hajtum
0.0
2
5.8 MB
Intel (64 bit)
167
imagent
hajtum
0.0
4
3.0 MB
Intel (64 bit)
126
launchd
hajtum
0.0
2
1.1 MB
Intel (64 bit)
39
loginwindow
hajtum
0.0
3
27.9 MB
Intel (64 bit)
918
lsboxd
hajtum
0.0
2
1.6 MB
Intel (64 bit)
165
mdmclient
hajtum
0.0
2
4.1 MB
Intel (64 bit)
130
mdworker
hajtum
0.0
4
14.7 MB
Intel (64 bit)
149
pboard
hajtum
0.0
1
288 KB
Intel (64 bit)
191
Router Manager
hajtum
0.0
5
3.6 MB
Intel
261
Shockwave Flash (Chrome Plug-In Host)
hajtum
11.9
18
217.3 MB
Intel
175
SpotifyWebHelper
hajtum
0.0
3
1.3 MB
Intel
152
SystemUIServer
hajtum
0.0
2
14.9 MB
Intel (64 bit)
151
talagent
hajtum
0.0
2
4.9 MB
Intel (64 bit)
144
UserEventAgent
hajtum
0.0
3
6.6 MB
Intel (64 bit)
161
warmd_agent
hajtum
0.0
2
396 KB
Intel (64 bit)

Answer 1

There is excessive swapping of data between physical memory and virtual memory.
That can happen for two reasons:
You have a long-running process with a memory leak (i.e., a bug), or
You don't have enough memory installed for your usage pattern.
Tracking down a memory leak can be difficult, and it may come down to a process of elimination.
In the Activity Monitor application, select All Processes from the menu in the toolbar, if not already selected. Click the heading of the  Real Mem column in the process table twice to sort the table with the highest value at the top. If you don't see that column, select
View ▹ Columns ▹ Real Memory
from the menu bar.
If one process (excluding "kernel_task") is using much more memory than all the others, that could be an indication of a leak. A better indication would be a process that continually grabs more and more real memory over time without ever releasing it. Here is an example of how it's done.
The process named "Safari Web Content" renders web pages for Safari and other applications. It uses a lot of memory and may leak if certain Safari extensions or third-party web plugins are installed. Consider it a prime suspect.
If you don't have an obvious memory leak, your options are to install more memory (if possible) or to run fewer programs simultaneously.
The next suggestion is only for users familiar with the shell. For a more precise, but potentially misleading, test, run the following command: 
sudo leaks -nocontext -nostacks process | grep total
where process is the name of a process you suspect of leaking memory. Almost every process will leak some memory; the question is how much, and especially how much the leak increases with time. I can’t be more specific. See the leaks(1) man page and the Apple developer documentation for details.