3.3 sec in total
323 ms
2.3 sec
732 ms
Visit rdublog.com now to see the best up-to-date Rdublog content for United States and also check out these interesting facts you probably never knew about rdublog.com
The official blog of Raleigh-Durham International Airport
Visit rdublog.comWe analyzed Rdublog.com page load time and found that the first response time was 323 ms and then it took 3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
rdublog.com performance score
name
value
score
weighting
Value4.1 s
20/100
10%
Value11.7 s
0/100
25%
Value7.1 s
30/100
10%
Value970 ms
28/100
30%
Value0.134
80/100
15%
Value13.1 s
12/100
10%
323 ms
112 ms
122 ms
126 ms
122 ms
Our browser made a total of 127 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Rdublog.com, 16% (20 requests) were made to S0.wp.com and 14% (18 requests) were made to Pixel.wp.com. The less responsive or slowest element that took the longest time to load (351 ms) relates to the external source Static.xx.fbcdn.net.
Page size can be reduced by 749.8 kB (44%)
1.7 MB
940.7 kB
In fact, the total size of Rdublog.com main page is 1.7 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. 75% 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 903.7 kB which makes up the majority of the site volume.
Potential reduce by 76.3 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 76.3 kB or 78% of the original size.
Potential reduce by 3.1 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. Rdublog images are well optimized though.
Potential reduce by 642.8 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 642.8 kB or 71% of the original size.
Potential reduce by 27.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. Rdublog.com needs all CSS files to be minified and compressed as it can save up to 27.7 kB or 46% of the original size.
Number of requests can be reduced by 71 (60%)
119
48
The browser has sent 119 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Rdublog. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 40 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
rdublog.com
323 ms
style.css
112 ms
122 ms
126 ms
style.css
122 ms
gprofiles.js
139 ms
wpgroho.js
118 ms
118 ms
118 ms
tiled-gallery.css
116 ms
134 ms
widgets.js
344 ms
119 ms
w.js
99 ms
merriweather.css
10 ms
rdublogbanner2.jpg
158 ms
platform.js
142 ms
sdk.js
307 ms
5945ded206cee8d702925661288c5376
163 ms
6b725e25159c019c6c78c32f91b1e821
162 ms
rdu_1134.jpg
143 ms
181394313-santiegochile.jpg
141 ms
bll01.jpg
147 ms
wordpress.png
135 ms
loading.gif
139 ms
master.html
138 ms
86dc77681a2b9e6e443bb7cc0cf5a1bf
144 ms
e0796d43757039f84f4272f2d30dfea6
190 ms
ed65fd1f7293d206ad19bae49a98b50f
189 ms
268ab5668e15f5a96bfaa2b0705ebf4d
187 ms
delhi.jpg
263 ms
philadelphia.jpg
296 ms
cancun.jpg
283 ms
160735798-saltlake.jpg
131 ms
186210832-dubai.jpg
126 ms
dsc1345.jpg
144 ms
rdu_0946.jpg
134 ms
482078223-wallchina.jpg
154 ms
6cf9c10a5e618f1b5933234b366f4e13
179 ms
f6ee74e9d8eec23a5b3a1b160a5c0d50
248 ms
ff62a7921bf8521f98752e6531605414
247 ms
accinterior.jpg
131 ms
onestop.jpg
154 ms
Genericons.svg
141 ms
8AAnjaY2BgYGQAgosrjpwF0ZcUq9bCaABTzgdAAAA=
36 ms
Noticons.svg
148 ms
BaABdRAi2AAAA
31 ms
merriweather-bold-webfont.ttf
170 ms
merriweather-regular-webfont.ttf
244 ms
merriweather-light-webfont.ttf
268 ms
rdublogbanner2.jpg
276 ms
jquery.js
246 ms
hovercard.css
169 ms
services.css
203 ms
share
268 ms
g.gif
149 ms
count.json
264 ms
graph.facebook.com
199 ms
share
301 ms
count.json
259 ms
graph.facebook.com
259 ms
share
327 ms
count.json
257 ms
graph.facebook.com
258 ms
share
320 ms
count.json
255 ms
graph.facebook.com
255 ms
share
315 ms
count.json
251 ms
graph.facebook.com
291 ms
index.html
56 ms
g.gif
123 ms
g.gif
123 ms
g.gif
122 ms
g.gif
123 ms
g.gif
122 ms
g.gif
154 ms
g.gif
153 ms
g.gif
154 ms
g.gif
153 ms
g.gif
153 ms
g.gif
151 ms
g.gif
156 ms
g.gif
155 ms
g.gif
155 ms
g.gif
145 ms
g.gif
149 ms
g.gif
149 ms
jquery.js
123 ms
266 ms
xd_arbiter.php
209 ms
xd_arbiter.php
341 ms
postmessage.js
34 ms
jed.js
33 ms
underscore.min.js
34 ms
postmessage.js
34 ms
jed.js
33 ms
underscore.min.js
35 ms
jquery.wpcom-proxy-request.js
9 ms
jquery.wpcom-proxy-request.js
9 ms
52 ms
likes-rest.js
5 ms
follow-rest.js
6 ms
7 ms
batch
216 ms
batch
28 ms
http%3A%2F%2Frdublog.com
184 ms
botd.gif
220 ms
style.css
10 ms
k3k702ZOKiLJc3WVjuplzKRDOzjiPcYnFooOUGCOsRk.woff
32 ms
page.php
102 ms
2 ms
noticons.css
6 ms
style.css
4 ms
Noticons.svg
3 ms
bC7hIHbP4Mf.css
165 ms
q68gy-v_YMF.js
278 ms
YvxwM8R7ol8.js
351 ms
ihptErjAmMX.js
326 ms
1477443_813352802028054_1034898714_n.jpg
170 ms
577096_505915959438408_1740666040_n.jpg
206 ms
wL6VQj7Ab77.png
85 ms
s7jcwEQH7Sx.png
85 ms
R9a_DtVRZgv.js
38 ms
cUDgRFxaoIk.js
42 ms
0JBr1QHp8Gi.js
39 ms
kDOzhTr2W91.js
76 ms
rdublog.com 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.
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
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.
rdublog.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
Browser errors were logged to the console
rdublog.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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 Rdublog.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 Rdublog.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.
rdublog.com
Open Graph data is detected on the main page of Rdublog. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: