11.5 sec in total
1.8 sec
9.3 sec
439 ms
Click here to check amazing Phuket Marathon content for Thailand. Otherwise, check out these important facts you probably never knew about phuketmarathon.com
Welcome, the 11th Laguna Phuket International Marathon™ will take place on 4 & 5 June 2016
Visit phuketmarathon.comWe analyzed Phuketmarathon.com page load time and found that the first response time was 1.8 sec and then it took 9.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
phuketmarathon.com performance score
name
value
score
weighting
Value12.9 s
0/100
10%
Value29.3 s
0/100
25%
Value19.0 s
0/100
10%
Value1,420 ms
15/100
30%
Value0
100/100
15%
Value30.0 s
0/100
10%
1751 ms
503 ms
514 ms
515 ms
516 ms
Our browser made a total of 118 requests to load all elements on the main page. We found that 30% of them (35 requests) were addressed to the original Phuketmarathon.com, 33% (39 requests) were made to Static.xx.fbcdn.net and 13% (15 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (4 sec) belongs to the original domain Phuketmarathon.com.
Page size can be reduced by 712.1 kB (26%)
2.8 MB
2.1 MB
In fact, the total size of Phuketmarathon.com main page is 2.8 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 65% of websites need less resources to load. Images take 1.8 MB which makes up the majority of the site volume.
Potential reduce by 33.7 kB
HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 33.7 kB or 78% of the original size.
Potential reduce by 41.0 kB
Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Phuket Marathon images are well optimized though.
Potential reduce by 302.4 kB
It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 302.4 kB or 64% of the original size.
Potential reduce by 335.1 kB
CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Phuketmarathon.com needs all CSS files to be minified and compressed as it can save up to 335.1 kB or 80% of the original size.
Number of requests can be reduced by 67 (60%)
111
44
The browser has sent 111 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Phuket Marathon. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 44 to 1 for JavaScripts and from 25 to 1 for CSS and as a result speed up the page load time.
phuketmarathon.com
1751 ms
wp-emoji-release.min.js
503 ms
jquery.flexslider.css
514 ms
jquery.countdown.css
515 ms
plugins.css
516 ms
main.css
770 ms
wp.css
531 ms
theme.css
760 ms
css
24 ms
genericons.css
1021 ms
style.css
1024 ms
jetpack.css
1283 ms
jquery.js
1586 ms
jquery-migrate.min.js
1017 ms
modernizr.custom.80453.js
1024 ms
fb-sdk.js
1277 ms
phuketmarathon.com
1487 ms
devicepx-jetpack.js
5 ms
gprofiles.js
54 ms
wpgroho.js
1041 ms
jquery.countdown.min.js
1044 ms
main.js
1297 ms
plugins.js
1296 ms
jquery.flexslider-min.js
1567 ms
masonry.min.js
1568 ms
jquery.masonry.min.js
1506 ms
functions.js
1565 ms
e-201611.js
4 ms
css
13 ms
css
22 ms
droidsansthai.css
24 ms
all.js
281 ms
QQjA_PNESzI
89 ms
run-paradise-logo.png
1043 ms
language-icons.png
302 ms
sponsors-logo-hi-res.png
3960 ms
banner-image1.jpg
1451 ms
banner-image2.jpg
1200 ms
banner-image3.jpg
1203 ms
banner-image4.jpg
1093 ms
banner-image5.jpg
2801 ms
sportstats-logo.png
1358 ms
sponsors-logo.png
1965 ms
analytics.js
31 ms
APH4jr0uSos5wiut5cpjrnhCUOGz7vYGh680lGh-uXM.woff
7 ms
zhcz-_WihjSQC0oHJ9TCYBsxEYwM7FgeyaSgU71cLG0.woff
8 ms
IQHow_FEYlDC4Gzy_m8fcgFhaRv2pGgT5Kf0An0s4MM.woff
10 ms
Genericons.svg
1691 ms
8AAnjaY2BgYGQAgosrjpwF0ZcUq9bCaABTzgdAAAA=
6 ms
collect
17 ms
www-embed-player-vflfNyN_r.css
77 ms
www-embed-player.js
107 ms
fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js
78 ms
ad_status.js
95 ms
hovercard.css
56 ms
services.css
88 ms
g.gif
38 ms
2UX7WLTfW3W8TclTUvlFyQ.woff
47 ms
RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff
47 ms
142 ms
xd_arbiter.php
219 ms
xd_arbiter.php
424 ms
ping
57 ms
like_box.php
239 ms
410ucuAGgaJ.css
289 ms
tSbl8xBI27R.css
356 ms
Czh0gDTFcBt.css
425 ms
VyhHmC9SnBT.css
500 ms
Ek6lpayKeeB.css
557 ms
EoarYgA68t4.css
567 ms
5VZ003vMUZg.css
577 ms
dAhyk4_vXRy.css
494 ms
1kPfZUdGrka.js
575 ms
Yuj_Y8xNH2C.js
695 ms
Mpe38fuBVZ2.js
600 ms
n8qIhCw3vMx.js
624 ms
QKy94bWvcbp.js
626 ms
d20DxWMAn1e.js
628 ms
qcMicXoOToy.js
822 ms
57RpJa05x58.js
714 ms
7B-2ZS3Qt8r.js
754 ms
pf3FNnit_ev.js
758 ms
BmFj6FmaQGO.js
712 ms
hGrOQrzI1QD.js
762 ms
qf1RiuO5N-I.js
763 ms
6q5od22S-uf.js
763 ms
OgxH-jlaKMd.js
854 ms
vnY_jgcOCcS.js
891 ms
4ALP2bcCEZ5.js
856 ms
CqFyjqic8Gy.js
857 ms
AmlxWlqMvlv.js
902 ms
cVut-tmssw-.js
887 ms
cExDZPRI9VL.js
1024 ms
10568911_971357796242727_2525364111053763156_n.jpg
350 ms
12472263_1076908282354344_5700741443241681453_n.jpg
409 ms
12308230_126828151018711_1499919841627984468_n.jpg
480 ms
12512630_206889766322324_8414281042330762855_n.jpg
545 ms
10153164_699979860044659_8303202991930996690_n.jpg
549 ms
11742723_10207320843249033_1841551637696324204_n.jpg
546 ms
5516_10205690870132863_2600452185152672783_n.jpg
721 ms
12800285_1018416031556618_8607200164299226265_n.jpg
547 ms
12794389_1112476348797537_3409119683128677787_n.jpg
636 ms
3071_1110534648991707_7536847493767696637_n.jpg
671 ms
1463407_1106766806035158_7384273020892810679_n.jpg
680 ms
12365462_1104844976227341_1001332933_n.jpg
615 ms
12821580_1102975373080968_7534875559014552736_n.jpg
682 ms
12814146_1102975366414302_1637616652283372254_n.jpg
683 ms
12814461_1102975389747633_1988703144471947776_n.jpg
702 ms
wL6VQj7Ab77.png
109 ms
s7jcwEQH7Sx.png
110 ms
pimRBh7B6ER.png
111 ms
QDwYpIaRyfG.png
109 ms
l5aPruN9xMM.png
110 ms
K00K-UgnsKu.png
111 ms
yCfZpessXwm.js
74 ms
gxbPuQdXIZP.png
71 ms
K_65vAc89SX.png
69 ms
VXcANLwwL5J.js
69 ms
phuketmarathon.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
Image elements do not have [alt] attributes
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
phuketmarathon.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
phuketmarathon.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).
Impact
Issue
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Phuketmarathon.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Phuketmarathon.com main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.
phuketmarathon.com
Open Graph data is detected on the main page of Phuket Marathon. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: