3.8 sec in total
264 ms
3.4 sec
96 ms
Click here to check amazing Run 2 Airport content. Otherwise, check out these important facts you probably never knew about run2airport.com
Save up to 35% on flights and hotels. We put the best flight and hotel packages together for you so you don't need to search for your flight and hotel separately.
Visit run2airport.comWe analyzed Run2airport.com page load time and found that the first response time was 264 ms and then it took 3.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
run2airport.com performance score
name
value
score
weighting
Value2.9 s
52/100
10%
Value2.9 s
80/100
25%
Value13.2 s
2/100
10%
Value5,370 ms
0/100
30%
Value0.193
64/100
15%
Value21.0 s
1/100
10%
264 ms
1829 ms
129 ms
299 ms
255 ms
Our browser made a total of 94 requests to load all elements on the main page. We found that 69% of them (65 requests) were addressed to the original Run2airport.com, 16% (15 requests) were made to Fonts.gstatic.com and 4% (4 requests) were made to Tp.media. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Run2airport.com.
Page size can be reduced by 844.8 kB (70%)
1.2 MB
363.6 kB
In fact, the total size of Run2airport.com main page is 1.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. 60% of websites need less resources to load. CSS take 934.0 kB which makes up the majority of the site volume.
Potential reduce by 58.6 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 58.6 kB or 81% of the original size.
Potential reduce by 0 B
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. Run 2 Airport images are well optimized though.
Potential reduce by 27.3 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.3 kB or 16% of the original size.
Potential reduce by 758.8 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. Run2airport.com needs all CSS files to be minified and compressed as it can save up to 758.8 kB or 81% of the original size.
Number of requests can be reduced by 69 (91%)
76
7
The browser has sent 76 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Run 2 Airport. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 51 to 1 for JavaScripts and from 20 to 1 for CSS and as a result speed up the page load time.
run2airport.com
264 ms
run2airport.com
1829 ms
wp-emoji-release.min.js
129 ms
style.min.css
299 ms
classic-themes.min.css
255 ms
style.min.css
250 ms
theme.min.css
252 ms
frontend-lite.min.css
515 ms
post-213.css
352 ms
elementor-icons.min.css
419 ms
swiper.min.css
337 ms
frontend-lite.min.css
340 ms
global.css
385 ms
post-267.css
421 ms
post-252.css
425 ms
post-249.css
442 ms
loader.502052c178d2b15bb98b.css
474 ms
css
35 ms
fontawesome.min.css
584 ms
solid.min.css
504 ms
brands.min.css
509 ms
jquery.min.js
706 ms
jquery-migrate.min.js
557 ms
js
92 ms
js
165 ms
widget-nav-menu.min.css
567 ms
content
529 ms
widget-search-iframe.js
215 ms
scripts_en.js
518 ms
content
498 ms
content
489 ms
content
503 ms
widget-icon-list.min.css
569 ms
lodash.min.js
655 ms
wp-polyfill-inert.min.js
609 ms
regenerator-runtime.min.js
633 ms
wp-polyfill.min.js
650 ms
autop.min.js
654 ms
blob.min.js
742 ms
block-serialization-default-parser.min.js
741 ms
react.min.js
742 ms
hooks.min.js
742 ms
deprecated.min.js
795 ms
dom.min.js
796 ms
react-dom.min.js
803 ms
escape-html.min.js
810 ms
element.min.js
874 ms
is-shallow-equal.min.js
788 ms
i18n.min.js
668 ms
keycodes.min.js
667 ms
priority-queue.min.js
706 ms
compose.min.js
660 ms
private-apis.min.js
647 ms
redux-routine.min.js
643 ms
data.min.js
632 ms
html-entities.min.js
599 ms
shortcode.min.js
620 ms
blocks.min.js
863 ms
hello-frontend.min.js
623 ms
runtime.953b7d9d487275a1040f.js
590 ms
loader.b3502b7f4263defd178d.js
570 ms
jquery.smartmenus.min.js
615 ms
webpack-pro.runtime.min.js
631 ms
webpack.runtime.min.js
591 ms
frontend-modules.min.js
565 ms
frontend.min.js
563 ms
waypoints.min.js
603 ms
core.min.js
587 ms
frontend.min.js
645 ms
elements-handlers.min.js
556 ms
jquery.sticky.min.js
564 ms
run2airportlogo-1024x293.jpeg
569 ms
run2airportlogo-300x86.jpeg
544 ms
js
118 ms
analytics.js
49 ms
KFOmCnqEu92Fr1Mu4mxMKTU1Kg.woff
85 ms
KFOlCnqEu92Fr1MmEU9fBBc-AMP6lQ.woff
86 ms
KFOlCnqEu92Fr1MmSU5fBBc-AMP6lQ.woff
119 ms
KFOkCnqEu92Fr1MmgVxIIzQXKMny.woff
124 ms
KFOlCnqEu92Fr1MmWUlfBBc-AMP6lQ.woff
136 ms
KFOlCnqEu92Fr1MmYUtfBBc-AMP6lQ.woff
136 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtapbCIPrcVIT9d4cw.woff
135 ms
font
210 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCIPrcVIT9d4cw.woff
138 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpbCIPrcVIT9d4cw.woff
124 ms
font
161 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrcVIT9d4cw.woff
136 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCIPrcVIT9d4cw.woff
136 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtaorCIPrcVIT9d4cw.woff
157 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvao7CIPrcVIT9d4cw.woff
181 ms
collect
70 ms
fa-brands-400.woff
424 ms
collect
46 ms
ga-audiences
31 ms
run2airport.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.
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
Form elements do not have associated labels
run2airport.com 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
Page has valid source maps
run2airport.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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Run2airport.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 Run2airport.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.
run2airport.com
Open Graph data is detected on the main page of Run 2 Airport. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: