9.4 sec in total
9 ms
5.4 sec
3.9 sec
Click here to check amazing Fanatictraveller Wordpress content for United States. Otherwise, check out these important facts you probably never knew about fanatictraveller.wordpress.com
Compares hotel websites with reality and reviews off beat destinations
Visit fanatictraveller.wordpress.comWe analyzed Fanatictraveller.wordpress.com page load time and found that the first response time was 9 ms and then it took 9.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
fanatictraveller.wordpress.com performance score
name
value
score
weighting
Value3.0 s
50/100
10%
Value6.2 s
11/100
25%
Value4.7 s
68/100
10%
Value830 ms
35/100
30%
Value0.373
28/100
15%
Value16.8 s
5/100
10%
9 ms
790 ms
93 ms
123 ms
101 ms
Our browser made a total of 136 requests to load all elements on the main page. We found that 1% of them (2 requests) were addressed to the original Fanatictraveller.wordpress.com, 65% (88 requests) were made to Fanatictraveller.files.wordpress.com and 12% (16 requests) were made to S2.wp.com. The less responsive or slowest element that took the longest time to load (2 sec) relates to the external source Fanatictraveller.files.wordpress.com.
Page size can be reduced by 492.0 kB (6%)
8.4 MB
7.9 MB
In fact, the total size of Fanatictraveller.wordpress.com main page is 8.4 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 7.7 MB which makes up the majority of the site volume.
Potential reduce by 86.8 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 86.8 kB or 73% of the original size.
Potential reduce by 0 B
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. Fanatictraveller Wordpress images are well optimized though.
Potential reduce by 373.1 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 373.1 kB or 75% of the original size.
Potential reduce by 32.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. Fanatictraveller.wordpress.com needs all CSS files to be minified and compressed as it can save up to 32.1 kB or 73% of the original size.
Number of requests can be reduced by 29 (23%)
127
98
The browser has sent 127 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fanatictraveller Wordpress. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
fanatictraveller.wordpress.com
9 ms
fanatictraveller.wordpress.com
790 ms
93 ms
css
123 ms
101 ms
global.css
107 ms
106 ms
style.css
105 ms
global-print.css
108 ms
gprofiles.js
211 ms
wpgroho.js
96 ms
95 ms
jetpack-carousel.css
104 ms
tiled-gallery.css
102 ms
103 ms
widgets.js
105 ms
105 ms
725X1342.skimlinks.js
166 ms
w.js
106 ms
merriweather.css
20 ms
stripe.png
30 ms
dsc04399.jpg
486 ms
header.jpg
16 ms
search.png
17 ms
ornament.png
14 ms
smile.svg
16 ms
sad.svg
14 ms
wink.svg
17 ms
ornament-secondary.png
19 ms
map1.png
859 ms
dsc04300.jpg
485 ms
dsc04302.jpg
508 ms
img-20160216-wa0017.jpg
416 ms
dsc04340.jpg
478 ms
img-20160216-wa0008.jpg
537 ms
dsc04350.jpg
764 ms
dsc04353.jpg
781 ms
img-20160217-wa00261.jpg
596 ms
img_20151002_131318948.jpg
660 ms
img-20151002-wa0014.jpg
539 ms
img_20151002_131035157_hdr.jpg
761 ms
img_20151004_113730238_hdr.jpg
805 ms
dsc03713.jpg
922 ms
dsc03655.jpg
1014 ms
dsc03659.jpg
986 ms
dsc03672.jpg
995 ms
dsc03679.jpg
1032 ms
dsc03673.jpg
1132 ms
dsc03689.jpg
1178 ms
dsc03746.jpg
1214 ms
dsc03694.jpg
1204 ms
dsc03705.jpg
1237 ms
dsc03780.jpg
1259 ms
dsc03820.jpg
1366 ms
dsc03709.jpg
1403 ms
dsc03841.jpg
1406 ms
dsc03713.jpg
1400 ms
dsc03853.jpg
1467 ms
picture1.png
1608 ms
dsc04066.jpg
1576 ms
dsc04076.jpg
1589 ms
dsc03877.jpg
1623 ms
dsc03914.jpg
1604 ms
dsc03928.jpg
1733 ms
vDvcuXwZxUMLuTfuLrSLpA.ttf
170 ms
4GwpJM7qx9X5Obd9KsnKxQ.ttf
180 ms
zpv3sOKAbMf4wff105oLjw.ttf
210 ms
Noticons.svg
121 ms
BaABdRAi2AAAA
86 ms
merriweather-bold-webfont.ttf
114 ms
merriweather-regular-webfont.ttf
120 ms
merriweather-light-webfont.ttf
131 ms
px.gif
149 ms
148 ms
hovercard.css
119 ms
services.css
152 ms
86 ms
px.gif
83 ms
g.gif
79 ms
g.gif
75 ms
g.gif
80 ms
dsc03937.jpg
1404 ms
dsc03960.jpg
1124 ms
dsc03986.jpg
1339 ms
dsc04106.jpg
1340 ms
dsc04128.jpg
1322 ms
dsc04134.jpg
1376 ms
dsc04137.jpg
1413 ms
1.jpg
1327 ms
link
23 ms
track.php
67 ms
2.jpg
1265 ms
dsc04197.jpg
1319 ms
dsc04151.jpg
1322 ms
dsc04185.jpg
1363 ms
dsc04216.jpg
1320 ms
img_20150501_150206114.jpg
1261 ms
img_20150501_150511190.jpg
1329 ms
img_20150501_172256558_hdr.jpg
1258 ms
img_20150501_172408403_hdr.jpg
1282 ms
img_20150503_071437643.jpg
1264 ms
img_20150502_181926707_hdr.jpg
1290 ms
img_20150502_161457402_hdr.jpg
1214 ms
img_20150502_163818093.jpg
1253 ms
launch.jpg
1351 ms
img_0207-edit1.jpg
1482 ms
img_0188-edit-6.jpg
1472 ms
teaser-4.jpg
1157 ms
img_6508.jpg
1540 ms
dsc03160.jpg
1257 ms
dsc03032.jpg
1252 ms
dsc03171.jpg
1355 ms
dsc03018.jpg
1451 ms
dsc02971.jpg
1361 ms
dsc02974.jpg
1315 ms
dsc03026.jpg
1344 ms
dsc03010.jpg
1361 ms
dsc03067.jpg
1511 ms
dsc03096.jpg
1522 ms
dsc03103.jpg
1403 ms
dsc03139.jpg
1349 ms
dsc03182.jpg
1339 ms
dsc03179.jpg
1350 ms
dsc02649.jpg
1814 ms
dsc02795.jpg
1818 ms
dsc02932.jpg
1494 ms
dsc02938.jpg
1448 ms
img_4769.jpg
1671 ms
dsc02872.jpg
1312 ms
dsc02668.jpg
1823 ms
dsc02677.jpg
1771 ms
dsc02672.jpg
1861 ms
dsc02671.jpg
1961 ms
img_5534.jpg
1957 ms
dsc02807.jpg
1981 ms
botd.gif
235 ms
fanatictraveller.wordpress.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.
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
Links do not have a discernible name
fanatictraveller.wordpress.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
fanatictraveller.wordpress.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fanatictraveller.wordpress.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 Fanatictraveller.wordpress.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.
fanatictraveller.wordpress.com
Open Graph data is detected on the main page of Fanatictraveller Wordpress. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: