53.6 sec in total
10.4 sec
41.8 sec
1.3 sec
Welcome to whatevertherewas.com homepage info - get ready to check Whatevertherewas best content for Malaysia right away, or after learning these important things about whatevertherewas.com
This domain may be for sale!
Visit whatevertherewas.comWe analyzed Whatevertherewas.com page load time and found that the first response time was 10.4 sec and then it took 43.1 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 were 15 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
whatevertherewas.com performance score
name
value
score
weighting
Value3.3 s
39/100
10%
Value3.6 s
62/100
25%
Value3.3 s
90/100
10%
Value330 ms
75/100
30%
Value0.298
40/100
15%
Value3.8 s
90/100
10%
10438 ms
4442 ms
774 ms
1242 ms
6271 ms
Our browser made a total of 110 requests to load all elements on the main page. We found that 38% of them (42 requests) were addressed to the original Whatevertherewas.com, 15% (17 requests) were made to Static.xx.fbcdn.net and 15% (16 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (19.9 sec) belongs to the original domain Whatevertherewas.com.
Page size can be reduced by 691.9 kB (45%)
1.5 MB
829.2 kB
In fact, the total size of Whatevertherewas.com main page is 1.5 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. 55% of websites need less resources to load. Images take 689.0 kB which makes up the majority of the site volume.
Potential reduce by 74.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 74.8 kB or 83% of the original size.
Potential reduce by 57.5 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. Whatevertherewas images are well optimized though.
Potential reduce by 267.6 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 267.6 kB or 67% of the original size.
Potential reduce by 292.0 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. Whatevertherewas.com needs all CSS files to be minified and compressed as it can save up to 292.0 kB or 85% of the original size.
Number of requests can be reduced by 45 (58%)
77
32
The browser has sent 77 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Whatevertherewas. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 32 to 1 for JavaScripts and from 15 to 1 for CSS and as a result speed up the page load time.
whatevertherewas.com
10438 ms
wp-emoji-release.min.js
4442 ms
styles.css
774 ms
wp-image-borders.css
1242 ms
style.css
6271 ms
instag-slider.css
1944 ms
jetpack.css
2961 ms
jquery.js
3373 ms
jquery-migrate.min.js
3567 ms
jquery.flexslider-min.js
3634 ms
jquery.form.min.js
1549 ms
scripts.js
668 ms
devicepx-jetpack.js
97 ms
gprofiles.js
152 ms
wpgroho.js
686 ms
libs-script.min.js
9456 ms
main.js
948 ms
post-like.js
1000 ms
wp-embed.min.js
1403 ms
e-201614.js
109 ms
css
256 ms
css
310 ms
css
358 ms
css
62 ms
analytics.js
253 ms
logo2.png
1509 ms
loading.gif
789 ms
Screen-Shot-2015-05-11-at-12.36.54-PM.png
19852 ms
mountain.png
2039 ms
IMG_4690.jpg
19851 ms
DSC00133-585x390.jpg
2451 ms
IMG_8049.jpg
19848 ms
IMG_9538.jpg
19848 ms
IMG_9550.jpg
14601 ms
WTW_SEKINCHAN_01-585x390.jpg
8738 ms
WTW_BORNEO_01-585x390.jpg
13634 ms
What-else-did-i-do-in-Iceland_-1080p.mp4.00_01_20_04.Still001-585x390.jpg
15632 ms
WTW_JAPAN_MAIKO_01-585x390.jpg
16286 ms
IMG_9601.jpg
19835 ms
IMG_9602.jpg
19836 ms
IMG_9603.jpg
19835 ms
IMG_81481.jpg
19836 ms
IMG_2799.jpg
19836 ms
06a64238_original.jpg
19835 ms
ChiangMai.jpg
19836 ms
IMG_9548.jpg
19837 ms
searchsubmit.png
19836 ms
10497022_10153017525473808_5014321371332495575_o.jpg
19836 ms
2dBELi3ZbivnVPt1KR2lhQ.woff
329 ms
lyIZFqDTaXXyAxN6-svvJg.woff
475 ms
yATwQM0pIZXIFPrEDZyOHg.woff
574 ms
mjitrc9VnL7D7tS-i3g3XQ.woff
709 ms
R5nyNcvoz7n0iBHxjY_LyQ.woff
709 ms
fontawesome-webfont.woff
19644 ms
JbtMzqLaYbbbCL9X6EvaIxsxEYwM7FgeyaSgU71cLG0.woff
708 ms
1ImRNPx4870-D9a1EBUdPBsxEYwM7FgeyaSgU71cLG0.woff
709 ms
PKCRbVvRfd5n7BTjtGiFZBsxEYwM7FgeyaSgU71cLG0.woff
709 ms
xkvoNo9fC8O2RDydKj12bxsxEYwM7FgeyaSgU71cLG0.woff
704 ms
CcKI4k9un7TZVWzRVT-T8xsxEYwM7FgeyaSgU71cLG0.woff
699 ms
IczWvq5y_Cwwv_rBjOtT0w.woff
786 ms
-_Ctzj9b56b8RgXW8FAriRsxEYwM7FgeyaSgU71cLG0.woff
785 ms
8KhZd3VQBtXTAznvKjw-kxsxEYwM7FgeyaSgU71cLG0.woff
777 ms
RJMlAoFXXQEzZoMSUteGWD8E0i7KZn-EPnyo3HZu7kw.woff
777 ms
collect
86 ms
sdk.js
597 ms
hovercard.css
265 ms
services.css
266 ms
g.gif
114 ms
454 ms
xd_arbiter.php
203 ms
xd_arbiter.php
643 ms
player_api
59 ms
fontawesome-webfont.ttf
7942 ms
www-widgetapi.js
38 ms
CAc4ffYXbco
73 ms
page.php
332 ms
ik8d09sCUBr.css
171 ms
h0O-5u1ruio.css
210 ms
S4Hdo_46O-S.css
263 ms
SRSW8M763HA.js
440 ms
3k9g4dfmgsB.js
482 ms
XokP-R2tSzH.js
392 ms
qknduWkmLL_.js
470 ms
EwhOebGmqZh.js
392 ms
UlhmM0m3TH8.js
314 ms
RFvRVBkbFtO.js
840 ms
12289749_530488360433779_6624592040048617979_n.jpg
324 ms
12226980_530485677100714_3562557610422076167_n.jpg
386 ms
184489_1692944114309485_8357047468993038792_n.jpg
442 ms
12742002_1285458808138388_5534978805467777821_n.jpg
533 ms
12360294_1727459760816592_8112283661929466390_n.jpg
491 ms
1094850_532079180175203_1873353220_n.jpg
495 ms
12524300_1011863768873894_98427273050281364_n.jpg
495 ms
11214051_10152964636451247_5280120127655080902_n.jpg
496 ms
1964798_10154119971209203_2987693740765416333_n.jpg
495 ms
1689622_10209087771530849_6977910496239879880_n.jpg
549 ms
wL6VQj7Ab77.png
188 ms
Wh-wXqXludh.png
186 ms
-N4O24bI2Vm.png
51 ms
R9GKCzjAnbk.js
72 ms
AWWjhOengNF.js
82 ms
YnSasnyq68i.js
77 ms
kQf_jlUv-kX.js
82 ms
CAc4ffYXbco
534 ms
www-embed-player-vfl5foy2V.css
176 ms
www-embed-player.js
237 ms
F5EcQNuXvzCwnROrenDy46C3KsouVqfn29hTt0MreZk.js
298 ms
ad_status.js
329 ms
2UX7WLTfW3W8TclTUvlFyQ.woff
58 ms
RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff
49 ms
whatevertherewas.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
<frame> or <iframe> elements do not have a title
whatevertherewas.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
whatevertherewas.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 Whatevertherewas.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 Whatevertherewas.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.
whatevertherewas.com
Open Graph data is detected on the main page of Whatevertherewas. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: