35.8 sec in total
12 ms
21.7 sec
14.1 sec
Welcome to fencer.wordpress.com homepage info - get ready to check Fencer Wordpress best content for United States right away, or after learning these important things about fencer.wordpress.com
It's about Emerson, fencing, painting, writing, absurdities, aikido, politics, spirit, rock 'n' roll, Thoreau, science fiction, beauty... and getting down with my bad side
Visit fencer.wordpress.comWe analyzed Fencer.wordpress.com page load time and found that the first response time was 12 ms and then it took 35.8 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
fencer.wordpress.com performance score
name
value
score
weighting
Value2.5 s
67/100
10%
Value3.5 s
64/100
25%
Value4.7 s
70/100
10%
Value4,250 ms
1/100
30%
Value0.084
93/100
15%
Value17.0 s
4/100
10%
12 ms
232 ms
94 ms
159 ms
102 ms
Our browser made a total of 217 requests to load all elements on the main page. We found that 1% of them (2 requests) were addressed to the original Fencer.wordpress.com, 11% (23 requests) were made to S.pubmine.com and 9% (19 requests) were made to Usersync.gumgum.com. The less responsive or slowest element that took the longest time to load (20.5 sec) relates to the external source Ssl-market-east.smrtb.com.
Page size can be reduced by 116.9 kB (12%)
986.6 kB
869.7 kB
In fact, the total size of Fencer.wordpress.com main page is 986.6 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 55% of websites need less resources to load. Images take 740.2 kB which makes up the majority of the site volume.
Potential reduce by 106.6 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 106.6 kB or 71% of the original size.
Potential reduce by 1.2 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. Fencer Wordpress images are well optimized though.
Potential reduce by 9.0 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. This website has mostly compressed JavaScripts.
Potential reduce by 202 B
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. Fencer.wordpress.com has all CSS files already compressed.
Number of requests can be reduced by 144 (77%)
186
42
The browser has sent 186 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fencer 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 12 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
fencer.wordpress.com
12 ms
fencer.wordpress.com
232 ms
wp-emoji-release.min.js
94 ms
159 ms
102 ms
global.css
101 ms
110 ms
style.css
105 ms
gprofiles.js
102 ms
wpgroho.js
105 ms
103 ms
tiled-gallery.css
103 ms
107 ms
w.js
105 ms
global-print.css
5 ms
conf
147 ms
ga.js
165 ms
cropped-114_1460.jpg
196 ms
wpcom-gray-white.png
87 ms
obsidian.jpg
114 ms
walking_dead_poster-296458221.jpg
243 ms
ensouling-language.jpg
359 ms
stephen-harrod-buhner-thumb.jpg
247 ms
winged-life-1.jpg
248 ms
thoreau.jpg
248 ms
walden_pond_2010.jpg
362 ms
sapphirebg.jpg
37 ms
sapphirebody.jpg
37 ms
sapphirefooter.jpg
38 ms
g.gif
111 ms
hovercard.min.css
13 ms
services.min.css
47 ms
92 ms
g.gif
81 ms
g.gif
81 ms
ata.js
43 ms
__utm.gif
133 ms
5.js
81 ms
pixel
78 ms
tag.js
184 ms
uc.html
377 ms
user_sync.html
447 ms
user_sync.html
437 ms
prbds2s
493 ms
async_usersync.html
494 ms
user_sync.html
445 ms
usync.html
622 ms
checksync.php
620 ms
iframe
422 ms
3.js
253 ms
jslog
198 ms
prebid
729 ms
bidRequest
543 ms
30907
626 ms
setuid
569 ms
all
20494 ms
match
454 ms
sync
220 ms
match
127 ms
match
321 ms
PugMaster
639 ms
match
313 ms
usermatch
256 ms
URnmbSKM
661 ms
user_sync.html
240 ms
match
403 ms
usersync.aspx
714 ms
1066 ms
match
251 ms
pd
233 ms
usync.js
234 ms
match
266 ms
match
359 ms
match
352 ms
match
353 ms
0.gif
881 ms
cksync.php
236 ms
1010 ms
match
370 ms
engine
900 ms
cksync.php
473 ms
match
302 ms
33f0689f-42a2-e3e6-f627-0c9481a26b97
504 ms
ny75r2x0
669 ms
match
260 ms
cksync.php
657 ms
match
418 ms
getuid
725 ms
us.gif
204 ms
usersync
1044 ms
demconf.jpg
346 ms
us.gif
345 ms
us.gif
412 ms
us.gif
581 ms
usersync
920 ms
us.gif
555 ms
pixel
640 ms
usersync
848 ms
usersync
923 ms
cksync.html
592 ms
b9pj45k4
692 ms
match
287 ms
49E514F3-6FE0-4353-9D92-BB12AB80E20B
575 ms
us.gif
572 ms
us.gif
572 ms
usersync
945 ms
usersync
930 ms
usersync
957 ms
pixel
711 ms
usync.html
530 ms
cksync.php
536 ms
usersync
930 ms
usync.html
760 ms
us.gif
604 ms
pixel
690 ms
jslog
419 ms
usersync
769 ms
1000.gif
467 ms
info2
467 ms
rum
404 ms
us.gif
397 ms
tap.php
391 ms
crum
608 ms
crum
738 ms
tap.php
538 ms
rtset
338 ms
usg.gif
262 ms
Pug
758 ms
dcm
449 ms
match
278 ms
usersync
626 ms
usersync
611 ms
user_sync.html
337 ms
Pug
706 ms
cksync
528 ms
usersync
550 ms
Pug
530 ms
rum
426 ms
Pug
567 ms
dcm
268 ms
usersync
441 ms
cksync.php
263 ms
usermatchredir
231 ms
Pug
485 ms
cksync
385 ms
cksync.php
231 ms
sd
212 ms
usync.html
235 ms
pixel
226 ms
crum
210 ms
match
212 ms
cksync.php
258 ms
crum
253 ms
pixel
180 ms
Pug
350 ms
sd
182 ms
usersync
180 ms
usersync
204 ms
usersync
268 ms
match
137 ms
177 ms
match
145 ms
match
176 ms
175 ms
tap.php
185 ms
match
257 ms
usersync
155 ms
match
230 ms
match
236 ms
cksync.php
186 ms
cksync.php
141 ms
ecm3
117 ms
match
175 ms
usersync
78 ms
match
24 ms
cksync.php
129 ms
cksync.php
132 ms
match
26 ms
match
16 ms
ecm3
104 ms
sync
65 ms
PugMaster
65 ms
PugMaster
25 ms
p.gif
131 ms
info
59 ms
g.pixel
48 ms
generic
49 ms
usersync.aspx
57 ms
match
85 ms
Pug
86 ms
Pug
76 ms
Pug
68 ms
Pug
66 ms
Pug
66 ms
PugMaster
52 ms
p.gif
77 ms
Pug
21 ms
Pug
30 ms
sn.ashx
225 ms
pubmatic
133 ms
i.match
202 ms
usersync
48 ms
Pug
42 ms
Artemis
142 ms
Pug
58 ms
Pug
52 ms
qmap
80 ms
pbmtc.gif
24 ms
receive
32 ms
pixel
31 ms
Pug
29 ms
Pug
18 ms
Pug
9 ms
i.match
206 ms
Pug
9 ms
sn.ashx
40 ms
725X1342.skimlinks.js
38 ms
fencer.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.
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
ARIA IDs are not unique
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
Links do not have a discernible name
fencer.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
fencer.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
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 Fencer.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 Fencer.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.
fencer.wordpress.com
Open Graph data is detected on the main page of Fencer Wordpress. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: