Sure, first run check-fetch-times.php?show=versions to see if the scripts are up-to-date (they mostly are on your site).
Then run check-fetch-times.php itself to show timings to the usual websites.
Your results looks pretty normal except for the UV forecast fetch:
curl fetching '
http://www.temis.nl/uvradiation/nrt/uvindex.php?lon=-80.097374&lat=26.967634'
HTTP stats: RC=200 dest=145.23.254.72 port=80 (from sce=173.236.184.135)
Times: dns=2.511 conn=2.590 pxfer=2.591 get=1.070 total=
3.661 secs
Then do a view-source of view-source:https://www.joe4speed.com/wxindex.php?debug=y&force=1 and look for all the 'HTTP stats' messages to see what the load times of the support scripts are showing.
The UV forecast again reports:
HTTP stats: RC=200 dest=145.23.254.72 port=80 (from sce=173.236.184.135)
Times: dns=2.511 conn=2.590 pxfer=2.590 get=0.917 total=
3.507 secs
I do notice on the view-source, that there's a 404 for your Forecast Zone spec. FLZ068 is not found. You should use FLZ168 in your Settings.php
$SITE['NWSforecasts'] = array( // for the advforecast2.php V3.xx version script
// use "Zone|Location|Point-printableURL", as entries .. first one will be the default forecast.
"FLZ0168|Jupiter|http://forecast.weather.gov/MapClick.php?lat=26.967634&lon=-80.097374&unit=0&lg=english&FcstType=text&TextType=2",
"FLZ064|Hobe Sound|http://forecast.weather.gov/MapClick.php?lat=27.05950&lon=-80.13643230000002&unit=0&lg=english&FcstType=text&TextType=2",
);
Lastly, running the developer tools and watching the timing of the full page just shows a 28 second load.. the UV counts for maybe 3.5 seconds of that.
I'm suspecting that something inside the alternative dashboard might be causing the bulk of the delay .. look in the code for all the include()/include_once()/require()/require_once() statements.. one of them (that are not loading the usual top/header/common/menubar/footer/Settings files is your likely culprit.
Hope this helps...