2.8 sec in total
138 ms
2.4 sec
301 ms
Welcome to lilliputing.com homepage info - get ready to check Lilliputing best content right away, or after learning these important things about lilliputing.com
Covering mobile tech news, tips and reviews with a focus on smartphones, tablets, notebook, and handheld computers as well as tiny desktop PCs
Visit lilliputing.comWe analyzed Lilliputing.com page load time and found that the first response time was 138 ms and then it took 2.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
lilliputing.com performance score
name
value
score
weighting
Value3.2 s
43/100
10%
Value5.5 s
19/100
25%
Value3.4 s
90/100
10%
Value810 ms
36/100
30%
Value0.787
5/100
15%
Value6.8 s
54/100
10%
138 ms
60 ms
13 ms
18 ms
34 ms
Our browser made a total of 205 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Lilliputing.com, 6% (12 requests) were made to C.betrad.com and 5% (10 requests) were made to V4.moatads.com. The less responsive or slowest element that took the longest time to load (483 ms) relates to the external source Staticxx.facebook.com.
Page size can be reduced by 1.3 MB (59%)
2.2 MB
911.6 kB
In fact, the total size of Lilliputing.com main page is 2.2 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 1.7 MB which makes up the majority of the site volume.
Potential reduce by 101.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 101.8 kB or 74% of the original size.
Potential reduce by 14.7 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. Lilliputing images are well optimized though.
Potential reduce by 1.1 MB
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 1.1 MB or 63% of the original size.
Potential reduce by 142.4 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. Lilliputing.com needs all CSS files to be minified and compressed as it can save up to 142.4 kB or 85% of the original size.
Number of requests can be reduced by 130 (65%)
199
69
The browser has sent 199 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lilliputing. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 76 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
liliputing.com
138 ms
wp-emoji-release.min.js
60 ms
style.css
13 ms
jquery.tosrus.all.css
18 ms
sfsi-style.css
34 ms
jetpack.css
30 ms
jquery.js
33 ms
jquery-migrate.min.js
19 ms
sfp.js
122 ms
liliputing.com.js
105 ms
adsbygoogle.js
6 ms
ref.js
37 ms
32X105.skimlinks.js
36 ms
zdsticky.rel.js
64 ms
jquery.tosrus.min.all.js
29 ms
front.js
29 ms
core.min.js
29 ms
modernizr.custom.min.js
30 ms
jquery.shuffle.min.js
30 ms
random-shuffle-min.js
31 ms
custom.js
29 ms
devicepx-jetpack.js
31 ms
wp-embed.min.js
30 ms
count.js
29 ms
analytics.js
257 ms
sdk.js
377 ms
texture.png
254 ms
api
231 ms
cross.png
232 ms
220 ms
plusone.js
275 ms
platform.js
380 ms
widgets.js
387 ms
count.js
247 ms
20087
110 ms
64 ms
LiliputingLogo320.png
64 ms
kit_02-200x132.jpg
62 ms
surface-3-188x150.jpg
64 ms
ringing-bells-freedom-251-77x150.jpg
63 ms
creo-mark-1-150x84.jpg
64 ms
moto-x-pure-back-150x115.jpg
64 ms
edge-extensions_02-150x84.jpg
69 ms
fairphone_03-150x83.jpg
71 ms
e403sa_02-150x76.jpg
68 ms
win10-update-92x150.jpg
71 ms
xperia-z5-compact-143x150.jpg
68 ms
samsung-galaxy-tabpro-s-150x103.jpg
71 ms
nextbit-robin_04-133x150.jpg
76 ms
flat_twitter.png
75 ms
flat_google.png
75 ms
flat_facebook.png
85 ms
flat_youtube.png
77 ms
flat_rss.png
77 ms
fairphone_03-125x69.jpg
85 ms
hand_01-125x77.jpg
84 ms
in-hand_02-125x94.jpg
83 ms
surface-3-125x100.jpg
93 ms
rss.png
94 ms
blue.png
63 ms
pop_up.png
63 ms
liliputing.com-async.js
88 ms
nsgpt.jsonp
66 ms
gpt.js
65 ms
tag.js
151 ms
ca-pub-2998039209070153.js
142 ms
zrt_lookup.html
184 ms
show_ads_impl.js
92 ms
zdvtools.min.js
177 ms
widget.php
107 ms
pubads_impl_82.js
131 ms
20214
118 ms
count-data.js
107 ms
count-data.js
204 ms
ga.js
103 ms
beacon.js
109 ms
walker-min.js
203 ms
gurgle.zdbb.net
204 ms
v60.js
199 ms
bk-coretag.js
199 ms
cb=gapi.loaded_0
98 ms
ads
169 ms
collect
147 ms
osd.js
49 ms
ads
244 ms
151 ms
__utm.gif
58 ms
container.html
42 ms
set
41 ms
xd_arbiter.php
277 ms
xd_arbiter.php
483 ms
check
75 ms
20838
32 ms
p.skimresources.com
29 ms
326 ms
adj
184 ms
beacon
67 ms
link
10 ms
track.php
12 ms
7 ms
ads
474 ms
30 ms
0
95 ms
surly.js
183 ms
index.html
218 ms
verify_selector.js
138 ms
blank.gif
161 ms
verifyr.js
37 ms
ba.html
47 ms
pixel
34 ms
4.gif
66 ms
lidar.js
32 ms
sbhK2lTE.js
66 ms
beacon.js
55 ms
0
37 ms
bg.png
45 ms
adchoices.en.png
88 ms
pixel
85 ms
pixel
57 ms
4311.js
27 ms
cTrvNaRi.html
8 ms
FaceBody_728x90_logo.gif
46 ms
FaceBody_728x90_bg.jpg
105 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
6 ms
expansion_embed.js
57 ms
jload
155 ms
moatad.js
347 ms
jload
180 ms
sfp-iframe-buster.js
71 ms
jload
184 ms
acq_fios_3x_DoublePlayEndFrame_6499_0_Static_3172016_300x250.jpg
149 ms
21929
288 ms
sbhK2lTE.js
44 ms
jload
172 ms
awa_1X_DefaultBanners10815_0_0_Static_1082015_160x600.jpg
166 ms
21929
278 ms
adj
118 ms
beacon
58 ms
ggcmb510.js
102 ms
storageframe.html
38 ms
sd
87 ms
cTrvNaRi.html
27 ms
155 ms
surly.js
150 ms
lidar.js
17 ms
glcfg510.js
9 ms
m
140 ms
pldpr510.js
89 ms
pldcr500.js
135 ms
ls.html
134 ms
mon
114 ms
box_19_top-right.png
155 ms
ci.png
155 ms
mon
104 ms
mon
104 ms
dt
143 ms
mon
133 ms
ba.html
153 ms
4.gif
155 ms
150 ms
surly.js
109 ms
dt
105 ms
dt
104 ms
dt
125 ms
15293
132 ms
pixel.gif
113 ms
n.js
112 ms
n.js
99 ms
n.js
89 ms
n.js
73 ms
pixel
62 ms
v4
69 ms
image.gif
49 ms
img;p=11087206531016;idfa=;idfa_lat=;aaid=;aaid_lat=;cache=1458482483720
58 ms
Ukitu.min.js
97 ms
WU2TPsgLEeSUDxIxPSpF6g
31 ms
mraid.js
33 ms
pixel
45 ms
pixel
47 ms
pixel.gif
29 ms
4311.js
51 ms
41640.js
50 ms
WU2TPsgLEeSUDxIxPSpF6g
18 ms
sfp-user-set-cookie.js
181 ms
ats
49 ms
_creativeJSFile.js
124 ms
pixel.gif
12 ms
WU2TPsgLEeSUDxIxPSpF6g
12 ms
sd
23 ms
pixel.gif
14 ms
pixel.gif
6 ms
pixel.gif
2 ms
pixel.gif
2 ms
pixel.gif
2 ms
pixel.gif
74 ms
9c2d3a98a203c49134aab6392531e38f.png
28 ms
ef3863de2d907289c60eb52716c401c6.jpeg
39 ms
pixel.gif
23 ms
WU2TPsgLEeSUDxIxPSpF6g
19 ms
pixel.gif
10 ms
pixel.gif
13 ms
pixel.gif
23 ms
pixel.gif
21 ms
pixel.gif
23 ms
H4jyvsy8EeSUDxIxPSpF6g
13 ms
lilliputing.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
Links do not have a discernible name
lilliputing.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
Missing source maps for large first-party JavaScript
lilliputing.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 Lilliputing.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 Lilliputing.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.
lilliputing.com
Open Graph data is detected on the main page of Lilliputing. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: