3.3 sec in total
13 ms
2.8 sec
419 ms
Click here to check amazing Next Gen Ortho content. Otherwise, check out these important facts you probably never knew about nextgenortho.us
At NextGen Dental & Orthodontics in Wheeling, IL, our dentists offer the latest in pediatric dentistry and general dentistry to ensure optimal oral health.
Visit nextgenortho.usWe analyzed Nextgenortho.us page load time and found that the first response time was 13 ms and then it took 3.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
nextgenortho.us performance score
name
value
score
weighting
Value7.5 s
1/100
10%
Value10.1 s
0/100
25%
Value11.3 s
5/100
10%
Value1,090 ms
24/100
30%
Value0.001
100/100
15%
Value16.9 s
5/100
10%
13 ms
261 ms
60 ms
70 ms
49 ms
Our browser made a total of 94 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Nextgenortho.us, 53% (50 requests) were made to Nextgendentalonline.com and 22% (21 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (771 ms) relates to the external source Nextgendentalonline.com.
Page size can be reduced by 224.8 kB (10%)
2.2 MB
2.0 MB
In fact, the total size of Nextgenortho.us 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. 70% of websites need less resources to load. Images take 1.8 MB which makes up the majority of the site volume.
Potential reduce by 62.0 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 62.0 kB or 85% of the original size.
Potential reduce by 15.6 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. Next Gen Ortho images are well optimized though.
Potential reduce by 146.2 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 146.2 kB or 37% of the original size.
Potential reduce by 919 B
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. Nextgenortho.us needs all CSS files to be minified and compressed as it can save up to 919 B or 11% of the original size.
Number of requests can be reduced by 40 (61%)
66
26
The browser has sent 66 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Next Gen Ortho. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 34 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
nextgenortho.us
13 ms
www.nextgendentalonline.com
261 ms
669b63244b7fcb767e9c2c85a08ca177.css
60 ms
font-awesome.min.css
70 ms
font-awesome.min.css
49 ms
jquery-ui.css
45 ms
print.min.css
50 ms
classic.css
466 ms
classic.date.css
469 ms
jquery-1.12.4-wp.js
168 ms
jquery-migrate-1.4.1-wp-ec3ddf14687aa194c227916372a99dbb.js
161 ms
js
77 ms
scripts-e9a7e8ac959620a25b0427b865cf2fef.js
161 ms
jquery.wpcf7-starrating-d8c9cedf07e0c86a6cf55abfe9476a00.js
166 ms
core.min.js
166 ms
widget.min.js
167 ms
accordion.min.js
213 ms
frontend-6053837177ddfb0b4dc75bcdee7fe886.js
216 ms
wpcf7-redirect-frontend-script-b9720351a5638d79a734ba4f8c4202a6.js
218 ms
imagesloaded.min.js
219 ms
masonry.min.js
220 ms
modernizr_2.8.3-0f733da3660f5a8ae29af774984ac075.js
220 ms
masonry.pkgd-f263b8fefcd7b89a84e9673cd78f9a52.js
269 ms
jquery-ui.min.js
50 ms
jquery.customSelect-64ce9baae3221c74458f9d62c588a95f.js
270 ms
jquery.bxslider.min.js
270 ms
jquery.fancybox.min.js
273 ms
jquery.sidr.min.js
273 ms
custom-form-elements-4500135bcdf1390c5cbb60e082d98faa.js
272 ms
jquery.mmenu.min.all-1a7c3cb26bca344217ae2d70a501204f.js
322 ms
print.min.js
225 ms
jquery.sticky-9e6e7f6158741990fd73b566c16c6904.js
324 ms
picker.js
558 ms
picker.date.js
557 ms
jquery.inputmask.bundle.js
558 ms
baslider-7bf03556c1e75b75dfd14ec4b8279b32.js
322 ms
script-e15b78bc010801a0ab50d6c6c40cf671.js
324 ms
wp-embed.min.js
324 ms
wpcf7-recaptcha-controls-2f2976a7ba53414e5093b96abb28c335.js
325 ms
api.js
64 ms
css
27 ms
phone-icon.png
80 ms
location-icon.png
65 ms
logo.png
66 ms
slide_1.jpg
66 ms
slide-2-1.png
308 ms
slide-3.png
299 ms
3-e1576081346163-600x300.jpg
218 ms
background_diff.jpg
450 ms
miami-office.png
771 ms
bg_home.jpg
219 ms
img_1.png
307 ms
img_2.png
483 ms
app.png
369 ms
logo_1.jpg
370 ms
logo_2.jpg
370 ms
logo_3.jpg
452 ms
invisalign-platinum-provider2.png
458 ms
phone-white.png
452 ms
js
149 ms
analytics.js
145 ms
KFOmCnqEu92Fr1Mu4mxMKTU1Kg.woff
146 ms
KFOmCnqEu92Fr1Mu7GxMKTU1Kvnz.woff
147 ms
KFOmCnqEu92Fr1Mu7WxMKTU1Kvnz.woff
223 ms
KFOmCnqEu92Fr1Mu4WxMKTU1Kvnz.woff
231 ms
KFOmCnqEu92Fr1Mu7mxMKTU1Kvnz.woff
233 ms
KFOmCnqEu92Fr1Mu5mxMKTU1Kvnz.woff
233 ms
KFOmCnqEu92Fr1Mu72xMKTU1Kvnz.woff
233 ms
KFOlCnqEu92Fr1MmEU9fBBc-AMP6lQ.woff
234 ms
KFOlCnqEu92Fr1MmEU9fChc-AMP6lbBP.woff
233 ms
KFOlCnqEu92Fr1MmEU9fCxc-AMP6lbBP.woff
232 ms
font
290 ms
KFOlCnqEu92Fr1MmEU9fCBc-AMP6lbBP.woff
263 ms
KFOlCnqEu92Fr1MmEU9fABc-AMP6lbBP.woff
264 ms
KFOlCnqEu92Fr1MmEU9fCRc-AMP6lbBP.woff
263 ms
KFOlCnqEu92Fr1MmWUlfBBc-AMP6lQ.woff
263 ms
KFOlCnqEu92Fr1MmWUlfChc-AMP6lbBP.woff
263 ms
KFOlCnqEu92Fr1MmWUlfCxc-AMP6lbBP.woff
288 ms
KFOlCnqEu92Fr1MmWUlfBxc-AMP6lbBP.woff
288 ms
KFOlCnqEu92Fr1MmWUlfCBc-AMP6lbBP.woff
288 ms
KFOlCnqEu92Fr1MmWUlfABc-AMP6lbBP.woff
288 ms
KFOlCnqEu92Fr1MmWUlfCRc-AMP6lbBP.woff
287 ms
Sagona-MediumItalic.woff
397 ms
Sagona-Medium.woff
436 ms
Sagona-Bold.woff
427 ms
fontawesome-webfont.woff
140 ms
fontawesome-webfont.woff
141 ms
recaptcha__en.js
186 ms
refill
537 ms
ajax-loader.gif
312 ms
collect
48 ms
collect
119 ms
ga-audiences
27 ms
select.png
55 ms
nextgenortho.us accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
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
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.
nextgenortho.us best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
nextgenortho.us SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
Tap targets are not sized appropriately
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Nextgenortho.us 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 Nextgenortho.us 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.
nextgenortho.us
Open Graph data is detected on the main page of Next Gen Ortho. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: