5.5 sec in total
1.2 sec
3.1 sec
1.3 sec
Welcome to jawsurgeryblog.com homepage info - get ready to check Jawsurgeryblog best content for Sweden right away, or after learning these important things about jawsurgeryblog.com
My double jaw surgery was scary but turned out great, so I created a blog and community to make it easier for future orthognathic patients...
Visit jawsurgeryblog.comWe analyzed Jawsurgeryblog.com page load time and found that the first response time was 1.2 sec and then it took 4.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
jawsurgeryblog.com performance score
name
value
score
weighting
Value1.8 s
89/100
10%
Value2.1 s
96/100
25%
Value1.8 s
100/100
10%
Value0 ms
100/100
30%
Value0.024
100/100
15%
Value1.8 s
100/100
10%
1186 ms
7 ms
206 ms
140 ms
159 ms
Our browser made a total of 49 requests to load all elements on the main page. We found that 59% of them (29 requests) were addressed to the original Jawsurgeryblog.com, 10% (5 requests) were made to Fonts.gstatic.com and 6% (3 requests) were made to S.ytimg.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Jawsurgeryblog.com.
Page size can be reduced by 567.2 kB (52%)
1.1 MB
517.1 kB
In fact, the total size of Jawsurgeryblog.com main page is 1.1 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. 35% of websites need less resources to load. Javascripts take 442.7 kB which makes up the majority of the site volume.
Potential reduce by 34.7 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 34.7 kB or 73% of the original size.
Potential reduce by 16.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. Jawsurgeryblog images are well optimized though.
Potential reduce by 276.7 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 276.7 kB or 62% of the original size.
Potential reduce by 239.7 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. Jawsurgeryblog.com needs all CSS files to be minified and compressed as it can save up to 239.7 kB or 83% of the original size.
Number of requests can be reduced by 20 (49%)
41
21
The browser has sent 41 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Jawsurgeryblog. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
www.jawsurgeryblog.com
1186 ms
webfont.js
7 ms
css.css
206 ms
styles.css
140 ms
fancybox.css
159 ms
jquery.js
341 ms
jquery-migrate.min.js
137 ms
jquery.fancybox.js
267 ms
jquery.form.min.js
76 ms
scripts.js
78 ms
counter.js
21 ms
css
23 ms
LeFlHvsZjXu2c3ZRgBq9nD8E0i7KZn-EPnyo3HZu7kw.woff
30 ms
PIbvSEyHEdL91QLOQRnZ13hCUOGz7vYGh680lGh-uXM.woff
40 ms
ByLA_FLEa-16SpQuTcQn4IbN6UDyHWBl620a-IRfuBk.woff
58 ms
displays.htm
54 ms
signup.png
53 ms
bg1.png
73 ms
jsb-logo-new.jpg
96 ms
banner-arrow1.png
84 ms
header-before-during-after.png
210 ms
1.png
85 ms
access-icon.png
847 ms
author.jpg
151 ms
wisdom-teeth-surgery-300x182.jpg
165 ms
corrective-jaw-surgery-300x200.jpg
158 ms
after-corrective-jaw-surgery-smile-300x225.jpg
171 ms
before-corrective-jaw-surgery-profile-300x225.jpg
233 ms
after-corrective-jaw-surgery-profile-300x225.jpg
234 ms
before-corrective-jaw-surgery-bite-300x225.jpg
237 ms
after-corrective-jaw-surgery-bite-300x225.jpg
246 ms
before-corrective-jaw-surgery-front-300x225.jpg
260 ms
after-corrective-jaw-surgery-front-300x225.jpg
359 ms
corrective-jaw-surgery-before-after-300x150.jpg
360 ms
jsb-cover-sidebar.jpg
438 ms
buy-now-button.png
360 ms
displays.htm
49 ms
analytics.js
30 ms
t.php
148 ms
hy74x6g3qS0
82 ms
icons.ttf
310 ms
collect
13 ms
www-embed-player-vfl8xM8me.css
61 ms
www-embed-player.js
81 ms
base.js
153 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
30 ms
ad_status.js
60 ms
2UX7WLTfW3W8TclTUvlFyQ.woff
76 ms
RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff
84 ms
jawsurgeryblog.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
<frame> or <iframe> elements do not have a title
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.
jawsurgeryblog.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Browser errors were logged to the console
jawsurgeryblog.com 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
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Jawsurgeryblog.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 Jawsurgeryblog.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.
jawsurgeryblog.com
Open Graph description is not detected on the main page of Jawsurgeryblog. 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: