char clat[10+11+1] = "Latitude: ";
dtostrf(gps.location.lat(), 11, 6, clat+10);
Since you've named the buffer 'clat' I'm assuming it will always be used for latitude, so we've pre-initialized its size and contents, and we know where to begin the latitude value.
By the way, don't forget to size string buffers one more byte than the length of the maximum length string you intend to put in it.
From your other question and your comment to this answer, I'll revise my suggestion to this. The ..printf() functions are particularly easy to use, saves you (mis)counting buffer positions, and don't add much lot more code than the Serial() object already includes:
char outbuf[40+1]; // wider than nec, easier than counting
char clat[15+1]; clong[15+1]; // workspaces
sprintf(outbuf, "Latitude/Longitude: %s %s",
dtostrf(gps.location.lat(), 10, 6, temp),
dtostrf(gps.location.lng(), 10, 6, temp) );
This works because dtostrf() returns the address of the buffer you gave it; sprintf then takes that string (two of them in this case) when building your final output string.
The printf() functions are often deprecated for embedded systems. They're large (but see my comment about that above); and they're non-reentrant, so don't do that! In these low-end systems we don't often multi-thread anyway - just be aware of that if you do. And even if you have to remove them later and go back to printing piece by piece, they can save you a lot of headaches during development.
Here's another way that avoids both printf and the 32 bytes of work buffers:
strcpy(outbuf, "Latitude/Longitude: ");
dtostrf(gps.location.lat(), 12, 6, outbuf+strlen(outbuf));
dtostrf(gps.location.lng(), 12, 6, outbuf+strlen(outbuf));
We can't initialize outbuf unless it is 1) static, and 2) not going to be used more than once, since its initial conditions won't be the same the second time around. I've increased the field-widths of dostrf() to be sure the outputs of the won't be run-together for large values.