16.9 sec in total
317 ms
16.3 sec
277 ms
Visit meetstheweird.com now to see the best up-to-date Meetstheweird content and also check out these interesting facts you probably never knew about meetstheweird.com
Meets The Weird: Come and explore the weird world. Investigate UFOs, ghosts and monsters as we explore Ufology, Cryptozology and the paranormal.
Visit meetstheweird.comWe analyzed Meetstheweird.com page load time and found that the first response time was 317 ms and then it took 16.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
meetstheweird.com performance score
name
value
score
weighting
Value3.1 s
47/100
10%
Value3.3 s
69/100
25%
Value3.1 s
93/100
10%
Value330 ms
75/100
30%
Value0.099
90/100
15%
Value4.0 s
88/100
10%
317 ms
98 ms
140 ms
154 ms
238 ms
Our browser made a total of 103 requests to load all elements on the main page. We found that 17% of them (18 requests) were addressed to the original Meetstheweird.com, 11% (11 requests) were made to Apis.google.com and 7% (7 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (15.1 sec) relates to the external source Octofinder.com.
Page size can be reduced by 252.8 kB (41%)
615.2 kB
362.4 kB
In fact, the total size of Meetstheweird.com main page is 615.2 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. 65% of websites need less resources to load. Javascripts take 298.3 kB which makes up the majority of the site volume.
Potential reduce by 33.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 33.6 kB or 76% of the original size.
Potential reduce by 19.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. Meetstheweird images are well optimized though.
Potential reduce by 175.5 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 175.5 kB or 59% of the original size.
Potential reduce by 24.5 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. Meetstheweird.com needs all CSS files to be minified and compressed as it can save up to 24.5 kB or 82% of the original size.
Number of requests can be reduced by 61 (62%)
98
37
The browser has sent 98 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Meetstheweird. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 33 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
www.meetstheweird.com
317 ms
style.css
98 ms
sharing.css
140 ms
wpp.css
154 ms
jquery.js
238 ms
tw-sack.js
162 ms
show_ads.js
14 ms
widgets.js
13 ms
getnetworkwidget
79 ms
gprofiles.js
63 ms
wpgroho.js
156 ms
sharing.js
176 ms
plusone.js
101 ms
e-201611.js
8 ms
e-201611.js
26 ms
bg3.png
171 ms
ca-pub-1075356486827884.js
163 ms
zrt_lookup.html
125 ms
show_ads_impl.js
70 ms
HeaderBG.png
144 ms
TitleGFX.png
145 ms
RssTopBarBtn.png
146 ms
twitterTopBarBtn.png
140 ms
SidebarBG.png
140 ms
ghosthunters-1.gif
264 ms
votepicture.art
353 ms
logo_small.png
93 ms
ads
195 ms
271 ms
tweet_button.html
55 ms
269 ms
tweet_button.html
58 ms
265 ms
tweet_button.html
68 ms
www.blogratedirectory.com
166 ms
blogcatalog5.gif
161 ms
octofinderok.png
15085 ms
bloglistings_button.gif
256 ms
v_28063.gif
1228 ms
paranormal-3.gif
330 ms
alien-2.gif
254 ms
osd.js
153 ms
Earthrise_cutout.jpg
490 ms
LithoArtKepler2-br.jpg
169 ms
facebook.png
161 ms
bigfoot-ornament.jpg
165 ms
jot
247 ms
jot
239 ms
jot
223 ms
cb=gapi.loaded_0
206 ms
cb=gapi.loaded_1
194 ms
fastbutton
264 ms
fastbutton
252 ms
fastbutton
253 ms
g.gif
84 ms
ga.js
77 ms
ads
318 ms
blogcatalog5.gif
336 ms
abg.js
198 ms
__utm.gif
63 ms
hovercard.css
67 ms
services.css
132 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
137 ms
ads
331 ms
badge_su.js
191 ms
badges_su.css
192 ms
rank-77.gif
182 ms
postmessageRelay
140 ms
rs=AGLTcCMmxxv5a__MjyaVcD74l1XyH_kiOQ
44 ms
cb=gapi.loaded_0
75 ms
cb=gapi.loaded_1
71 ms
grlryt2bdKIyfMSOhzd1eA.woff
79 ms
follow_button.b9740740e0bcf9b0657c5b11bd4388da.en.html
49 ms
badgeRect74x18.png
106 ms
0_zVU9U9ia.jpg
228 ms
a.gif
115 ms
bcs0
181 ms
creative_add_on.js
245 ms
3193398744-postmessagerelay.js
160 ms
rpc:shindig_random.js
108 ms
14335356835040511619
49 ms
s
43 ms
m_js_controller.js
50 ms
x_button_blue2.png
92 ms
googlelogo_color_112x36dp.png
85 ms
jot
42 ms
cb=gapi.loaded_0
21 ms
fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js
10 ms
surly.js
136 ms
dvtp_src.js
141 ms
ba.html
29 ms
4.gif
136 ms
dvtp_src_internal26.js
37 ms
2532.js
125 ms
t2tv7.html
208 ms
visit.js
57 ms
avs5639.js
33 ms
cfbc.htm
72 ms
event.jpg
68 ms
box_19_top-right.png
38 ms
ci.png
44 ms
activeview
28 ms
activeview
12 ms
meetstheweird.com accessibility score
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
Document doesn't have a <title> element
<frame> or <iframe> elements do not have a title
meetstheweird.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
Page has valid source maps
meetstheweird.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Document doesn't have a <title> element
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
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
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Meetstheweird.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Meetstheweird.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.
meetstheweird.com
Open Graph description is not detected on the main page of Meetstheweird. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: