2.1 sec in total
697 ms
1.1 sec
254 ms
Click here to check amazing Broken Body content. Otherwise, check out these important facts you probably never knew about broken-body.net
Visit broken-body.netWe analyzed Broken-body.net page load time and found that the first response time was 697 ms and then it took 1.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.
broken-body.net performance score
name
value
score
weighting
Value2.4 s
70/100
10%
Value4.8 s
31/100
25%
Value4.4 s
75/100
10%
Value140 ms
96/100
30%
Value0.009
100/100
15%
Value4.2 s
85/100
10%
697 ms
165 ms
341 ms
159 ms
200 ms
Our browser made a total of 6 requests to load all elements on the main page. We found that 83% of them (5 requests) were addressed to the original Broken-body.net, 17% (1 request) were made to Np.lexity.com. The less responsive or slowest element that took the longest time to load (697 ms) belongs to the original domain Broken-body.net.
Page size can be reduced by 334.7 kB (22%)
1.5 MB
1.2 MB
In fact, the total size of Broken-body.net 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. Only 10% of websites need less resources to load. Images take 1.5 MB which makes up the majority of the site volume.
Potential reduce by 1.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 1.8 kB or 54% of the original size.
Potential reduce by 303.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. Obviously, Broken Body needs image optimization as it can save up to 303.5 kB or 20% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 27.9 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 27.9 kB or 78% of the original size.
Potential reduce by 1.6 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. Broken-body.net needs all CSS files to be minified and compressed as it can save up to 1.6 kB or 73% of the original size.
We found no issues to fix!
5
5
The browser has sent 5 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Broken Body. According to our analytics all requests are already optimized.
broken-body.net
697 ms
style.css
165 ms
s-header.png
341 ms
s-bg001.png
159 ms
s-bg02x.png
200 ms
96f50953f0c318490d43b98b982e4b16
73 ms
broken-body.net 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.
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
Form elements do not have associated labels
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
broken-body.net 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
broken-body.net SEO score
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
N/A
N/A
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Broken-body.net 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 Broken-body.net main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
broken-body.net
Open Graph description is not detected on the main page of Broken Body. 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: