3.2 sec in total
69 ms
2.8 sec
315 ms
Click here to check amazing Status A Small Orange content for India. Otherwise, check out these important facts you probably never knew about status.asmallorange.com
Visit status.asmallorange.comWe analyzed Status.asmallorange.com page load time and found that the first response time was 69 ms and then it took 3.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
status.asmallorange.com performance score
name
value
score
weighting
Value2.2 s
76/100
10%
Value3.9 s
53/100
25%
Value3.6 s
86/100
10%
Value4,200 ms
1/100
30%
Value0.001
100/100
15%
Value13.6 s
11/100
10%
69 ms
165 ms
33 ms
60 ms
210 ms
Our browser made a total of 72 requests to load all elements on the main page. We found that 21% of them (15 requests) were addressed to the original Status.asmallorange.com, 11% (8 requests) were made to D.adroll.com and 6% (4 requests) were made to Facebook.com. The less responsive or slowest element that took the longest time to load (1.9 sec) relates to the external source Storage.luckyorange.net.
Page size can be reduced by 366.0 kB (54%)
672.9 kB
306.9 kB
In fact, the total size of Status.asmallorange.com main page is 672.9 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. 40% of websites need less resources to load. Javascripts take 511.8 kB which makes up the majority of the site volume.
Potential reduce by 36.1 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. This page needs HTML code to be minified as it can gain 5.1 kB, which is 11% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 36.1 kB or 81% of the original size.
Potential reduce by 2.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. Status A Small Orange images are well optimized though.
Potential reduce by 301.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 301.6 kB or 59% of the original size.
Potential reduce by 25.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. Status.asmallorange.com needs all CSS files to be minified and compressed as it can save up to 25.5 kB or 84% of the original size.
Number of requests can be reduced by 37 (76%)
49
12
The browser has sent 49 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Status A Small Orange. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
status.asmallorange.com
69 ms
status.asmallorange.com
165 ms
main.css
33 ms
fonts.css
60 ms
foundation-A123339-9773-4177-9c5f-7b735b3ac0dc1.js.gz
210 ms
gtm.js
100 ms
entry.js
38 ms
logo.png
308 ms
rss_orange.png
80 ms
asmallorange.com
226 ms
clock.png
37 ms
clock-b.png
78 ms
footer-bg.jpg
154 ms
logo.png
172 ms
sprite.png
154 ms
vollkornregular.woff
173 ms
3747581806.js
552 ms
roundtrip.js
133 ms
conversion_async.js
164 ms
analytics.js
162 ms
be716356c43dc45ab67d58c80d6c736685a5d677.js
230 ms
fbds.js
342 ms
heap-1725719924.js
213 ms
w.js
161 ms
brandon_bld.woff
100 ms
klinicslablight.woff
104 ms
brandon_blk.woff
138 ms
brandon_reg.woff
139 ms
foundation-tags-SD395-1eb7-483d-be6d-63dbb33501c31.min.js
100 ms
collect
53 ms
clickstream.min.js
83 ms
88 ms
mediasource-A123339-9773-4177-9c5f-7b735b3ac0dc1.js
183 ms
4U2C2QJPCFCJ7NMJNDMDCO.js
116 ms
collect
90 ms
h
70 ms
77 ms
storage.luckyorange.net
1925 ms
ga-audiences
28 ms
fbevents.hashing.js
86 ms
out
11 ms
out
6 ms
out
30 ms
out
29 ms
out
34 ms
out
35 ms
out
33 ms
130 ms
29 ms
u.php
137 ms
sync
57 ms
pixel
82 ms
67 ms
tap.php
40 ms
72 ms
sd
31 ms
377928.gif
21 ms
in
19 ms
5 ms
event
52 ms
css
56 ms
vbfwY87kf6-hyxJ8vOy6PeTef1gmZ9S
28 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
55 ms
MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf
63 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
73 ms
3107
39 ms
21 ms
settings.luckyorange.net
48 ms
64 ms
mutation.min.js
21 ms
reset.css
48 ms
10 ms
status.asmallorange.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.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
Image elements do not have [alt] attributes
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
status.asmallorange.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
status.asmallorange.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Status.asmallorange.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Status.asmallorange.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.
status.asmallorange.com
Open Graph description is not detected on the main page of Status A Small Orange. 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: